At some point Claude switched from doing things deterministically (e.g. knowing the position of an element based on its css) to wanting to eyeball everything (take screenshot, make some judgment). I disabled claude-in-chrome but it's still finding a headless browser to use.

CSS is great - until it’s not. If you're curious about shaders but don't know where to start, this guide, written by @marchantweb will gently walk you through why and how to use them in modern UI. Read it here👇

What makes Arm CSS for Mobile 2 more than a collection of IP? 📱 It brings together world-class AI CPU and GPU capabilities, including the Arm C2 CPU Cluster with SME2 and Mali G2-Ultra NX, with system technologies and software in one configurable AI-native platform. @ctbergey breaks down the bigger platform story. Watch the full keynote on Arm YouTube:

Introducing Arm CSS for Mobile 2. 📱 Built for the system-level demands of agentic AI and cinematic mobile graphics, our new AI-native compute platform brings together world-class AI CPU and GPU capabilities to change what the next generation of mobile devices can do.

Different products need different choices.  Arm CSS for Mobile 2 brings together world-class AI CPU and GPU capabilities, system IP and software in a configurable foundation partners can tailor to build differentiated custom SoCs. @ctbergey shares what that unlocks. 👇

Recent performance fix: lazy-loaded CSS comes with a price. @vite_js build.cssCodeSplit helped us. Linear still uses CSS Modules for complex selectors not yet migrated to @stylexjs. When our module preloader warmed lazy-loaded chunks that contained CSS, it attached new stylesheets in quick succession. Each invalidated style and layout across the page, triggering 28 full-page layouts. 🥺 We fixed this by setting `build.cssCodeSplit` to false, which makes Vite emit one stylesheet. As StyleX already uses atomic CSS, the file size is acceptable and bounded. That introduced a new issue: Vite adds the file to the HTML as a render-blocking link, delaying our custom loader icon baked into the HTML. Our post-build step rewrites the link to media=print so it fetches early without blocking the loader. We wait for it to load, switch it to media=all, and only then render the app.