Skip to content

[css-text-3] unclear detail of white space collapsing? #3513

Closed

Description

@frivoal

Section 4.1 says:

Any space immediately following another collapsible space [...] is collapsed to have zero advance width.

Shouldn't that be:

Any collapsible space immediately following another collapsible space [...] is collapsed to have zero advance width.

I'd rather be a little redundant to avoid suggesting that sequences mixing collapsible and non collapsible space do collapse.

Activity

  1. self-assigned this
    on Jan 15, 2019
  2. fantasai commented on Jan 15, 2019

    @fantasai
    Collaborator

    It's pretty clear from the wording introducing this particular list. Also if we were to be redundant here, we'd need to be redundant in every other item of this list. Given that I think I lean towards not making the change here...

  3. frivoal commented on Jan 15, 2019

    @frivoal
    CollaboratorAuthor

    I wondered about this bit of sentence because I wanted to be sure what the spec said for cases like

    <span style=white-space:pre>a </span><span style=white-space:normal> b</span>

    or

    <span style=white-space:normal>a </span><span style=white-space:pre> b</span>

    collapse or not? I think the answer is not to collapse in both cases, but with the current phrasing, I wasn't 100% sure for case 2.

    we'd need to be redundant in every other item of this list

    Well, the entries on this list are supposed to be talking about collapsible spaces, so if there's only one mention of spaces in one entry, then surely it's about collapsible spaces. But this entry talks about spaces and collapsible spaces, and I couldn't be sure whether the commission of collapsible in one of the references but not the other was just because it was "obvious" from context, or if it was meant to draw a contrast. Hence filing this bug. The presence of the word "another" gives a good hint, so I won't be too sad if we close this as wontfix, but I'd prefer minimizing the chances of misunderstanding.

  4. fantasai commented on Jan 15, 2019

    @fantasai
    Collaborator

    I'd have to rewrite all the entries in that entire list. :/

  5. added
    Commenter SatisfiedCommenter has indicated satisfaction with the resolution / edits.
    on Jan 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions