Krinkle <> changed:

           What    |Removed                     |Added
           Assignee|           |

--- Comment #5 from Krinkle <> ---
It should be reliably reproducible on all of the above.

It happens when you access veaction=edit directly in the url on a fresh load.

Chrome has the nasty habit of firing a popstate event (sometimes?) on a regular
load that wasn't via the history.

This can be worked around by storing a piece of data with the state and using
that to tell events apart (to distinguish between a state pop to one we
pushed/replaced into the history, from a pop state to one some other
application pushed in or one the browser is faultily firing, like Chrome does).

jquery-pjax (the plugin GitHub uses to ajax navigate everywhere, powered by
popState), does the same thing. Generate an ID or tag, store that with the
push/replace state, and on the popstate, use that to identify ours and ignore

This will fix lots of other potential bugs as well.

Assigning back to me as it's on my mind now, might as well fix it.

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to