Timo Tijhof c3f6a2f561 mw.ViewPageTarget: Tag our state changes and reject foreign states ... Store a bit of data with the states we push or replace in the history so that when the user navigates back to them, we know for sure this is a state we pushed in the history. This allows us to filter out popstate events triggered by the user browsing to states create by other software, as well as states triggered by the browser that have no state data at all (Chrome is known to, in contrast with other browsers, trigger a blank popstate event on load, which we were mistaking for a user event where the user navigates back to veaction=edit). Bug: 57901 Change-Id: I142777d0d2ae96d3afee224782f0d2d1522da1eb		2014-03-12 22:26:52 +01:00
..
ve.init.mw.MobileViewTarget.js	Merge "Abstract tracking and specify which target it came from"	2014-03-08 01:01:08 +00:00
ve.init.mw.ViewPageTarget.init.js	Let users set #REDIRECT and __STATICREDIRECT__ status	2014-02-12 15:24:12 -08:00
ve.init.mw.ViewPageTarget.js	mw.ViewPageTarget: Tag our state changes and reject foreign states	2014-03-12 22:26:52 +01:00