@Samwilson Do we need to backport the fixes? There is no regular deployment this week.

I think a temporary workaround is to lock the preference of line wrapping (and perhaps add a horizontal resizability so users can have a wider editor and less line wrapping if that is desired).

Yes, you are right. The cursor at the end of the filter was an unexpected side effect when constructing the CodeMirror editor.

Sorry, I cannot understand this task. Could you add a reproducible link (e.g., a public abusefilter) and maybe also a screenshot with annotations?

Highlighting of comments inside links is a bug that we should work on first. Will see if we can support openLinks with comments later.
Free external links (i.e., bare URLs) containing comments will likely be a "won't fix", which does not make any sense to me.

In T423548#11836564, @Ninovolador wrote:

In T423548#11836560, @Bhsd wrote:

Could you provide a link so that we can reproduce the issue?

Of course, this is the book I'm working on.

In T423548#11836558, @Ninovolador wrote:

I am not sure if it's the same error, but ever since this bug started (apparently 15/04/26) I'm also experiencing a bug with the EditInSequence extension, where every page shows the same image.

First of all, what is the use case for inserting comments between two parts of a page name/ external URL?

I think this ticket should probably be declined as "won't fix". First, WikiLint has no way to expand the template. Second, the diagnostic severity is provided as optional info, which means users can choose to ignore it.

Horizontal resizability was discouraged in r1247931, and it may also conflict with T423759 if we want to add a WikiEditor toolbar.

There was no toolbar before when using Ace. A full list of available CodeMirror shortcuts can be viewed by pressing Ctrl-Shift-/.

At the current stage (after the deployment next week), a user can customize the client-side linting rules like this:

The master branch of ProofreadPage works perfectly in my local environment, so I still think Wikisource is broken due to image thumbnails.

Most recent bugs associated with the image when editing the Page namespace (e.g., T420077 and T421372) are caused by core changes in image thumbnailing instead of ProofreadPage itself. It could be true again this time.

In T259059#11826451, @MusikAnimal wrote:

But if there's disagreement there I can change r1271092 to keep $wgCodeMirrorEnabledModes with just mediawiki.

There will be some breaking changes to be deployed next week for T373720: Deprecate use of CodeMirror 5, so I had better review new feature proposals after that.

I find another extension that has hard dependency on the legacy CodeMirror 5 modules: MediaWiki-extensions-TEI

In T259059#11822688, @MusikAnimal wrote:

What I've done with respect to T419332 is leave the various *UseCodeMirror and *UseCodeEditor flags still set to CodeEditor, and we'll override it in the WMF config. This is because CodeEditor is bundled with MW, while CodeMirror still isn't (T391926). We can take care of that and the full replacement of CodeEditor by MW 1.47, which is fitting given that is also an LTS release. The plan for MW 1.46 is for Extension:CodeMirror itself to ship with default values assuming the sysadmin wants to use CM6, including replacing CodeEditor.

By the way, I think the tests also need to be done with CodeMirror only (no WikiEditor) and WikiEditor only (no CodeMirror), because the implementations are different.

In T421333#11817664, @GMikesell-WMF wrote:

On block, it shows but not the shortcut keys for it, as seen in the screenshot.

@Shreyansh123 If you have difficulty accessing Gerrit, you can also start with a GitHub fork. We can help you upload your patch to Gerrit.

r1270190 proposes user script customization like this:

I think we can prepare a JS interface first so that experienced users can start customizing in their user scripts.

In T383285#11756597, @MusikAnimal wrote:

we could perhaps go ahead and implement one gadget for a select wiki, and publish that code in our documentation (say at Help:Extension:CodeMirror/Custom linters) so other wikis and individual users can borrow from it to craft their own implementation.

In T383285#10450479, @stjn wrote:

see for example https://ru.wikipedia.org/wiki/Участник:DonRumata/Gadget-keybLayout.js

In T421372#11792354, @Samwilson wrote:

And I guess we can't detect which is which?

Mac seems to always load the 2x version instead of the src image, so switching to the src image may cause a lower image quality for Mac users.

With T417919 and T421541, the flaky selenium test should have been fixed now.

In T397871#11781224, @Novem_Linguae wrote:

I went to test it and didn't see any signs of CodeMirror. Is there anything I have to do besides installing the CodeMirror extension to turn it on?

The patch will be deployed next week, but you can test it now on the beta cluster (e.g., https://en.wikisource.beta.wmcloud.org/wiki/Page:9_02_1885_Martinet.djvu/1?action=edit).

T26586: Add title= option for images may be related.