In T426996#11946811, @jhsoby wrote:

But I guess CodeMirror is used for more than just WikiEditor, so it probably needs to use its own messages.

It is already localizable, but someone needs to translate the messages into Czech on TranslateWiki.

Since JSON syntax highlighting is now using CodeMirror on WMF sites, this task is also relevant to CodeMirror.

The task has been completed for one month, but gadget authors still need to implement the new JS interface for their specific needs.

In T424442#11898054, @Nikerabbit wrote:

Do you have a link for the conversation? I'd like to better understand where this would be helpfu.

Maybe duplicate of T424198: Sometimes missing "Edit Section" option on mediawikiwiki pages which are translatable.

This issue is due to Convenient-Discussions calling the CodeMirrorWikiEditor#destroy method. r1282370 has been merged to fix it.

This is a known issue which unfortunately we cannot improve at this moment.

The standard CodeMirror shortcut for deleting a line is Ctrl-Shift-K, but it is now occupied by inserting <ref></ref>. Ctrl-D is a good candidate which also makes it consistent with previous Ace editor.

In T50826#11881193, @TheDJ wrote:

I say thats resolved then ;)

MediaWiki-extensions-CodeMirror now has its own CSS/JavaScript/JSON/Lua/Vue modes, and has become the default highlighter on WMF wikis.

TemplateStyles are now highlighted by MediaWiki-extensions-CodeMirror, which warns about unsupported vendor prefixes.

Even if we want to support this feature, the shortcut should be reconsidered because insert is not a universally available key on keyboards.

In T419679#11874287, @phuedx wrote:

Is the CI failure still happening?

Sure, I can work on it. There are a few things to consider though:

• Should it be default?
• Should it be toggleable?
• Should its position be configurable?

In T383285#11756597, @MusikAnimal wrote:

In addition to adding the new public customLint() method, 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.

I wonder if it is worth reporting upstream. It is reproducible on the CodeMirror playground, but it is not very clear what the expected behavior is.

We need to first clarify what color formats should be supported. Given continuing development of CSS specs, it will be inefficient to increase the JS bundle size for some rarely used color formats.

insertNewlineAndIndent will replace tabs with spaces. Ideally, insertNewlineKeepIndent should be fixed upstream.

It was designed to prevent bold or italic plain texts in template/parser function arguments which can be ambiguous since the very beginning of this extension.

I will not call it undoable, but it seems to me really difficult as it requires good understanding of both ProofreadPage and CodeMirror. Maybe we should consider a workaround instead at least for now? Do you have any alternative suggestions to mitigate the annoyance?

I have submitted a pull request to the upstream @codemirror/legacy-modes library.

Okay, I get it now. I can work on this tomorrow.

May I know what is the use case for inserting a tab character?

In T419332#11849130, @Candalua wrote:

And will this not create problems with gadgets and scripts, if the intended action is performed twice?

In T419332#11848560, @Candalua wrote:

1. When I activate the "Syntax", keyboard events are fired twice, looks like they're being duplicated by CodeMirror:

@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).