- From: Thomas Michael Semmler via GitHub <sysbot+gh@w3.org>
- Date: Sun, 10 Oct 2021 20:46:10 +0000
- To: public-houdini-archive@w3.org
I just ran into this issue and wanna express the validity of this use case, if that is any help. Projects like [Houdini.how](https://houdini.how/) provide CDN links to paintworklets, presenting them as a single-file dependency. This means, that authors of paintworklets may need to sanitise inputProperties from custom properties or document them with specific instructions, when the CSS Typed OM is right there, just not connected. This becomes especially relevant when `<length>` units are used. Worklets on houdini.how work with unit-less number inputs and are even required to do so in order to be able to [submit them](https://github.com/GoogleChromeLabs/houdini.how/blob/main/CONTRIBUTING.md). This layer could be entirely eliminated, with paintworklets being able to access the CSS Typed OM API right from `inputProperties()`. Currently, If authors of paintworklets wanna utilise the CSS Typed OM API, they'll have to instruct users to either use `CSS.registerProperty` or `@property` in CSS adding fragmentation, where it might not be needed. -- GitHub Notification of comment by nachtfunke Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/924#issuecomment-939549842 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 10 October 2021 20:46:12 UTC