W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2018

Re: [csswg-drafts] [cssom] Spec no longer defines the general "shortest serialization" principle

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 14 Feb 2018 17:20:36 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-365680255-1518628835-sysbot+gh@w3.org>
The Working Group just discussed `[cssom] Spec no longer defines the general "shortest serialization" principle`, and agreed to the following resolutions:

* `RESOLVED: add serialization principles to cssom`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [cssom] Spec no longer defines the general "shortest serialization" principle<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1564<br>
&lt;dael> fantasai: main issue is we need someone to make edits. There's no active editor. This keeps coming up as some editor is confused as to why FF serializes different and it's because this isn't in the spec.<br>
&lt;dael> fantasai: Can we assign somebody to do the edits?<br>
&lt;dael> astearns: There's the edits to re-introduce the shortest serialization and the other preinciples dbaron mentioned.<br>
&lt;dael> fantasai: Yes, they should all be in the spec but no one is owning them.<br>
&lt;dael> astearns: I would love to have an editor for CSSOM. I've been trying to recruit one. Anyone on the call willing to volunteer.<br>
&lt;dael> TabAtkins: I can do particular issues, but not the new general editor<br>
&lt;dael> astearns: Can we tasks you to add the principles in the issue? Just this edit.<br>
&lt;dael> TabAtkins: Absolutely.<br>
&lt;dael> tantek: Not volunteering. Do we have a label for something like PR desired where there isn't someone assigned but we'd welcome someone to do a PR for this item?<br>
&lt;Chris> "Good first issue"<br>
&lt;dael> astearns: We don't but it would be good. A first issue tag for easy thigns would also be good for someone new.<br>
&lt;dael> florian: We have edits needed, but doesn't distinguish.<br>
&lt;dael> tantek: This is a callout to a volunteer stepping forward instead of saying this is the a to do list.<br>
&lt;dael> tantek: This is a good example where it's non-normative text where it's a easy first edit.<br>
&lt;dael> fantasai: This isn't non-normative<br>
&lt;dael> tantek: Reading dbaron text it sounded like it's non-normative<br>
&lt;dael> TabAtkins: This is in the guideline of things where we really want to say it normative but there's too many variations. THis needs an experienced editor<br>
&lt;dael> florian: The principle of tantek ask is sound<br>
&lt;dael> fantasai: Spec is normative and will say there are exceptions. For properties should should be able to apply these and get correct serialization<br>
&lt;dael> tantek: I think enough text is in there that a new person culd do a decent PR. This is the kind of edit I'd welcome someone taking a shot at. Anyway. Didn't mean to sidetrack<br>
&lt;dael> astearns: It would be good to have a tag saying outside submissions welcome and a tag that says this is unassigned and we don't have an editor.<br>
&lt;dael> TabAtkins: Agree to both<br>
&lt;dael> action TabAtkins to make the edits in https://github.com/w3c/csswg-drafts/issues/1564<br>
&lt;trackbot> Created ACTION-867 - Make the edits in https://github.com/w3c/csswg-drafts/issues/1564 [on Tab Atkins Jr. - due 2018-02-21].<br>
&lt;dbaron> I think this is the sort of edit where I'm likely to have substantive disagreements with draft text by Tab, and Tab would be likely to have substantive disagreements with draft text by me.<br>
&lt;dael> action astearns to come up with new tags for new edits<br>
&lt;trackbot> Created ACTION-868 - Come up with new tags for new edits [on Alan Stearns - due 2018-02-21].<br>
&lt;krit> +present<br>
&lt;dael> astearns: objections to putting these principles into cssom?<br>
&lt;dael> RESOLVED: add serialization principles to cssom<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1564#issuecomment-365680255 using your GitHub account
Received on Wednesday, 14 February 2018 17:20:40 UTC

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