- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Mar 2018 16:14:12 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `white-space collapse at end of line: test case and queries`, and agreed to the following resolutions: * `RESOLVED: spec Gecko's behavior at the ends of lines in display text?` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: white-space collapse at end of line: test case and queries<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1997<br> <dael> florian: I can try and cover for fantasai<br> <dael> florian: If she's not here.<br> <dael> fantasai: I'm here.<br> <dael> fantasai: There's inline box bounderies that prevent the whitespace from collapsing at the end of the line for certain impl.<br> <dael> fantasai: You can see from the example in the issue.<br> <dael> fantasai: Question is will we collapse all consequitive spaces and we have the end of the line and after the space the inline tag closes. Does the space at the end collapse even though there's an inline box boundary. I say yes for the reasons in the comment.<br> <dael> astearns: Looks like we will have interop with Gecko, upcoming Blink, upcoming Edge.<br> <dael> fantasai: I don't remember the Blink testcase, but we will have some engines that do that.<br> <dael> fantasai: An important reason to do this is authors will expect this. When closing tags aren't tight against the last it just hangs out and it's unexpected. havging a space hanging out inside be different then outside doesn't make a whole lot of sense.<br> <dael> astearns: Any concerns with trimming the trailing psace?<br> <dael> florian: Agree<br> <dael> myles: I don't quiteunderstand the test case. I thought spec was all trimmed except the first. So the space shown isn't from inside the span? Maybe I should take this offline<br> <dael> fantasai: Space is after the first. If you have a series fo collapsable spaces the first is preserved.<br> <dael> myles: It's before the span with the border-left in the firstline<br> <dael> fantasai: Test cases have checks for before the text and after. Whitespace does 2 phases, one go down to one space and then go through the line and any space adjacent to start or end is trimmed.<br> <dael> myles: Let's take this offline. Resolution is fine.<br> <dael> Rossen_: You're okay to resolve on current behavior and continue to define?<br> <dael> myles: I'm a little confused about the test case, but in the issue there was a proposed resolution to use the FF behavior.<br> <dael> Rossen_: I would point out that even though you'll get similar renderings with at least our current work in progress as well as what I'm assuming the NG layout is aiming for in Chrome. I can't speak to webkit. As soon as you start interacting with this particular test case in content: editable or you select it, you get very different behavior.<br> <dael> Rossen_: I'm not sure how much this resolution captures this.<br> <dael> florian: I thinkt he problem of having more divergence as to what happened to spaces when you select them goes way beyond this test case. We probably should tackle that sep.<br> <dael> Rossen_: My point is we should either, ideally have a note for this or test cases that involve selection. Something that allows us to proceed forward more interop. I think we've discussed extensively in the past and made some progress.<br> <dael> Rossen_: I want to point out this issue doesn't address any of that.<br> <dael> florian: That's fair and this is something I'm interested in looking into. I'll try and see what the spec says about when selecting and editing. It's separate, but I want to look into it.<br> <dael> astearns: Setting content editable and selection aside, it sounds likew e're converging on Gecko's behavior for trimming at the end of lines for displayed test<br> <dael> astearns: Objections to spec Gecko's behavior at the ends of lines in display test?<br> <dael> RESOLVED: spec Gecko's behavior at the ends of lines in display text?<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1997#issuecomment-374998740 using your GitHub account
Received on Wednesday, 21 March 2018 16:14:17 UTC