W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2017

[csswg-drafts] [cssom]Inline style manipulation is somewhere between underspecified and incorrectly specified

From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
Date: Fri, 23 Jun 2017 18:12:12 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-238215652-1498241530-sysbot+gh@w3.org>
bzbarsky has just created a new issue for https://github.com/w3c/csswg-drafts:

== [cssom]Inline style manipulation is somewhere between underspecified and incorrectly specified ==
A simple example.  Say we start at https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setproperty  and walk through the steps.  The property value is parsed, the new value is set, etc.  This is all fine.

But there's a comefrom bit in https://drafts.csswg.org/cssom/#the-elementcssinlinestyle-interface that says:

> Mutating the declarations must set the style content attribute on the context object to the serialization of the declarations. If the style content attribute is set, changed or removed, the declarations must be updated as appropriate.

Where does that fit into the above-linked algorithm?  Does it run inside https://drafts.csswg.org/cssom/#set-a-css-declaration and if so does it run after step 3 _and_ after step 4, or just after step 4, or something else?  This is observable via mutation observers.

Or does it run at all?  I'm pretty sure that in browsers mutating the inline style via CSSOM does NOT do a serialize-and-reparse thing.  And this is black-box distinguishable (in browsers; not sure about per spec, because the processing model for this stuff is somewhat underdefined in varuous other ways) from doing the serialize-and-reparse, as far as I can tell, if base URIs are changed.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1559 using your GitHub account
Received on Friday, 23 June 2017 18:12:18 UTC

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