- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2023 17:53:25 +0000
- To: public-css-archive@w3.org
> Does "a list" imply that the as-specified order is retained? I don't think it necessarily does (and the order should be unimportant). In practice, a UA might want to sort the list (e.g. by binary value of tag) as part of its de-duplicating operation. I'm inclined to think it should be allowed (but not required) to do so. > the fix here is to change "as specified" to "as specified, with duplicates removed as described below" While we're here, is the UA allowed/expected to normalize feature settings such that tags with the value `1` or `on` are serialized without an explicit value, and `off` is normalized to `0`? That would be consistent with using the shortest form; but it means these aren't quite "as specified" in such cases. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8296#issuecomment-1377637564 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 January 2023 17:53:26 UTC