Ian Kilpatrick
@bfgeek
Followers
787
Following
1K
Media
76
Statuses
1K
🇦🇺🦘 in California. Software Engineer on Blink for CSS, Layout, Rendering. Swim.
Menlo Park, CA
Joined April 2009
Amazing work by the Microsoft engineers on this project. In particular really excited to see the major performance cliff removed by this: https://t.co/dlO8ZKclrq 1/N
Microsoft Edge 93 includes a new rewrite of the CSS Grid 1 module (GridNG), with substantial improvements to Chromium's cross-browser compatibility for CSS Grid. Learn more in our latest #Compat2021 blog:
2
16
70
Congrats to @int32_t for shipping line-breakable ruby!
Chrome 128からは、長いルビは改行可能になります https://t.co/sgDHJfrcyX
1
0
4
Super happy this is shipping. Congrats to Kyra. Large privacy/security win. (The CSS :visited selector wont match if you've visited a particular site, only if you've visited that site from the site you are currently on).
Blink: Intent to Experiment: Partitioning :visited links history Phase 2
1
12
38
Fyi - 👀 - Upcoming releases of Safari may start returning incorrect results for: document.body.getBoundingClientRect() (Began to break in latest Safari TP). https://t.co/sTaKJp2vSe
0
0
1
andres freund: genius programmer responsible for one of the most widely used pieces of software in the world, just single-handedly stopped a huge attack from happening. nyt journalist: 'i am too fucking stupid to understand his work and won't even try but it's very boring!!!'
154
852
11K
🖌️ CSS field-sizing shipped in Chrome Stable last week. Check out the details on the blog 👇 https://t.co/I9RQYoSZhF
blog.stephaniestimac.com
A look at the `field-sizing` CSS property and how it could improve web form user experience.
✨New CSS Feature Here's a demo of the CSS field-sizing property applied on a <textarea> I blogged about yesterday. textarea { field-sizing: content; } The textarea grows as you add content. This is currently in developer trial behind a flag in Chromium.
0
7
32
Malte from Team-SSR here: I looked into this and their website was robots.txt-blocking the JS necessary to render their content. Hence Google could not index it. Google exclusively indexes your content by rendering it, operating on the DOM post rendering–never just the HTML.
looks like fixing the SSR (because google absolutely does NOT index pages that load content via javascript) is starting to have tangible lift in daily traffic
11
9
299
Lions share of work for this feature was specification work (both gaining consensus, and adding spec text), followed by testing, then implementation (with @int32_t doing most of the work). Glad to have it out the door soon!
0
0
5
(I'm biased, in all seriousness, just start taking Blink's style/layout engine and start cutting features).
0
0
1
TL;DR just take and strip down an existing engine, it'll be O(weeks) vs. O(months/years) to get a resonable subset of the web platform. Cursed those are who know the complexities of the CSS layout engine. 4/N
1
0
3
Another similar project is Cobalt ( https://t.co/0eKYtzyRAs) significant engineering resources to implement just a subset of the web platform.... 3/N
github.com
Cobalt is a lightweight HTML5 application container - youtube/cobalt
1
0
0
E.g. large parts of CSS aren't really well defined, and existing implementations are battled hardened for edge cases that take a long time to get right. A comparable project might be servo, and that's taken significant engineering resources to get where it is today.... 2/N
1
0
2
As @ElliottZ mentioned to me a while back - the folks behind https://t.co/TUU11xhzhI might want to consider pillaging large parts of existing web engines to achieve this rather than re-implement from scratch.... 1/N
2
0
3
Here's blink layout (left with ikilpatrick), and paint (right with pdr)
0
0
8
`field-sizing` property has been enabled since Google Chrome 123. https://t.co/nHP80CaOnN
1
1
7
The amount that Chromium is used to generate PDFs truly terrifies me some days: https://t.co/bGuEisJoZV (this is a relatively minor case - but some of our highest starred bugs under our Blink>Layout component are print related).
0
0
8
Don't over-index on one survey! One recent data-point I like to point out to folks is the new "field-sizing" property. https://t.co/tFrIGetjlZ This doesn't appear in many/any surveys (for a variety of potential reasons) but a massive missing feature for developers.
Should you believe the results of that web survey? Probably not. My top 10 best ways to understand developer sentiment. Did I miss anything?
0
0
5