[csswg-drafts] [css-text] hanging punctuation: ink vs scrollable overflow

frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-text] hanging punctuation: ink vs scrollable overflow ==
[original mail thread starts here (sub-point 6)](https://lists.w3.org/Archives/Public/www-style/2016Mar/0073.html)

key arguments for and against:

----

> The WG resolved overflow is ink overflow. I think it should be scrollable overflow. I can elaborate on this if needed, but it’s a selectable character that has to be reachable when edited and cut/copied etc. Any designer is going to leave space for hanging punctuation if they turn it on, so fears of scrollbars are unfounded IMO. It’s also an annoying amount of additional work to treat that as ink overflow when the common sense implementation just moves the line box (and line boxes are scrollable overflow obviously). This is similar to text-indent, which creates layout overflow when negative, so it’s not clear to me why hanging punctuation can’t behave the same way. 

----

> The reason that we decided to make it an ink overflow is that, many
> punctuations in CJK are full-width while their ink just takes less than
> half of the space. It is especially true for Simplified Chinese and
> Japanese, for stop and comma. It means that, it is completely fine to have
> a space which is enough to show the ink but not enough from the metrics.
> Making hanging punctuation scrollable overflow could confuse people in this
> reasonable usecase.

----

Also, we've made preserved white-space at the end of a line be treated as hanging for the specific purposed of having it be ink overflow.

----

I would suggest:
* must be treated as ink overflow in the general case
* must be treated as scrollable overflow when editable

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2398 using your GitHub account

Received on Monday, 5 March 2018 08:45:48 UTC