W3C home > Mailing lists > Public > public-html@w3.org > February 2008

Re: Validation error frequencies

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Sat, 23 Feb 2008 16:43:10 +0100
Message-ID: <47C03F0E.3050402@students.cs.uu.nl>
To: "Michael A. Puls II" <shadow2531@gmail.com>
CC: Henri Sivonen <hsivonen@iki.fi>, Geoffrey Sneddon <foolistbar@googlemail.com>, Sam Ruby <rubys@us.ibm.com>, HTML Issue Tracking WG <public-html@w3.org>
Michael,

Instead of .getAttribute('href'), try seeing what kind of result you get 
by using .getAttribute('href', 2). In Internet Explorer, by this means 
you can get the attribute as it was specified on the document.


~Grauw

Michael A. Puls II schreef:
> On 2/2/08, Henri Sivonen <hsivonen@iki.fi> wrote:
>   
>> On Feb 2, 2008, at 16:19, Geoffrey Sneddon wrote:
>>
>>     
>>> Henri, were you meaning to make it conformant or just defining
>>> behaviour of spaces in IRIs?
>>>       
>> I meant researching how browsers cope with unescaped U+0020 in IRIs,
>> specifying what is interoperable, identifying what interoperable cases
>> are practically harmless and making those conforming.
>>     
>
> Are you looking for info like the following?
>
> input: <a href=" http://www.example.com/√/with spaces/script
> name.ext?uni=√&with spaces=with spaces ">test</a>
>
> Here's the output in different browsers. (.href first and then
> .getAttribute("href"))
>
> Opera:
> "http://www.example.com/√/with%20spaces/script%20name.ext?uni=%E2%88%9A&with%20spaces=with%20spaces"
> " http://www.example.com/√/with spaces/script name.ext?uni=√&with
> spaces=with spaces "
>
> IE:
> "http://www.example.com/√/with%20spaces/script%20name.ext?uni=√&with
> spaces=with spaces"
> "http://www.example.com/√/with%20spaces/script%20name.ext?uni=√&with
> spaces=with spaces"
>
> Firefox:
> "http://www.example.com/%E2%88%9A/with%20spaces/script%20name.ext?uni=%E2%88%9A&with%20spaces=with%20spaces"
> " http://www.example.com/√/with spaces/script name.ext?uni=√&with
> spaces=with spaces "
>
> Safari:
> "http://www.example.com/%E2%88%9A/with%20spaces/script%20name.ext?uni=%E2%88%9A&with%20spaces=with%20spaces"
> " http://www.example.com/√/with spaces/script name.ext?uni=√&with
> spaces=with spaces "
>
> For .href,
>
> Leading and trailing raw spaces are stripped in all 4 browsers.
>
> Raw spaces in directory names are converted to %20 in all 4.
>
> Raw spaces in hvalues and hnames are converted to %20 in Opera,
> Firefox and Safari, but not IE.
>
> Wide characters in hvalues and hnames are converted to their
> corresponding %HH sequence in Opera, Firefox and Safari, but not IE.
>
> Wide characters in directory names are converted to their
> corresponding %HH in Firefox and Safari, but not in IE and Opera.
>
> For getAttribute,
>
> Firefox, Opera and Safari give the actual value as it was in the
> source. IE gives the same (at least in this case) as .href.
>
> There are other things to check like leading and trailing raw spaces
> in directory names and  in hvalues and hnames because those might get
> stripped by some browsers also.
>
> Btw, if you look at the source of <
> http://revision3.com/diggnation/2008-01-31tokenuser/ >, you'll see
> that the Thumb and File hvalues in the embed src URIs are not escaped
> properly, which is also the case for the markup they give others to
> embed on their own site.
>
>   


-- 
Ushiko-san! Kimi wa doushite, Ushiko-san nan da!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Laurens Holst, student, university of Utrecht, the Netherlands.
Website: www.grauw.nl. Backbase employee; www.backbase.com.



Received on Saturday, 23 February 2008 15:43:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:52 UTC