Bartosz Dziewoński ae8b0a1f36 Replace $wgVisualEditorSupportedSkins with a check for required elements ... The bare minimum of elements that must be present on the page for VisualEditor to start and mostly work is: * '#content' to attach our interface (toolbar etc.) * '#mw-content-text' to replace with the editing surface * '#ca-edit' to start up the editor When those elements are missing (and we expect them to be present, e.g. we're not on a special page), we print a console warning. For example, VisualEditor now launches on Timeless and CologneBlue. It does not launch and prints a warning on Modern and Erudite. (It is actually possible to edit and save pages on CologneBlue, although various pieces of the interface look funny.) This does not change which skins we claim to support: these are still currently only Vector, MonoBook and Apex. But it allows third-party skin developers to more easily test the editor and fiddle with their CSS to make it look right. Bug: T161373 Change-Id: I97c786f3c8c795c238b10bef332a129ea26f86c2		2017-03-29 18:13:05 +00:00
..
ve.init.mw.DesktopArticleTarget.init.js	Replace $wgVisualEditorSupportedSkins with a check for required elements	2017-03-29 18:13:05 +00:00
ve.init.mw.DesktopArticleTarget.js	Merge "Don't use '#content #firstHeading', unnecessarily specific"	2017-03-29 18:02:22 +00:00
ve.init.mw.MobileArticleTarget.js	*ArticleTarget: Don't trust oldid in the query string, it lies	2017-03-24 00:30:00 +00:00