- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 May 2019 14:57:04 +0000
- To: public-houdini-archive@w3.org
Okay, so that's kinda a 3.5. To make that a consistent line thru the APIs, it would mean that: * .setProperty() throws on invalid syntax for registered props * .supports(prop, val) validates registered props * all the TypedOM methods throw on invalid syntax If this is what we settle on I won't be too unhappy, but I don't *like* it either - it feels very much like a dividing line drawn by internal browser APIs (am I invoking a declaration-value parsing function, or a more general CSS parser?) rather than author-exposed usage patterns (what I was trying to do with 4). But like I said, I'm fine with it if y'all are happy, it's still an improvement over the current world. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/880#issuecomment-490116015 using your GitHub account
Received on Tuesday, 7 May 2019 14:57:05 UTC