Safari on the left super responsive, zero delay. Safari Technology Preview on the right, it takes like half a second until the text is in place.
Of course, the transitions also don’t support reduced motion settings, so they are a great additional way to make your users feel sick. There are no website settings to turn them off.
@yatil css could have easily been added for reduced motion, the demo could have been better. I do welcome the view transition, animation does help in certain cases (not everywhere), and killing JS dependency is going to improve overall performance.
@yatil It doesn’t help that most people think reduce motion is level AAA, and clients only ask for AA. Unless i am wrong but i believe reduce motion is AA, making a custom control to turn animation on/off is AAA. So i always push for full reduce motion support. Just released a site this week with that.
@mikemai2awesome The argument is that the 2.3.3 is not concurrent to other content and not ongoing. It makes some sense. Also reduced motion wasn’t a thing when this was created, so implementing it was much harder which also decides the level.
And I’m sorry that I’m so negative about all this, but I see how people use these technologies and then cause harm with them. Like, my job is 80% preventing people from doing accidental harm. I don’t need more of that.
@yatil Not coupling these transitions with prefers-reduced-motion: reduce is nearly criminal, and I hope this will get resolved when it ships @webkit@firefox@developers
@marcus People don’t care about reduced motion today. View transitions will not change that. But they will make your content flashy in a new way, so it will be used everywhere!
@yatil At least prefer reduced motion, built-in and without explicit need to handle it (because, as you rightly say, no one cares), would prevent the worst and serve as an off-switch
@marcus Yeah, the problem is how would a browser know what to do with the animation. Like what are the two stages to toggle between. It’s hard to automate. Maybe it’s better/possible with view transitions?
@marcus@yatil
When View Transitions between page requests are possible, I imagine it would be relatively straightforward for browsers to completely ignore view transition CSS rules when "reduce motion" is enabled. The browser could either act as if it doesn't support View Transitions at all or a transition could still occur but with the user agent defaults (I forget how quick it is by default but there's no motion, it's a fade).
@marcus@yatil
Maybe the same could be done with current SPA View Transitions, I don't know if there could ever be losses to functionality or understanding if the authored transition is absent. I don't think they can be as complex as regular CSS animations.
Avoiding the need for authors to use prefers-reduced-motion would help.
@cwilcox808@marcus I haven’t looked that closely yet. I’m just exhausted that user preferences for these features are not part of the process. It should be.
@yatil Other than that, I second Eric's second comment. Browser vendors, please don't add another feature to cause avoidable harm because of fancyness and "move fast and break things" attitudes
Add comment