Looks like @Rxy has a revert patch here: https://gerrit.wikimedia.org/r/c/operations/puppet/+/535987/
Aug 24 2022
Feb 22 2022
Feb 21 2022
Jun 2 2021
Sep 12 2019
Nov 15 2018
I'd like to see this. We use CodeMirror (and LinkSuggest), but the latter doesn't work with CodeMirror.
Oct 23 2018
I think that regardless of how effective CentralAuth's global locks are, implementing something in the GlobalBlocking extension that allows users to be blocked would be worthwhile, especially for independent wikis who don't utilize CentralAuth.
Sep 23 2018
Jan 26 2018
@Volker_E Well, anywhere that the help buttons are used in conjunction with a form, whether that be a custom gadget/script that utilises OOUI or an extension. Whenever I've used forms elsewhere (outside of MW), tab has cycled through each input on the page, not any guidance or help text. It's a slight annoyance from my perspective that there are extra key presses required to cycle to each input, especially when there is a form with a lot of inputs and each have their own help buttons.
@Volker_E Can we set the button to an access key instead to retain that accessibility? It just doesn't make a whole lot of sense to cycle to the help elements on tab, especially when you're trying to quickly fill in a form. Alternatively, another solution where we can keep this functionality but move it away from tab, as I know access key can behave differently per browser.