MobileArticleTarget: Remove duplicate way to trigger abandon warnings

Abandon warnings are already handled by the code in MobileFrontend's
EditorOverlayBase. Using window.history.back() causes that code to run.
Having a duplicate way to trigger them only results in inconsistencies
because our dialogs animate in a different way.

Bug: T222315
Change-Id: I19c5616a6aeecf0ac63f37a564ef44f11df010b0
This commit is contained in:
Bartosz Dziewoński 2019-06-04 15:50:47 -04:00
parent 742564d1d2
commit 4184d44dc5

View file

@ -452,11 +452,7 @@ ve.init.mw.MobileArticleTarget.prototype.saveFail = function ( doc, saveData, wa
* @inheritdoc
*/
ve.init.mw.MobileArticleTarget.prototype.tryTeardown = function () {
// Parent method
ve.init.mw.MobileArticleTarget.super.prototype.tryTeardown.apply( this, arguments )
.then( function () {
window.history.back();
} );
};
/**