- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Sep 2020 16:25:08 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text] Reconsider the resolution on #855`, and agreed to the following: * `RESOLVED: Treat CR as an ordinary space` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-text] Reconsider the resolution on #855<br> <oriol> emilio: Logical values computing as-is was resolved in https://github.com/w3c/csswg-drafts/issues/2821#issuecomment-415092595<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5410<br> <emilio> oriol: great, just wanted to make sure that there was a resolution on that, thanks!<br> <emilio> oriol: a bit odd that it behaves differently from logical props but maybe not too much :)<br> <fantasai> emilio, it would have been necessary for text-align to actually work as expected :)<br> <dael> florian: We resolved control characters are displayed visually. As part of that the CR character, carrage return, is supposed to be the same. Most of the time you can't notice b/c handled by HTML parser. But if you inject it you should see it. No one does it.<br> <emilio> fantasai: fair enough :)<br> <dael> florian: Mostly can't see, Chrome sometimes replaces with ordinary space. Did testing to see what kind of invisible people do. It's all over the place. Everyone does a weird varient<br> <dael> florian: Suggestion is treat as ordinary space. Depending on whitespace property it may be collapsable. Partially matches Chrome. When whitespace is normal Chrome does that. When whitespace is not normal Chrome does different things.<br> <dael> florian: Suggestion is from fantasai and I think it's good. This is kind of an error case<br> <dael> emilio: filed it b/c wikipedia was complaining. Not sure about nobody uses it<br> <dael> florian: Do they want it to do something?<br> <dael> emilio: No, Gecko was doing something more weird. I fixed that more weird but when I looked how to handle it was all over the place as you said.<br> <dael> florian: So I think you for the opportunity to write fun tests. Now that I've had my fun how about we change to a space and move on<br> <dael> s/think/thank<br> <dael> emilio: Okay with that but a change for all engines<br> <dael> florian: Yeah. In main case it's what Chrome does<br> <dael> chrishtr: #2 on yoru option list always?<br> <dael> florian: Yes. It behaves as any space on whitespace:pre<br> <dael> chrishtr: So Chrome just needs whitespace:pre to change?<br> <fantasai> proposed resolution is "treat as U+0020"<br> <dael> florian: Yeah, maybe other non-normal. I don't recall.<br> <dael> smfr: Makes me a little nervious b/c they're more common in mac.<br> <dael> florian: Yeah. Probably not shoing because actual carriage return is handled. It's an explicit escape<br> <dael> smfr: Worried files converted to user entities.<br> <dael> florian: Could. but what happens now is everybody is different<br> <dael> Rossen_: I see soft agreement by koji on issue. Sounds like emilio is fine for Gecko to try.<br> <dael> smfr: I won't object. I think we'd have to try it and see what happens<br> <dael> Rossen_: Let's try and resolve. If we see a lot more information saying this is causing crazy breaks we'll discuss again<br> <dael> florian: I think behavior in safari and FF isn't crazy but i could find so many ways to make something visual that this seemed a lot simpler<br> <dael> florian: Prop: Treat CR as an ordinary space<br> <dael> florian: I'll be more exact in spec<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: Treat CR as an ordinary space<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5410#issuecomment-693517255 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 September 2020 16:25:09 UTC