- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 May 2019 08:56:22 +0000
- To: public-css-archive@w3.org
Actually, on the surface it seems like this contradicts the spirit of #3886, where it was just resolved that "Inline box boundaries don't affect line breaking opportunities".
Consider:
data:text/html,<style>p{width:0}span{word-break:break-all}</style><p><span>foo</span><span>bar</span>
vs:
data:text/html,<style>p{width:0}span{word-break:break-all}</style><p><span>fo</span><span>ob</span><span>ar</span>
The only difference between these is where the boundaries of the inlines fall; the actual styles applied to all the text is the same in both. Yet Chrome (following the spec text as pointed out above) renders them differently, with pairs of characters stuck together at the span boundaries. Safari, OTOH, and also latest Firefox Nightly (since the patch in https://bugzilla.mozilla.org/show_bug.cgi?id=1507744), renders both examples the same, with no letter pairs stuck together.
--
GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3897#issuecomment-490818655 using your GitHub account
Received on Thursday, 9 May 2019 08:56:24 UTC