- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Sep 2024 01:31:18 +0000
- To: public-css-archive@w3.org
@ZachHaber In that case, it shouldn't be a Note. A Note explains the reason for or the consequences of pre-existing requirements / allowances. A statement with RFC2119 SHOULD gives new normative expectations. As phrased, we're just remarking that given how this is defined, this is a thing UAs can do. Whether they actually do it is a question of UI design, and up to them. If we take it out of a Note, and use SHOULD, it because a thing we expect of them (unless they have a good reason not to do it). Here, I'm a bit on the fence about which to go for. I feel like this is indeed something they should do, but whether a CSS spec is the right place to set expectations on UI component design is less clear to me. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10591#issuecomment-2354329466 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 September 2024 01:31:19 UTC