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

Re: [csswg-drafts] [css-variables] Substitution of invalid variables into other variables (#4075)

From: andruud via GitHub <sysbot+gh@w3.org>
Date: Mon, 01 Jul 2019 17:51:10 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-507362325-1562003468-sysbot+gh@w3.org>
I think it would "only" cost us consistency. Can't think of any use-cases that would be limited (either way).

Your intuition is right that this adds confusion in the Houdiniverse; there has been at least [one report of confusion](https://github.com/w3c/css-houdini-drafts/issues/849), though here it probably doesn't help that I've implemented registered custom properties to work per spec, which adds another de-facto inconsistency with (the actual implementation of) unregistered custom properties.

Personally, I think we should at least _try_ to change browser behavior. I'm mostly fishing for whether there's a hidden CSSWG resolution / TPAC hallway discussion / Tab Atkins tweet / hivemind consensus that custom properties should work the way they actually do in browsers, and it just never reached the spec, or whether this was just an unlucky oversight during the creation of some WPT.

-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4075#issuecomment-507362325 using your GitHub account
Received on Monday, 1 July 2019 17:51:12 UTC

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