- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 May 2019 15:19:59 +0000
- To: public-houdini-archive@w3.org
So the "must not affect the cascade" thing was to ensure that we didn't need to either: * do a global re-parse of all stylesheets every time a new thing was registered, or * expensively hold onto all custom stuff (along with side information like specificity) and re-evaluate just them every time a new thing was registered I think a whole block which is explicitly declared to depend on registration doesn't trigger these concerns. It's equivalent to some JS inserting a stylesheet alongside registering a property. Notably, this does *not* change the fallback behavior; registered props still are assumed valid until computed-value time, etc. This just allows you to supply different styles if the registration succeeds or not, which seems useful. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/882#issuecomment-490125494 using your GitHub account
Received on Tuesday, 7 May 2019 15:20:00 UTC