- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jul 2022 18:08:45 +0000
- To: public-houdini-archive@w3.org
Hm, I suppose we can add those. The Speech module is completely unimplemented on the web (and I dunno how much it's implemented anywhere else?), which is why I forgot about it. ^_^ > They are missing in CSS Values but generally speaking, wouldn't it be better to refer to the dimensions defined in CSS Values, and avoid explicitly listing the supported dimensions? I need to add `CSS.foo()` methods for every unit anyway, so it's not like it would save me any effort. > I would like to know the reason why type entries must be ordered according to the order of the base types: Because object keys aren't randomly ordered, and if I don't specify an order it'll be impl-specific, and some code might some day depend on one impl's ordering and break in another (or break when an impl updates some code and changes their own ordering). It's a small chance of a future problem, but it's also very easy to avoid entirely by just making the order deterministic from the start. This ordering is exposed by the `.type()` method, which returns an object with the types as keys. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1075#issuecomment-1172595226 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 July 2022 18:08:51 UTC