- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jul 2017 16:55:20 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Exclude 'none' from <counter-style-name>`, and agreed to the following resolutions: * `RESOLVED: Accept the edits proposed in https://github.com/w3c/csswg-drafts/issues/1295` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Exclude 'none' from <counter-style-name><br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1295<br> <dael> Rossen_: Who is on the call from this convo? Simon?<br> <TabAtkins> The specced thing is definitely *better*, no question. And it's what I designed the FontFace object after, not knowing the spec didn't match reality. But we need someone to actually make the change and show it's web-compatible.<br> <dael> fantasai: This was filed a while ago about dealing with none value. This was with SimonSapin & Xidorn about excluding none from <counter-style-name> Edits are checked in, it's on the agenda to check they're okay b/c i t's a change to CR spec.<br> <dael> fantasai: Otherwise we should resolve to accept edits and republish counter styles.<br> <fantasai> well, I guess there are two more issue son counter styles<br> <fantasai> to resolve before republishing<br> <Rossen_> https://github.com/servo/servo/commit/04aaef8b3d0bc12ad5d2d5c9ecf003c016928a30<br> <dael> Rossen_: I'm trying to find the edits. Is this the edit ^?<br> <fantasai> DoC: https://drafts.csswg.org/css-counter-styles-3/issues-cr-20150611<br> <AmeliaBR> Weren't there other changes about disallowed names? Decimal and circle, or something like that? Have they already been approved or deferred?<br> <fantasai> Looks like the changes are here : https://github.com/w3c/csswg-drafts/pull/1326/commits/07ca44199bda55b7d24a3d1ccc8c8a342a324c99<br> <dael> Rossen_: For this issue, #12 in DoC....<br> <dael> Rossen_: Excluding none from <counter-styles-name> will this reset the CR? I missed the consiquence of accepting the edit<br> <dael> fantasai: It's a substantive change to a CR spec so we need WG approval for the change.<br> <dael> Rossen_: Did anyone get to review? Does anyone have an opinion?<br> <dael> Rossen_: Se we can resolve on the committed change and reset the CR of CSS counters.<br> <fremy> (I just gave this a read, I think this is reasonable change; sounds ok)<br> <fantasai> https://drafts.csswg.org/css-counter-styles/issues-cr-20150611#issue-7<br> <dael> fantasai: Theres' 2 more issues on counter styles before we repub. 2 more substantive. 1 is included in thechange set whichis computing undeclared to decimals. Last one is involving i18n and a11y so we'll have to liase with those groups.<br> <dael> Rossen_: tantek you seems to be reviewing. Interesting in a good way from you. fremy seems to support.<br> <dael> Rossen_: Should we resolve or is anyone else looking?<br> <Rossen_> https://wiki.csswg.org/planning/paris-2017#proposed-agenda-topics<br> <dael> Rossen_: While everyone reviews, I want to remind people to add topics to the F2F agenda ^<br> <dael> Rossen_: Please add agenda items.<br> <dael> Rossen_: tantek supports it. Thanks for reviewing.<br> <dael> Rossen_: Other opinions before I CFC?<br> <dael> Rossen_: Objections to accepting the edits for https://github.com/w3c/csswg-drafts/issues/1295 ?<br> <dael> RESOLVED: Accept the edits proposed in https://github.com/w3c/csswg-drafts/issues/1295<br> <dael> Rossen_: That's the top of the agenda.<br> <dael> Rossen_: Any other quick topics? Or should we reclaim 5 min?<br> <tantek> agenda?<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1295#issuecomment-318115686 using your GitHub account
Received on Wednesday, 26 July 2017 16:55:24 UTC