[Bug 12839] @id: Define how Unicode normalization affects the 'unique identifier' status

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12839

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi

--- Comment #2 from Henri Sivonen <hsivonen@iki.fi> 2011-06-01 10:12:59 UTC ---
I request resolving this by comparing identifiers code-point-for-code-point
without normalization before comparison. 

(In reply to comment #0)
> private tests of today's user agents (IE8, Firefox4, Opera11, Safari, Chrome)
> shows that
> 
> that <a href="#a&#x30a;">link</a> targets <p id="&#xe5;">
> whereas <a href="#&#xe5;">link</a> targets <p id="&#xe5;">

Are you sure you meant exactly what you wrote? You next paragraph suggests that
you didn't?

> Thus, today's user agents do actually treat them as unique identifiers, despite
> that they both refer to the same "å" (&#xe5;).  
> 
> However, in order toi avoid author confusion as well as user confusion, this
> should not be considered valid.

Until very recently, Validator.nu treated failure to be in NFC as an error. Now
it treats it as a warning, because there was no normative trail from HTML5 to
charmod-norm C300.

Note to Hixie: If you contemplate adding a normative trail to charmod-norm
C300, I suggest pinging the W3C i18n group first, since they might not like
what charmod-norm says anymore.

-- 
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 Wednesday, 1 June 2011 10:13:03 UTC