New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
window.location.replace('#anchor') FAIL #1584
Comments
Here's a simple testcase: https://gist.github.com/3066765 It's also interesting to note that |
Confirmed. But I agree, it seems upstream. I don't know of anything we're doing that could cause this. But if Scriptish works, it kinda means we are doing something wrong. |
The reason this works in Scriptish is because they use an |
Interesting. Feels like a broken side-effect workaround rather than a fix. But most importantly, what does "Sent immediately after a web content document window has been set up, but before any script code has been executed." actually mean? That doesn't sound like DOMContentLoaded very much. |
Actually what I said in my earlier comment isn't quite correct. Scriptish uses the |
Do you know why this works around the bug? |
I'm pretty sure it's just coincidence. I've created a minimal addon to show that this is indeed an upstream bug: This addon does two things:
As expected, when visiting This should prove that the problem is indeed an upstream bug and not caused by Greasemonkey. The fact that Scriptish is not affected by this bug is simply because the bug only appears when calling |
Code:
Result:
All browsers and Firefox13+Scriptish 0.1.7 produces URL
http://sample.com/#anchor
Firefox13+GM 0.9.20 produces URL
chrome://browser/content/browser.xul#anchor
The text was updated successfully, but these errors were encountered: