For problems that are specifically related to the Mozilla Firefox browser and its rendering/behavior.
Details
Wed, Nov 13
Thu, Oct 31
The v6 module loads the CodeMirror lib (ext.CodeMirror.v6.lib) at the same time as the visualeditor module. In v5, it is loaded after VE and the toolbar have loaded. I'm fairly sure that's the problem. It may have something to do with the fact that ext.CodeMirror.v6 needs the library upfront, while ext.CodeMirror does not. Simply adjusting extension.json (adding ext.CodeMirror.v6.lib as a dependency, etc.) and even adding some mw.loader.using() blocks doesn't seem to reliably fix the issue.
Oct 17 2024
Oct 10 2024
Oct 9 2024
Tried Narrator on Microsoft Edge (Chromium) 109 on Windows 7. Somehow, it doesn't read Edge's web content, apparently. Nonetheless, at least Chromium Edge has its own Immersive Reader, which reads content aloud.
Almost forgot: I read some thread about Microsoft Narrator being incompatible with Google Chrome but works well with Chromium(?) Edge. And the thread is early this year, NOT years ago. As I can assume, this is concerning Windows 10 or 11.
I can confirm in Firefox 131.0 and I cannot reproduce in Chromium (which is also smart to linebreak between . and <).
Sep 29 2024
September 2024 report from pl.wikipedia - need to confirm about:config settings of the reporter
Sep 28 2024
Sorry to have bothered you:
it wasn't any of the extensions but clearing the cookies helped.
Firefox does load VE for me, so it's presumably something specific to your environment.
Which Firefox version do you use? You may want to disable some browser addons like AdBlock Plus or Greasemonkey in order to test the bug.
Sep 26 2024
Firefox supports break-inside: avoid; since January 2020 (just one month before this ticket was created) and break-inside: avoid-column; since September 2021 (i.e. at a later time). See compatibility table.
Sep 25 2024
Change #268316 abandoned by Jforrester:
[VisualEditor/VisualEditor@master] IME tests: Add failing Korean IME test
LGTM
This ticket documents the behaviour exactly as we implemented so not a bug.
Sep 16 2024
The first two things are intentional changes, for the third item see all the questions in my previous comment
Sep 4 2024
Sep 3 2024
Sep 2 2024
I think you might need to check your stats based on UserAgent (if that is possible). You might need to check with tool and bot authors which might be using outdated software. This is important because a single connection once a day by some tool might be used by thousands of users.
Aug 29 2024
Not, it's just automatic. Sorry about that. No need to announce.
Does this task need to be announced in Tech News? It looks like the User-notice tag was just automatically added due to the sub-task-creation system (cf. T239378 (un-linked to avoid unnecessary mentions there)).
I cannot tell if this change requires broad announcement to all technical editors.
Please either confirm it does (and suggest some wording for how to announce it), or remove that tag. Thanks!
Yes ... I have expanded my window (I have preferred to keep it so far at around 1024 pixels, about the size of a full desktop screen from 20-25 years ago when I started) and all these issues disappeared, so no problem. Of course that still, to me, begs the question of why this started happening last night ... up till then the new skin had been working just fine in smaller windows.
The first two things only happen on windows smaller than 1120 pixels wide and is needed to keep the content readable.
cannot be reconfigured
Aug 28 2024
@Volker_E , thanks for https://github.com/wikimedia/jquery.ime/pull/788 ! I've tested it and merged it. Some time very soon, hopefully tomorrow, I'll merge it to the ULS extension (I have a few more jquery.ime patches to update there, and I want to merge them all in one commit).
Aug 23 2024
Feel free to move the tag to a more specific subtask.
Aug 20 2024
Unassigning as seawolf35 has courtesy vanished on-wiki