W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [cssom-1] Replace steps of set a CSS declaration with some constraints

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Jul 2018 11:31:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-406245244-1531999918-sysbot+gh@w3.org>
> Feel free to merge this, probably after #2922 lands as well.

I think we should have that landed first.

> So what's the current behaviour? How interoperable are they?

Current behavior is to always update existing declaration with the same property name. I believe at least Blink and Gecko both do this, likely WebKit as well. Edge may have some other idea.

Blink (and probably WebKit as well) doesn't trigger mutation observer if the value and flag aren't changed, while Gecko did. That caused performance issue for us and thus we fixed that in 62 or 63.

> What would it take to converge behaviour in some other way to what we previously resolved in #1898?

I don't think we are going to use the algorithm we previously resolved in #1898 because that has webcompat issue.

We may eventually converge to some algorithm, but it's probably not going to happen very soon, as a conformant algorithm without webcompat issue is going to be somewhat complicated, and getting everyone agree on every details could take quite a bit of time.

Also there are other stuff currently in my mind that we should probably add to this constraints which may make things more complicated...

-- 
GitHub Notification of comment by upsuper
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/2924#issuecomment-406245244 using your GitHub account
Received on Thursday, 19 July 2018 11:32:01 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 July 2018 11:32:05 UTC