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

Re: [csswg-drafts] [CSS-appearance] Should we not use it, for now?

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Wed, 15 Nov 2017 01:20:18 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-344454987-1510708817-sysbot+gh@w3.org>
"not ready for shipping" is information for web browser implementers, not for authors. The vendor-prefixed variant of appearance has issues, so we don't want the standard one to be the same. But we haven't finished figuring out how the standard one should work, so browser vendors engineers should read the spec to think about the problem and give feedback, not jump straight into implementing a half baked idea.

In the meanwhile, authors can use the vendor prefixed versions. For simple uses, that will probably be fine. For more complicated ones, you may have a harder time getting things to work the same on all browsers. Which is why we're trying to come up with a standard alternative, but we're not done yet.

Until we've found a solution that works, and browsers have agreed to implement it, and have implemented it, and enough authors have used it that removing it would break lots of sites, there's unfortunately no way to promise that it will never be removed. It is not our current intention to remove it, but if we fail to make a sensible standard version, who knows.

Either way, you should generally not write code that depend on the future unprefixed property to behave the way you think (based on the current state of the spec) it will, as there's not guarantee until it actually happens.

GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1982#issuecomment-344454987 using your GitHub account
Received on Wednesday, 15 November 2017 01:20:20 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:44 UTC