MediaWiki 1.45 is scheduled to be released later this month, so I do not think people will actively work on this task.

In T409490#11353958, @Escargot_rouge wrote:

Yes, it could be helpful to limit the number of displayed tooltips and, if possible, to merge all 17 identical messages into a single one, indicating “×17”.

In T360351#11353877, @A_diehard_editor wrote:

I'm sorry, but the page in question is on my localhost private MediaWiki installation. If I find a way to reproduce on a public Wikimedia site, I will update.

In T360351#11333285, @A_diehard_editor wrote:

I figured it out, I apparently need to go to the file's page, edit the file, and change its privacy settings. Does it work now? (Why does Phabricator make files private by default?)

Do you have any suggestions? How about limiting the number of displayed tooltips?

What is "Editing help"? In addition, I do not think CodeMirror 6 for JavaScript has been deployed for Wikipedia.

In T360351#11331052, @A_diehard_editor wrote:

@SD0001 Could you confirm the state of this task?

@A_diehard_editor Are you using CodeMirror 5 or 6? CodeMirror 6 needs to be enabled in LocalSettings.php.

Currently there are some duplicate rules between WikiLint and Parsoid, such as unclosed-quotes-in-heading (Parsoid)/format-leakage#apostrophe (WikiLint), duplicate-ids (Parsoid)/no-duplicate#id (WikiLint), bogus-image-options (Parsoid)/no-duplicate#imageParameter (WikiLint), fostered (Parsoid)/fostered-content (WikiLint), wikilink-in-extlink (Parsoid)/nested-link (WikiLint), and obsolete-tag (Parsoid)/obsolete-tag (WikiLint). However, the marked text range can be different between the two linters, usually more precise from WikiLint. What should we do with these rules?

Will be resolved by T407153.

In T408292#11309721, @mykhal wrote:

.. just a note on linking to CodeMirror 5 (legacy): current enwiki production version is 6.0.0, having the bug (too)

The recent change breaks the replacement of the search button when CM6 is enabled, which queries .group-search .tool.

The linter feature of the beta CodeMirror 6 extension can be helpful when debugging Wikitext.

FYI, there is a task in progress to display all lint errors when CodeMirror 6 is on (T394965).

How about just disabling IME like in CodeMirror 5 (T194102)?

CodeMirror 5 has been disabled for the content model proofread-page, while the integration with CodeMirror 6 should be discussed in T380262.

The basic objective of this task has been completed. Further discussion about the linter configuration can be continued in T394964. The Parsoid-based linting is a separate task (T394965).

This issue seems more difficult than I thought, because the keyboard events are always re-dispatched in the original textarea.

Thanks for your kind words! The above patch will fix it for - as a special case, and we can leave a more comprehensive fix later (I do have some success in my online demo).

There are ongoing efforts to replace CodeEditor with CodeMirror in the integration with TemplateStyles, and this task should be easy to implement using a custom Stylelint rule.

I think there are multiple patches in multiple repositories that need backporting. Otherwise, we can just create a simple patch for REL1_44 to limit the CodeMirror beta feature within core content models (javascript, css and json).

I will not call it a bug because it is expected to some extent and a comprehensive fix for template argument names containing specific characters will be difficult. The same issue exists for ~, <, etc, for a long time. I will provide a simple fix for - soon.

A local fix is to explicitly register supported languages in $wgCodeMirrorContentModels.

@Jack_who_built_the_house Thanks for the recording! I can reproduce it now. A quick fix will soon follow.

I cannot reproduce the issue for the standard editor. In that case, although there are two .imeselector.imeselector-toggle elements, the other one is for #wpTextbox1 and is always display: none when CodeMirror is on.

Sohom's comments in r1186190:

Option #3 looks best to me as well.

In T381577#11179342, @Amire80 wrote:

The best solution would be to have a separate message for each of them.

In T381577#11179011, @Amire80 wrote:

Can anyone please say more about the message codemirror-wikilint-unclosed? What can $1 be?

Will be fixed by r1186187.

Thanks for reporting this! My opinion is that ' should not be auto-closed in Wikitext.

In T381577#11143083, @Amire80 wrote:

• $1 parameters are not documented. Please add explicit documentation for every $1 parameter in every new message.

r1184397 cannot be automatically merged. Maybe I need to avoid XML-like tags?

@Amire80 Thanks for your comments!

Shouldn't you also file tickets for WikiEditor and VisualEditor? CodeMirror just keeps the implementation consistent with existing shortcuts.

In T393833#11109416, @Novem_Linguae wrote:

I don't see an "Advanced" section though.

In T393833#11109407, @Novem_Linguae wrote:

Perhaps we should add a button/icon for CodeMirror find to the wikitext toolbar?

The DataScript needs updating to include subst, safesubst and raw.

In T373711#11033654, @MusikAnimal wrote:

I may need help adding a worker for the the linter as well. I figured it should be doable as there's a plugin for eslint, and we have that working already.

The new keyboard shortcut has been added for a while, so I am inclined to close this ticket. However, please feel free to open a new one if a related preference option is requested, which will likely wait for T393664.

In T393833#11018472, @SnorlaxMonster wrote:

It would be perfectly fine for the text outside of visible area to not be syntax-highlighted, as long as it's still findable with the Find function.

Do you mean that we also want to drop validFor?

I confirm that Edit Recovery still works, but it appears to be an opt-in feature so some Firefox users like me may not be familiar with this solution.