[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 #9 from Pravin D <pravind.2k4 at gmail.com>  2012-04-16 13:38:41 PST ---
(In reply to comment #8)
> How did you make the decision that we should fix WebKit, and not the spec?
> 
> I don't oppose the proposed change per se, but we need stronger rationale to know whether this is something we'll stand behind. For example, if we take this change and it breaks an important site, will we be willing to roll it out? And what if it's an unimportant site?

Just for information sake:

Tracked the logic used in the function to this 
http://trac.webkit.org/changeset/6479/trunk/WebCore/khtml/khtml_part.cpp

This is the beginning of the the gotoAnchor() function which is now changed to scrollToAnchor()... 

As for the logic used for scrolling to anchor seems to part of kde code base...
http://trac.webkit.org/browser/trunk/WebCore/khtml/khtml_part.cpp?rev=1035

Anyways the only rationale that i have to offer is that this part of the code pretty old and won't do much harm if someone poked it and bring it in terms with the current Web world...

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