Timo Tijhof 5036099906 ve.init.mw.ViewPageTarget.init: Pass default values ... Though this is already handled by Ie50b63ba5064e85d26 for the server-side, and that should automatically reflect to the client-side. Since we're dealing with cache conditions in wmf-production where the user.options manifest does not yet contain an entry for these relatively new preferences, lets transfer the default value here as well. This does not affect logged-in users (since their user options are always up-to-date and embedded in the page). Also made ve.support.es5 be casted to boolean. Previously it would be a reference to JSON.stringify (if supported), or the bottom value of whichever feature the browser didn't support. Doesn't change any behaviour but should make things slightly more performant when this value is evaluated. Change-Id: I9ca430051ae6f4e603c2d89982e540e455055255		2013-07-31 20:46:45 +00:00
..
styles	ve.ui.Toolbar: Refactor floating logic for performance	2013-07-30 01:47:54 +02:00
targets	ve.init.mw.ViewPageTarget.init: Pass default values	2013-07-31 20:46:45 +00:00
ve.init.mw.js	The great directory split of 2013	2013-07-02 20:51:38 -07:00
ve.init.mw.Platform.js	The great directory split of 2013	2013-07-02 20:51:38 -07:00
ve.init.mw.splitTest.js	The great directory split of 2013	2013-07-02 20:51:38 -07:00
ve.init.mw.Target.js	Infrastructure for loading plugins in the MW integration	2013-07-26 19:31:56 +00:00