FeedCity

Get noodled.

RE: https://mastodon.world/@heypresents/116222571128090421

“Curiosity breeds Discovery”

I spend a fair bit of time playing with View Transitions, and bending it in all sorts of ways.

This talk compiles my insights from building some of the more wild things with VTs.

See you at All Day Hey!?

(Expect a lot of code getting thrown your way!)

Other takeaways are:

- Damn, that was fast!
- We need a way in DevTools/the web to be notified of style changes (hello, brm.us/style-observer!)
- We need a Element.getAnchor() JS method.
- The "remembered scroll offsets" are a PITA.

So. Anchor Positioning and DevTools …

I sat together with The Hype™ tonight and this is what we built in 2 hours.

Main takeaway from this experiment is that it still requires a “Subject Matter Expert” (in this case: me) to build this, instructing The Hype™ what to do (and sometimes how to do it).

Introducing `view-transitions-mock`: A non-visual Polyfill for Same-Document View Transitions

https://www.bram.us/2026/03/11/view-transitions-mock-is-a-non-visual-polyfill-for-same-document-view-transitions/

It is a spec-compliant JavaScript implementation of Same-Document View Transitions that polyfills the entire JavaScript API surface but that doesn’t do the animation bits.

View Transitions are a powerful Modern Web feature allow for smooth seamless animated transitions two between different states of a web page. They can make for a much more pleasant user experience, but as with any new web platform feature, browser support is not yet fully universal so you need to add some fallback logic to your code.

view-transitions-mock bridges that gap by polyfilling the full JavaScript API surface of Same-Document View Transitions, without the animation bits.

Get focused

The post Separate Writing and Formatting appeared first on iA.

Help me out:

I’m looking for examples / use-cases where you want to trigger an action _after_ a programmatic scroll(*) finished.

No need for an actual demo; a description of the use-case itself is good enough.

(*) Things such as `Element.scrollIntoView()` or `window.scrollTo()`.

RE: https://mastodon.social/@btconf/116199043077374654

👀

How to get focused

CSS Anchor Positioning is a powerful tool, but one of the things that you cannot do natively (yet) is animating the position-area property. This blog post introduces a technique to animate position-area changes using View Transitions.

On my way back home from #SotB2026 I hacked my way into animating between `position-area` values with View Transitions. The VT automatically gets started by a StyleObserver.

Demo + details can be found on my blog: https://brm.us/animate-position-area

It’s not 100% perfect though, as Firefox doesn’t do anything and Chrome has a 1-frame glitch.

Talk on CSS Anchor Positioning

RE: https://mastodon.world/@webstandards/116147775062588951

You can find the slides of my #SotB2026 talk on my blog: https://www.bram.us/2026/02/28/anchors-aweigh-sotb2026/

"Working in Office apps, we are trapped in an old world that ceased to exist decades ago. Like the office in Severance, the office embedded in Microsoft Office is fetishized: margins, borders, and page numbers are treated as signals of authority rather than remnants of a paper era." https://ia.net/topics/trapped-in-ms-office

Seeking IT independence, Europe wants to escape Microsoft Office. The question is: where to?

Seeking IT independence, Europe wants to escape Microsoft Office. The question is: where to?

The post Trapped in MS Office appeared first on iA.

You can install `view-transitions-mock` through NPM. The library is fully tested, in both browsers with and without native View Transitions support.

All info in the repo: https://github.com/GoogleChromeLabs/view-transitions-mock

With the mock registered, you can write modern standard-compliant Same-Document View Transitions code for _any_ browser, including those without support for document.startViewTransition or VT Types.

Safely call the API, handle its promises, and manage VT Types as if they were natively supported! 🥳

Supporting writers is something that has always driven what we do at iA. That's why we're so proud of our continued partnership with NYC Midnight. Learn more about our sponsorships for upcoming 2026 challenges:

https://ia.net/topics/nyc-midnight-and-ia-partner-again