[css3-text] White space processing (was New WD of CSS Text Level 3

I hope this is the last question in your review, please let me know if I miss soething.

> Section 4 states
> Note that the document parser may have not only
> normalized segment breaks,
>
> How is the adjective "normalized" meant to be applied
> to "segment break"?

I think it can be removed, but let me check this with my co-editor.

> Are form feeds (U+000C?) explicitly NOT considered
> to be white space, and if so, should that be stated;
> how should they be handled, if at all?

Do you have any reason or real use cases to explicitly include it as white space? The "white space" here is not to be a general definition of white space but is a useful, interoperable, and backward compatible way for the UAs to handle source text. I don't think we should change this behavior unless it is absolutely necessary, as any changes can impact UA developers and HTML authors.

> I see "<span class="issue">Copied from CSS2.1
> but this has got to be wrong.</span>" -- for a minute,
> I thought that was part of the text!  I had to go into
> the source to see that it isn't.  I'll add a userstyle
> override on my side to make that a red background
> with white writing so I don't confuse those things...

I sent this to the CSS WG as a feedback, please stay tuned.

> Section 4.1:
> I see
>> Rename to white-space-trim or white-space-adjust?
> Out of the two, "adjust" seems to make more sense,
> since collapse and trim aren't the only options here;
> "white-space-behaviour" and "white-space-treatment"
> also seem viable.

Thank you for the feedback. I'll be talking to my co-editor about this soon.


Regards,
Koji

Received on Saturday, 19 February 2011 12:33:46 UTC