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

Re: [csswg-drafts] [css-logical-1] [css-cascade-3] The all longhand probably shouldn't set logical properties.

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Oct 2017 06:52:17 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-338891808-1508827936-sysbot+gh@w3.org>
> Other than this, I think the result would always be as expected if you used `removeProperty` just before `setProperty`. Would it be backwards-compatible if CSSOM automatically did this?

Maybe... I somehow think the current behavior makes more sense than always appending the changed declaration... except when it interacts with shorthands and logical properties...

Probably what we can do is:
* define the expand order for shorthands
* have CSSOM remove all longhands including their corresponding logical properties from the declaration block when it is setting a shorthand

With the first, we would have interoperable deterministic result, and with the second, the result should be less surprising when people try to set shorthand when some longhands have been there.

GitHub Notification of comment by upsuper
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1898#issuecomment-338891808 using your GitHub account
Received on Tuesday, 24 October 2017 06:52:18 UTC

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