- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Sep 2024 01:01:39 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-view-transitions] Users need to be able to disable view transitions https://github.com/w3c/csswg-drafts/issues/10267`, and agreed to the following: * `RESOLVED: in cases of prefers-reduced-motion the UA stylesheet will define a cross-fade animation by default, without size/position animation` <details><summary>The full IRC log of that discussion</summary> <matatk> subtopic: [css-view-transitions] Users need to be able to disable view transitions https://github.com/w3c/csswg-drafts/issues/10267<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/10267<br> <fantasai> matatk: We discussed in APA, idea of being able to do some kind of reduction on View Transitions we thought would be helpful<br> <fantasai> ... but also acknowledge that there is a subtle, but big, difference between reducing and disabling motion<br> <fantasai> ... wrt motion, there is good infrastruction for reducing but not disabling<br> <fantasai> ... so consistency issues<br> <fantasai> ... We're generally in favor of some sort of control, but wondering what is the latest from CSSWG<br> <khush> q+<br> <fantasai> vmpstr: We can respect prefers-reduced-motion and set up different default animation that doesn't have motion and does a cross-fade<br> <fantasai> ... but if authors customize, then that's a regular CSS animation -- they are responsible at that point<br> <PaulG> q+<br> <matatk> q+ to ask about 'one-sided' transitions<br> <matatk> q?<br> <matatk> ack khush<br> <fantasai> khush: There's another issue where flackr had a proposal for a forced no-motion mode<br> <PaulG> q-<br> <fantasai> ... that would disable all CSS animations completely<br> <fantasai> ... that seems better path for a CSS-wide fix for it<br> <fantasai> ... didn't want to do something specific for View Transitions<br> <fantasai> khush: one detail is that we do something generic for animating position and size<br> <matatk> q?<br> <fantasai> ... can adjust the defaults for that accordingly<br> <matatk> ack me<br> <Zakim> matatk, you wanted to ask about 'one-sided' transitions<br> <fantasai> matatk: if moving between documents and ...<br> <fantasai> vmpstr: Animation runs on one page only. The outgoing page doesn't control the animation in any shape or form<br> <fantasai> ... just specifies which parts will participate<br> <matatk> q?<br> <fantasai> ... incoming page controls the animation, so that's where prefers-reduced-motion would take effect<br> <fantasai> ...<br> <fantasai> matatk: OK, we'll take as homework on what to recommend<br> <fantasai> vmpstr: We can resolve now I guess<br> <fantasai> ... in cases of prefers-reduced-motion we will construct a cross-fade animation by default, without size/position animation<br> <fantasai> vmpstr: Thoughts? Objections?<br> <kbabbitt> q+<br> <fantasai> chrishtr: removing animation completely would be a separate feature<br> <matatk> ack kbabbitt<br> <fantasai> kbabbitt: Do we need to be concerned about whether this is detected as a user preference through timing or something?<br> <fantasai> fantasai: it's a media query<br> <fantasai> khush: by design, want authors to adapt to it<br> <fantasai> kbabbitt: but do we want the info to be detectable (concern wrt fingerprinting)<br> <fantasai> gregwhitworth: If mapping to prefers-reduced-motion, you can already get that info via JS<br> <fantasai> matatk: if document doesn't give an alternative, then you'd use the default cross-fade?<br> <fantasai> ... another option would be to not run the normal one, but that's not reducing it<br> <fantasai> ... I think that would surprise authors<br> <fantasai> khush: Firefox disables marquee animations in this mode already, so there's some precedent<br> <fantasai> chrishtr: UA stylesheet would normally do cross-fade + transform<br> <fantasai> ... with the second rule for prefers-reduced-motion would only do cross-fade<br> <fantasai> ... author's rules would always override<br> <matatk> ack fantasai<br> <TabAtkins> fantasai: Whatever we put in the default UA stylesheet<br> <TabAtkins> fantasai: Unless we specifically make it an override, it'll get overridden by the author<br> <matatk> q?<br> <TabAtkins> fantasai: so if they create a custom animation, it'll work in both modes. They'll have to create their own reduced one.<br> <TabAtkins> fantasai: This'll just change the default animation<br> <fantasai> matatk: So up to us to say if we think this is a good idea<br> <PaulG> +1 for the default<br> <fantasai> matatk: Motion doesn't come just from CSS<br> <fantasai> ... if the user says prefers-reduced-motion, is there any browser engine looking into reducing other forms of motion?<br> <fantasai> fantasai: prefers-reduced-motion is a MQ that the author has to adjust for; UA can oly adjust it's defaults<br> <fantasai> ... if adding a forced mode, we would take more heavy-handed approach to suppressing author-provided motion<br> <fantasai> s/provided/specified/<br> <fantasai> matatk: [missed]<br> <fantasai> flackr: smooth scrolling can get turned off, small example<br> <fantasai> emilio: we do that too<br> <fantasai> emilio: it's interesting to have different heuristics here, but similar to forced colors<br> <matatk> q?<br> <khush> q+<br> <fantasai> ... if was ? then we could take more aggressive measures<br> <fantasai> ... but right now no standard way to expose<br> <fantasai> ... so would need different settings or different browsers<br> <fantasai> ... may or may not be solveable<br> <fantasai> ... ideally we do something like that, where we have a forced-reduced-motion mode<br> <fantasai> ... but I don't think we're there yet<br> <zcorpan> q?<br> <matatk> ack khush<br> <fantasai> khush: Not all browsers have setting, try to infer from OS settings<br> <miriam> s/was ?/it was a need (not just a preference)/<br> <fantasai> ... e.g. Android no animations gets mapped to prefers-reduced-motion<br> <fantasai> ... so what was in the OS vs what's in the browser don't match very well<br> <astearns> proposed resolution: in cases of prefers-reduced-motion the UA stylesheet wil define a cross-fade animation by default, without size/position animation<br> <astearns> RESOLVED: in cases of prefers-reduced-motion the UA stylesheet will define a cross-fade animation by default, without size/position animation<br> <vmpstr> \o/<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10267#issuecomment-2369894361 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 September 2024 01:01:40 UTC