W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14360] Count Unicode 'combining marks" together with "inter-element whitespace"

From: <bugzilla@jessica.w3.org>
Date: Thu, 06 Oct 2011 23:06:57 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RBx1l-0000M6-LF@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
         AssignedTo|ian@hixie.ch                |contributor@whatwg.org

--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-06 23:06:53 UTC ---
> <http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1174>

Do you have a minimised example? I can't make heads or tails of this page.

> The demo shows tha combining marks, when "alone", move outside the left border
> of the element, as if it combines with something that is outside the element.

I don't see what this has to do with HTML. It's a rendering issue; either an
issue to bring up with the CSS working group or with the browser vendors.

> W.r.t. my subsequent reply to your comment, then look at the "inline-block"
> examples at the bottom of the following demo: <http://tinyurl.com/5stsb7r>.

I can't work out what's going on on that page.

> When I flesh it out a bit more, that demo has this code:
> <p>�<span style="display:inline-block">&#x0020;&#x20DC;</span>
>    Despite the space between the '�' and the combining character, the combining
> character combines with the '�'.  This, I said is fine. Only if we removed the
> "�", would there be a problem as then there would be nothing to combine with:
> <p><span style="display:inline-block">&#x0020;&#x20DC;</span>

I don't understand the problem here. Unicode is clear about what you do with
isolated combining characters.

> NOTE 1: This bug is filed against the 'Flow content' section, where you give a
> description of the  general rule of what """elements whose content model allows
> any flow content""" as a minimum **should** contain.

Actually that's been moved into its own section now.

> The spec says that the
> minimum is not a strict rule: 'not a hard requirement'. And I simply would like
> that this "not hard requirement" is stretched to include combining characters
> too. 

I don't see why they need mentioning at all.

>       Btw, conformance checkers do not display a warning if e.g. the <body>
> element is emtpy, and so it did not need to to actually warn in case the <body>
> only contains a combining mark either ... It would be enough for me if the spec
> explained that an element "whose content model allows any flow content", is
> more than spaces and combining marks.

What's wrong with just having an isolated combining mark? It's perfectly legal
per Unicode.

> NOTE 2: Do you disagree with the advice of Unicode6, that  authors, when they
> want to represent a combining character as if was an independent, spacing
> character, should combine with no-break space?  If you don't, how  can one get
> this authoring advice into the spec?

Why would we need to mention it at all? That's a Unicode issue.

> NOTE 3: It is not so that I that *my* proposal circumentvents all
> implementation bugs. Far the from. So it is not a proposal that seeks to
> circument implementation bugs. In fact, my proposal emphasizews that 

I've no idea what you're saying here.

> NOTE 3: Do I misunderstand "any flow content"? I read it as "every sort" but
> perhaps it is meant "some sort"?

I do not think you misunderstand it.

> NOTE 4: This variant of my previous demo, has dd:first-letter{white-space:pre}.
> And as you can see, this makes the line where there is a space plus a combining
> mark identical with the line where there is no-break space and a combining
> mark. However, the line where there is only a combining mark as first eltter,
> is not affected - given that not every implementation has CSS enabled, one
> can't rely on this:
> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1176

I have no idea how this is relevant to HTML.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 6 October 2011 23:07:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:05 UTC