User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.65 Safari/537.36
Steps to reproduce:
I nested an iframe inside an iframe. In the inner iframe, I included a button that calls `window.history.pushState({}, "some title", "somepage.html");`
Now go to the page in a new tab and click the button.
(This problem does not occur for only one iframe (N=1), only when nesting two or more. See the problem in action at http://janpaulposma.nl/pushstate-firefox-bug/)
Actual results:
Only when clicking the button for the second time does the interface change. Before, the back button is greyed out. After one click, it is still greyed out. After another click, it becomes active. When clicking and holding, it does show the intermediate state (first click) as well!
Expected results:
The interface should have updated on the first click, ie. the back button of the browser should have become active on the first click.
|
||
Updated•4 years ago
|
||
|
(Reporter) | |
Comment 1•4 years ago
|
||
By the way, this is the source code: https://github.com/janpaul123/pushstate-firefox-bug
|
||
Comment 2•4 years ago
|
||
Regression window Good: http://hg.mozilla.org/mozilla-central/rev/7cc523f32f98 Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100501 Minefield/3.7a5pre ID:20100501210322 Bad: http://hg.mozilla.org/mozilla-central/rev/02e1305294bd Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100502 Minefield/3.7a5pre ID:20100502040440 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7cc523f32f98&tochange=02e1305294bd Regressed by: Bug 554155
|
|
(Reporter) | |
Comment 3•4 months ago
|
||
This seems to be fixed now!
Description
•