- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Aug 2024 17:08:39 +0000
- To: public-css-archive@w3.org
Comments promised in the call: > @flackr: I wanted to make an argument against complete customisation. […] The argument for this is that the UA could provide a consistent experience across sites and the OS. I think the web platform is rich enough to have vastly different types of apps and sites in it, where it might not be possible to normalize them to a specific set of values. Some apps might want to have snappier values, others — more relaxed. A work tool like a monitoring app will likely need a different set of values compared to something like a casual blog or a promo page. `short` and `long` could mean different things in the context of the corresponding design systems, and a pre-defined list of UA-only values couldn't cover all the use cases (but might be useful as the default consistent list). > > @mfreed7: It's still possible for UAs to override this for users, e.g. via a "make delays 10x longer" setting. > > @dholbert: I worry a little that with specifying exact time, developers would coordinate animations with delays which would look cool but would break with UA adjustments. I like an idea of a global 10x longer setting. For cases where we'd need to synchronize things, we could introduce something similar to `forced-color-adjust` property, but for these delays/transitions. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9236#issuecomment-2289344066 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 August 2024 17:08:40 UTC