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

Re: [csswg-drafts] [cssom] Figure out what to do with non-standard CSSStyleSheet methods in WebKit / Blink (#3814)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 Apr 2019 16:54:00 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-486330911-1556124838-sysbot+gh@w3.org>
The CSS Working Group just discussed `Figure out what to do with non-standard CSSStyleSheet methods in WebKit / Blink`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Figure out what to do with non-standard CSSStyleSheet methods in WebKit / Blink<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3814<br>
&lt;dael> Rossen_: Anyone to take this?<br>
&lt;emilio> Given the comments, I'll just spec them<br>
&lt;dael> TabAtkins: Based on eric's numbers, unless someone can make argument that our numbers aren't actual usage they're too high to drop. .rules is almost a full % of page loads<br>
&lt;dael> TabAtkins: If not removing, should look to add. But emilio says no one cares on their side.  I don't know best thing, but removing isn't in the cards for us<br>
&lt;dael> AmeliaBR: Clarify impl of these they're aliases for standard features?<br>
&lt;dael> TabAtkins: There's one that's slightly different, but yes<br>
&lt;dael> dbaron: Will impl these in browsers that don't have them break?<br>
&lt;dbaron> s/break/break feature detection/<br>
&lt;dael> TabAtkins: Don't know. I jsut have use counter data, not information on how they're actually used. But numbers os use is too high<br>
&lt;dael> dbaron: Seems weird b/c I don't recall pages broken due to not having them<br>
&lt;dael> TabAtkins: Feature detection I didn't mean tell you're in blink but something that iterates over a bunch of properties to see what exists. That's caused high use counters in the past. THat might be the case at which point we might remove, but as of right now can't remove<br>
&lt;dael> Rossen_: Other action if we don't remove? Add to CSSOM?<br>
&lt;dael> TabAtkins: Not right now. emilio asked if should or should remove<br>
&lt;dael> Rossen_: Current data says cannot remove unless you want an action to see if you can get deeper into data to figure out if it's meaningful or triggering from aux. detection rules. Up to you<br>
&lt;dael> TabAtkins: Put it for triage. I'll get back to you<br>
&lt;dael> Rossen_: Reasonable.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3814#issuecomment-486330911 using your GitHub account
Received on Wednesday, 24 April 2019 16:54:01 UTC

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