Tasks related to JavaScript in MediaWiki core or extensions.
See also Instrument-ClientError (Javascript error logging in Wikimedia production).
Tasks related to JavaScript in MediaWiki core or extensions.
See also Instrument-ClientError (Javascript error logging in Wikimedia production).
Some things related to async functions that don't work yet:
In both of these cases, if you minify them with maxLineLength=1, the output puts async and function on separate lines, which is a syntax error.
Should be fixed now. QA efforts can be part of T370839
Resolving. QA efforts can be part of T370839.
In T369995#10006960, @CCiufo-WMF wrote:Are we sure this is an OOUI issue and not a browser issue? @Volker_E do you know of any recent OOUI changes that would have affected this?
I've done some tries, using e.preventDefault() in beforeinput event handler:
Using e.inputType === 'insertLineBreak' in the beforeinput event handler, it manages to catch the Enter input.
I logged e.key in the beforeinput event handler, and got undefined… so obviously, that's why the Enter inputs are not intercepted.
I don't think this is a browser issue, as I can reproduce the problem on Chrome and Firefox.
Are we sure this is an OOUI issue and not a browser issue? @Volker_E do you know of any recent OOUI changes that would have affected this?
@Jdlrobson Do you know why mw.config.get('wgCategories') doesn't work on mobile? That sounds like a MW Core bug, or perhaps MobileFrontend.
OOUI is owned by DST.
Change #1055512 merged by jenkins-bot:
[mediawiki/core@master] tests: Remove unstyled text atop Special:JavaScriptTest
A possible security consideration: if the check for redirect content is a simple prefix comparison, then such a redirect could "hide" some code from an unsuspecting user. This won't be an issue if only code comments are allowed in the suffix.
Change #1055511 merged by jenkins-bot:
[mediawiki/extensions/VisualEditor@master] tests: Fix DesktopArticleTarget dirtying location.href