Ian Kilpatrick

🇦🇺🦘 in California. Software Engineer on Blink for CSS, Layout, Rendering. Swim.

[Ian Kilpatrick @bfgeek]

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 Dev @MSEdgeDev]

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: https://t.co/JXxO6MSXYN

[Ian Kilpatrick @bfgeek]

@argyleink @_chenglou https://t.co/ka8dxYeRzS

[Ian Kilpatrick @bfgeek]

@argyleink @_chenglou @_chenglou If you are gluing text together with spaces (and assuming the spaces are the same width) you'll likely deviate from Blink on certain fonts with a large available width. E.g. a good test is "A V A V A V A V" repeated with Helvetica (I think) - Unless you disable 'kern'.

[Ian Kilpatrick @bfgeek]

@atroyn Good luck Anton, looking forward to seeing what you do next!

[Ian Kilpatrick @bfgeek]

@ericlaw @ChromiumDev @rick

[Ian Kilpatrick @bfgeek]

@stubbornella Its a real pain point for developers, see:
https://t.co/A3pN0Cxt3j
https://t.co/U91jaaEKGb
and a bunch of sites are using it per our use-counter.

[Ian Kilpatrick @bfgeek]

@stubbornella (also https://t.co/GyR2sispqh uses interactive-widget=resizes-content )

[Ian Kilpatrick @bfgeek]

@stubbornella This post reads as if the viewport units solve the same/similar problem, but it solves a different use-case, see:
https://t.co/y8sYZYXJHb.

[Ian Kilpatrick @bfgeek]

@int32_t (and thanks to @kosamari for the excellent write-up)

[Ian Kilpatrick @bfgeek]

Congrats to @int32_t for shipping line-breakable ruby!

[Koji Ishii @kojiishi]

Chrome 128からは、長いルビは改行可能になります
https://t.co/sgDHJfrcyX

[Ian Kilpatrick @bfgeek]

@briankardell @rachelandrew Roost laptop stand

[Ian Kilpatrick @bfgeek]

mistakes_in_css++

[Ian Kilpatrick @bfgeek]

@ElliottZ At the very least it'd be nice to remove the mitigations that were added (e.g. getComputedStyle lying) in an attempt to mitigate the privacy leakage.
(e.g. remove all the internal-visited logic).

I suspect to allowing more properties might be difficult (tm) as compat concerns.

[Ian Kilpatrick @bfgeek]

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).

[Intent To Ship @intenttoship]

Blink: Intent to Experiment: Partitioning :visited links history Phase 2 https://t.co/XnnwCDnVqo

[Ian Kilpatrick @bfgeek]

@ericlaw

[Ian Kilpatrick @bfgeek]

@briankardell Likely not the easiest discussion to have in short form twitter :P

[Ian Kilpatrick @bfgeek]

@briankardell .... The last 5% failures might be really bad. E.g. a 95% pass rate is worse than a 80% pass rate. Reason to focus on webdev issues filed.

[Ian Kilpatrick @bfgeek]

@briankardell > don't think of it
What constituency is it serving in your eyes? E.g. number goes up needs to have a net benefit to someone. (Personally for me that's webdevs and users)
> re:above
Yes we add tests. But if you are measuring end webdevs "happiness" it's a proxy.....

[Ian Kilpatrick @bfgeek]

@briankardell Also - WPT proxies are also often incomplete. E.g. they only test what there are tests for. One area where we are getting bugs for (related to aspect-ratio + flexbox) there are basically zero tests.
(See: https://t.co/y7KiAqn6GQ )

[Ian Kilpatrick @bfgeek]

@briankardell A thing to keep in mind is that all this is just a proxy for webdev sentiment (and user sentiment). The best proxy IMO is web developer filed bug reports (which we heavily index on). Incoming bug *rate* is also a good proxy.
WPT pass rate is ok as a proxy, but less valuable.

[Ian Kilpatrick @bfgeek]

@RickByers @LeaVerou I suspect this is more complex once you dig into the various things people are running into. E.g. embedding SVGs is a clear pain point digging into the free-form responses which isn't surprising. ("SVG" is kinda like saying "layout" there are likely multiple orthogonal things).