W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

Re: [csswg-drafts] [css-scoping] Handling global name-defining constructs in shadow trees (#1995)

From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
Date: Fri, 19 Apr 2019 05:46:34 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-484774252-1555652792-sysbot+gh@w3.org>
> It seems plausible to me that some JS sets the inline style of an element to be equal to a .gCS() result, either of the same element or something else. The case where this results in a problem due to tree-references would be rare, but precisely because it's rare and thus wouldn't be correctly handled by most JS, I'd like to make it harder to run into.

Right, but `scoped()` only solves this particular case, and only if the "source" and "target" elements are in the same tree.

GitHub Notification of comment by emilio
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1995#issuecomment-484774252 using your GitHub account
Received on Friday, 19 April 2019 05:46:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC