[Webkit-unassigned] [Bug 83930] Fragment navigation does not work properly when the fragment identifier contain hex values

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=83930





--- Comment #7 from Pravin D <pravind.2k4 at gmail.com>  2012-04-16 10:26:47 PST ---
Here is the link to the spec that talks about fragment navigation:
http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#scroll-to-fragid

The algorithm for fragment navigation is given in 7 steps. Webkit adheres to them expect for step 4 and 5.

These steps can be broken into 2 parts each:
Step 4 
a. Use hex decoded fragId.
b. Find an element whose id attr matches this decoded value.
If not found do step 5

Step 5
a. Use original fragId(non-decoded).
b. Find an anchor element(<a>) whose name attr matches this value.


Currently Webkit does the following:

A .Use original fragId 
B. find an element whose id attr matches this value or find an anchor tag whose name attr matches this value.

If not found Use the decode the fragId and do step (B).

So on webkit the steps 4.a and 5.a are swapped and 4.b and 5.b are not followed properly.


As I was not sure how closely we have to adhere to the above spec , I have uploaded a patch iwhich does the following:

X .Use decoded fragId 
Y. find an element whose id attr matches this value or find and anchor tag whose name matches this value.

If not found Use the original fragId and do step (Y).

Also contains 2 testcases to verify the same.

Please let know how to proceed about....

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.