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

Re: [csswg-drafts] [css-text] Question re white space processing rules for U+000D

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Jul 2018 06:04:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402022954-1530597853-sysbot+gh@w3.org>
The Working Group just discussed `form feeds and carriage returns`, and agreed to the following:

* `RESOLVED: revert the previous lone cr resolution, and treat it as any control character`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> topic: form feeds and carriage returns<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/855<br>
&lt;frremy> florian: In Berlin, we made two conflicting resolutions without noticing<br>
&lt;frremy> florian: frremy noticed after, and raised that<br>
&lt;frremy> florian: one is that we should render control characters<br>
&lt;frremy> florian: two is that cr should not be rendered<br>
&lt;frremy> florian: that is not very consistent, we didn't need to specialize cr given the first resolution<br>
&lt;frremy> florian: no strong opinion, but we could change this<br>
&lt;fantasai> frremy: Edge already does render the CR block<br>
&lt;fantasai> frremy: I thought rndering of chars was not enabled, but Rossen enabled it, but ...<br>
&lt;fantasai> frremy: I'm proposing to move to Edge behavior, consistent with first resolution<br>
&lt;frremy> myles: is there a proposal?<br>
&lt;fantasai> florian: Proposal is discard resolution about treating CRs specially, treat them just like any other control character<br>
&lt;frremy> florian: rescede the resolution we made for lone CR<br>
&lt;frremy> florian: then the resolution we made for control chars will apply<br>
&lt;frremy> astearns: i like the consistent behavior<br>
&lt;frremy> heycam: I'm fine with that<br>
&lt;frremy> florian: is there anybody objecting?<br>
&lt;frremy> (no objection)<br>
&lt;frremy> RESOLVED: revert the previous lone cr resolution, and treat it as any control character<br>
&lt;frremy> dbaron: we don't think there is much content like this?<br>
&lt;frremy> myles: no, because it would be converted by the html parser<br>
&lt;frremy> myles: so the only way would be a script doing that<br>
&lt;frremy> myles: I haven't seen it<br>
&lt;frremy> florian: does the javascript parser also does that?<br>
&lt;frremy> frremy: you can't have line breaks in string<br>
&lt;frremy> xidorn: but with backticks you can<br>
&lt;frremy> florian: nobody is going to be writing es6 code on a OS 8 mac<br>
&lt;frremy> dbaron: OS 9 does something even different<br>
&lt;frremy> (general agreement it should be rare enough)<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/855#issuecomment-402022954 using your GitHub account
Received on Tuesday, 3 July 2018 06:04:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 July 2018 06:04:41 UTC