Community Wishlist Survey 2023/Editing/Allow users to selectively disable code editor functions

Random proposal ►◄ Editing The survey has concluded. Here are the results!

Allow users to selectively disable code editor functions

Problem: The code editor currently tries to do too much, such as inserting an additional quote or bracket when you press a quote or bracket key, or delete an additional quote or bracket when you delete a quote or bracket. More often than not it guesses wrong and actually causes bugs by inserting things it shouldn’t have inserted and/or deleting things it shouldn’t have deleted. The coder would often stare at their code wondering why it doesn’t work before they realized it was the code editor that had corrupted their code.
Proposed solution: Add a button (or more) to allow the coder to selectively disable these automatic functions, such as autocomplete, auto-delete, and auto syntax checks.
Who would benefit: Wikipedians who write or edit Lua modules.
More comments: Currently coders have the option to disable the code editor entirely, but that is not ideal because line numbers and syntax highlighting are actually useful.
Phabricator tickets:
Proposer: Al12si (talk) 20:28, 5 February 2023 (UTC)[reply]

Discussion

This can already be achieved by pressing Ctrl+, while the focus is inside the code editor and unchecking "Enable Behaviours". This settings panel is part of the Ace library, which underlies CodeEditor, and is not well integrated with the MediaWiki interface, but it is possible nonetheless. Nardog (talk) 05:49, 6 February 2023 (UTC)[reply]

@Nardog: Huh, TIL! — TheresNoTime-WMF (talk • they/them) 14:51, 8 February 2023 (UTC)[reply]
Thanks for this, I had once opened the menu on accident around one and a half years ago and since wondered how I could access it on purpose. ~~~~
User:1234qwer1234qwer4 (talk) 17:42, 24 February 2023 (UTC)[reply]

It would probably be possible to expose a button to open this settings page. ESanders (WMF) (talk) 15:02, 6 February 2023 (UTC)[reply]
I have a user script for that ;) A challenge though is i18n (T146393). Nardog (talk) 16:17, 6 February 2023 (UTC)[reply]

Would definitely be useful for mobile editing. ~~~~
User:1234qwer1234qwer4 (talk) 17:43, 24 February 2023 (UTC)[reply]

Voting

Support TIL for me as well about the shortcut. Never knew about such a thing. I'd support adding a button to the toolbar as ESanders suggested — DaxServer (t · m · c) 20:05, 10 February 2023 (UTC)[reply]
Support TJ Ryba (talk) 22:04, 10 February 2023 (UTC)[reply]
Support --NGC 54 (talk｜contribs) 01:05, 11 February 2023 (UTC)[reply]
Support Hanif Al Husaini (talk) 05:35, 11 February 2023 (UTC)[reply]
Support Maybe some improvements of the CodeEditor for modules / US also. Thingofme (talk) 16:22, 11 February 2023 (UTC)[reply]
Support Thomas Kinz (talk) 20:14, 11 February 2023 (UTC)[reply]
Support Waldyrious (talk) 20:49, 11 February 2023 (UTC)[reply]
Support Betseg (talk) 04:03, 12 February 2023 (UTC)[reply]
Support adding the button and persisting its result as a built-in feature of CodeEditor. Tacsipacsi (talk) 18:09, 13 February 2023 (UTC)[reply]
Support Zwd626 (talk) 04:16, 14 February 2023 (UTC)[reply]
Support cyrfaw (talk) 12:08, 15 February 2023 (UTC)[reply]
Support —‍(ping on reply)—‍CX Zoom (A/अ/অ) (let's talk|contribs) 22:31, 17 February 2023 (UTC)[reply]
Support Packerfan386 (talk) 09:52, 19 February 2023 (UTC)[reply]
Support Seems reasonable to make this easily available. --CHF (talk) 20:30, 21 February 2023 (UTC)[reply]
Support Any kind of automatic "correction" is dangerous and should be optional. Chatul (talk) 12:43, 22 February 2023 (UTC)[reply]
Support Althair (talk) 04:00, 23 February 2023 (UTC)[reply]
Support per ESanders. ~~~~
User:1234qwer1234qwer4 (talk) 17:43, 24 February 2023 (UTC)[reply]