Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 10 years ago by Siddhartha Ghai in topic Clarification request

Legacy toolbar[edit]

Would someone please be able to explain whether the toggle for on and off will be functioning with the legacy toolbar? If not, then what will be the method to toggle it? Thanks. — billinghurst sDrewth 05:10, 28 August 2013 (UTC)Reply

I think you're referring to Special:Preferences#mw-prefsection-editing → "Enable enhanced editing toolbar". I just tested at if you disable this user preference, you'll still be presented with the newer (i.e., the WikiEditor) toolbar. The provided screenshots accurately convey what users will see on JS, CSS, and Scribunto pages from now on by default. The legacy toolbar won't be available on those pages. Even if you disable CodeEditor, the newer toolbar remains (though it appears both are being loaded...).
Okay, that replicates for me, and will do. — billinghurst sDrewth
Personally, I'm not sure why the legacy toolbar still exists at all. It's a blight. --MZMcBride (talk) 05:33, 28 August 2013 (UTC)Reply
Presumably for some sites the legacy toolbar is probably (simply?) just more effective. Easier to programmatically customise (add|remove) buttons, and also easier to use not have a whole lot of button bloat, nor drop down menus. — billinghurst sDrewth 10:39, 28 August 2013 (UTC)Reply

Clarification request[edit]

The last line says,

If you want to disable CodeEditor, you can press this button: (button image). This should be persistent for your account.

What does persistent for your account mean here? That the preference for usage/non-usage of codeEditor on js/css/lua pages will be saved and other pages will be loaded according to that preference? If so, how is the preference stored? If its client-side, its not really user account specific, but rather user account + os/browser specific. Or is the preference stored server-side (in which case it probably really is user account specific)?

Also, I haven't tried this out (don't know if it's been deployed), but wouldn't the button be for both disabling and enabling the editor? If yes, the text should clarify that once disabled, it can be re-enabled by the same button. If that's not the case, the process to re-enable it should probably be specified.

PS: I also need these clarifications in order to correctly translate this into Hindi.

Regards--Siddhartha Ghai (talk) 18:38, 8 September 2013 (UTC)Reply