Alex Monk 74cb83d2f8 Fix edit conflicts ... When we moved to mw.Api, edit conflict errors stopped going via onSave and started going to onSaveError instead. So the case to check for them in onSave would not have worked - instead, they would go through onSaveError and get picked up by our unknown error code, which just picks out error.info and shows it, instead of showing our edit conflict screen. Also return in a couple of other error cases where we probably should've been (but not necessarily must've been... that didn't necessarily show to the user if another error emit already caused saveDeferred to be rejected) Change-Id: Iae7a66a8aa96ee777e9fa780005feeb429129d5f		2015-03-19 02:36:21 +00:00
..
styles	mw.ViewPageTarget: Grey-out body content as soon as edit is clicked	2015-03-18 17:56:28 +00:00
targets	Handle TitleBlacklist errors	2015-03-18 21:58:51 +00:00
ve.init.mw.ApiResponseCache.js	Remove use of ve.indexOf and ve.getObjectKeys	2015-03-10 17:28:00 +01:00
ve.init.mw.ImageInfoCache.js	ImageInfoCache: Don't try to access imageinfo result if it's not set	2015-02-28 01:25:12 +00:00
ve.init.mw.js
ve.init.mw.LinkCache.js
ve.init.mw.Platform.js
ve.init.mw.Target.js	Fix edit conflicts	2015-03-19 02:36:21 +00:00
ve.init.mw.TargetEvents.js	Merge "Handle TitleBlacklist errors"	2015-03-18 22:44:36 +00:00
ve.init.mw.TargetLoader.js	Unbreak TargetLoader when ViewPageTarget.init isn't present	2015-03-17 17:38:29 -07:00
ve.init.mw.trackSubscriber.js	Set mwtiming events' target to 'mwTarget', if unset	2015-03-19 00:40:28 +00:00