Re: some case-insensitivity cases to test

On Wed, 12 Dec 2012 15:10:35 +0100, Leif Halvard Silli  
<xn--mlform-iua@målform.no> wrote:

> John Daggett, Wed, 12 Dec 2012 05:10:46 -0800 (PST):
>
>>>  * HTML tag names, attribute names, and attribute values, e.g.:
>>>      <input> vs <ınput> etc.
>>>      <select multiple> vs <select multıple> etc.
>>>      <input type="radio"> vs <input type="radıo"> etc.
>>
>>   http://people.mozilla.org/~jdaggett/tests/casesensitivity-tagnames.html
>
> I checked the above page. And mark element test, where the k has been
> replaced with a  kelvin-K, is buggy. The test says "highlighted if
> matched". And in Safari, it gets highlighted. However, when you look at
> the DOM in the Inspector, then it is evident that it is not the kelvin
> K but the normal, lower-case k that is used in the element. (So
> javascript apparently replaces the kelvin K with the normal k.) If we
> revise the the results due to this error, then it seems that
> Chrome/Safari behave like IE10 and FF. My suspicion is that it is the
> same issue in Opera (Dragonfly would not open).

It's not clear to me what exactly this test is intended to check, but yes  
- in Opera, like in Chrome/Safari, document.createElement in HTML context  
converts the kelvin sign to lowercase k. The HTML parsers do not (kelvin  
sign is preserved if used in tags in the static document source).

Looking at the DOM tree as displayed in inspectors doesn't really work,  
though, they seem to do some normalization/conversion of their own. (This  
includes Firebug and Firefox' built-in inspector.) I used localName  
instead (e.g. element.localName.charCodeAt(3).toString(16) which gives  
212a for kelvin sign and 6b for lowercase k).

-- 
Øyvind Stenhaug
Opera Software ASA

Received on Wednesday, 12 December 2012 15:17:39 UTC