Foteos Macrides wrote: > Foteos Macrides wrote: >> Although the >> https://bugzilla.mozilla.org/show_bug.cgi?id=156211 >> discussion claims that alternative entities such as   or   >> could be used [snip] > > That bug was marked RESOLVED INVALID based on the developers' view that the > Geckos are respecting the Unicode Standard Annex #14: > > http://www.unicode.org/reports/tr14/tr14-19.html > > by treating (U+00A0 NO-BREAK SPACE) as indeed NON-BREAKING but still > subject to expansion when a text-align:justify; CSS rule is being applied. > > Note, however, that Annex #14 also states that though the other spacing > entities such as   (U+2002 EN SPACE) and   (U+2002 EM SPACE) are > not subject to expansion, they still are BREAKING. Firefox is treating them > as non-expanding, but both are MUCH wider than U+0020 (ASCII space) or > U+00A0. Moreover, Firefox is not in fact respecting Annex #14 because it is > treating those other spacing entities as NON-BREAKING.. The other modern > browsers do treat them as non-expanding but BREAKING. > > In general, the Geckos not only aren't fully respecting Annex #14 as > imagined, but couldn't be more at odds with the other modern browsers in > this matter.
Most of the line breaking rules in UAX 14 are non-normative. The line breaking opportunities defined by UAX 14 are just a suggestion. Most of UAX 14 is effectively informative. This includes notes on justification behavior. However, note that nbsp decomposes to space + non-breaking behavior. It is expected to render exactly the same as a space character: the only difference is that it doesn't allow line breaks. ~fantasai _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
