- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Jan 2019 17:41:38 +0000
- To: public-css-archive@w3.org
Per https://www.chromestatus.com/features/schedule 72 reached stable yesterday, but I suppose it needs a few more days before the stats are accurate?
> If the counter value is low, Chromium project will try to remove all such values.
OK, but the values specified in this PR all have *some* usage based on httparchive analysis, in some cases on `select` elements, with the expectation to have the dropdown arrow removed (and apply custom styles).
Examples:
* `select{-webkit-appearance:caret;background-image:url("images/icon_arrow_down_blue.svg");background-position:95% center;background-repeat:no-repeat;-webkit-background-size:16px 16px;-moz-background-size:16px 16px;background-size:16px 16px;outline:none}`
* `.select-wrapper .select-inner select{position:absolute;z-index:999;top:0;left:0;height:100%;width:100%;margin:0;padding:0;border:0;opacity:0;background:url("/content/images/select_bknd_transparent.png");visibility:visible;-webkit-appearance:menulist-text}`
Not parsing these values at all would have such `select` elements either have `menulist` or `menulist-button` appearance, breaking the intended custom style. Therefore I think it is less likely to break such web pages if the keywords in this PR are aliases to `none`.
--
GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/3529#issuecomment-459038401 using your GitHub account
Received on Wednesday, 30 January 2019 17:41:39 UTC