- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Feb 2018 19:47:44 +0000
- To: public-css-archive@w3.org
I have the feeling that an API like `getComputedStyle` should always return the same result independently of the realm you are calling from. It just doesn't make sense otherwise. This is another reason why you don't want to apply the document's stylesheets on nodes that are currently in a detached tree, because it yields inconsistent results depending on your current realm. Edge's behavior guarantees stable results for identical detached markups in different documents since we only apply inline styles and the default style on these elements. > What happens when that node document is an XHR responseXML or equivalent? How does where you document comes from matter? In Edge at least, it is perfectly fine to interpret any xml document as a stylable document (xhtml by default). In fact, when you open an XML file in a tab, we render the XML file directly (though we add a script to append XHTML nodes to it so there is something more interesting to render than inline text). https://jsfiddle.net/0fgm1rgw/ > Also, an element can be in the document tree but not be on the flat tree There is indeed also the question of what to do with nodes that do not have used styles. I don't think there should be special sub-categories inside that category; nodes that do not generate a box (whether it's because one of their ancestors is display:none, because they were moved into a region flow and overflowed beyond the last region box, or because they were under a web components and didn't get pulled back into its shadow tree) should return their computed style, and their computed style should follow the same rules as usual (inherit from its parent element, or host if it's a shadow root, etc...). If that is not the case right now in some browsers, I would file bugs on the browsers that don't comply with this. Everybody seems to be interoperable regarding nodes in display:none subtrees. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1548#issuecomment-363888452 using your GitHub account
Received on Wednesday, 7 February 2018 19:47:49 UTC