- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Apr 2019 23:58:22 +0000
- To: public-css-archive@w3.org
Also, you could make the same argument for any other CSS rule, right? And scope() doesn't prevent something like: ``` document.styleSheets[0].cssRules[0].style.fontFamily = computedStyle.fontFamily; ``` from having that side-effect... So it seems only a partial fix for a particular use-case where the CSS rule that matched is from an outer tree, and the place where you stash the reference is in the same tree as the element you got the style from. As soon as you get out of that, you get the same kind of weirdness... so I'm not convinced that fixing that particular case is worth introducing scoped()... -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1995#issuecomment-484304534 using your GitHub account
Received on Wednesday, 17 April 2019 23:58:24 UTC