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

Re: fragid navigation and pct-encoded

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 04 Sep 2008 22:56:04 +0200
To: "Thomas Broyer" <t.broyer@gmail.com>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <op.ugy5rqds64w2qv@annevk-t60.oslo.opera.com>

On Thu, 04 Sep 2008 15:55:17 +0200, Thomas Broyer <t.broyer@gmail.com>  
wrote:
> On Thu, Sep 4, 2008 at 3:05 PM, Anne van Kesteren wrote:
>> Apparently there are some differences between browsers in the handling  
>> of percent escaped characters in fragment identifiers. I made a few  
>> tests to figure out the different behavior:
>>
>>  http://tc.labs.opera.com/html/navigation/fragids/
>
> Raw results:
>
> In Chrome and Safari 3.1.2 on Windows (same results, unsurprisingly ;-)  
> ):
> Test 3 says A (as HTML5)
> Test 4 says B
> Test 8 says B

Hmm, so WebKit has a fourth algorithm? That is, first try if fragment  
works without handling pct-encoded and if that fails, try again with a  
pct-encoded fragment.


> BTW, have you tried with links within the same document? There
> shouldn't be any difference IMO but just in case...

I tested that a little bit, does not matter as far as I can tell.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Thursday, 4 September 2008 20:56:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:23 GMT