With the new mobile statement editor being rolled out soon, the statements now will look nicer on dark mode. However, the most important issue (the main heading) still is completely illegible. Is there any plan to fix this soon?

This just started happening to me constantly today.

Has this been rolled out to English Wikipedia? See this talk page where the issue is happening on a similar (but not the exact same) image in a userbox.

Also occurs on Microsoft Edge.

In T437148#12314085, @MusikAnimal wrote:

We could make the mobile editor respect the 2017 editor preference, then everybody wins :) If that were the case, with the 2017 editor turned off, we are stuck with the MobileFrontend for now, but we can look forward to a mobile-friendly standalone CodeMirror experience after T95148.

I think that it would be nice if the preference was separate, as someone who dislikes the 2017 Wikitext Editor on desktop but would like a toolbar on mobile. Just my opinion though.

Also possibly links in CSS and JS (url(), mw.loader.load(), etc.) and pages in importScript()?

In T437764#12314478, @Bhsd wrote:

Underlines will be ambiguous because they are also used to mark links.

In T437763#12314476, @Bhsd wrote:

I am not sure if this task should be accepted. Extra bolding or italicizing may not always look good.

Similar to my request at T437764: Strike text wrapped in <s> and <strike> tags in CodeMirror.

Not sure why my two (not very related) tickets were merged here without explanation. An accident?

Also an issue on the mobile skin.

In T433767#12177489, @DLynch wrote:

I think the remaining unmerged patch on T432400 will probably do this. It'd make anything that work in the insert-a-link inspector work in the autocomplete, rather than just whatever happens to work via the opensearch API.

Would this also allow autocompleting templates after typing subst: and safesubst:?

In T433767#12177294, @Tacsipacsi wrote:

I’d also call this a bug (though a borderline one, which is not far from a feature request), but bugs also have their own form, which is also linked from the top of the task creation page, so using the generic form wasn’t appropriate in that case either.

Yeah, I realized that after reporting it. I just found the link to this Phabricator project on the MediaWiki extension page, and didn't see the "bug report form" button.

In T433767#12176530, @Tacsipacsi wrote:

Hi @Axolitl, and welcome to Phabricator! There are multiple ways to get link autocomplete in DiscussionTools, which use different pieces of software. To find out which one you’re complaining about, can you describe a bit more precisely where you experience the issue?

• In visual or source mode?
• Do you click a toolbar button, or just type in the [[ signs?

A screenshot would also be helpful (you can use the upload button on the Phabricator toolbar), although not required.

In T433767#12177198, @Aklapper wrote:

For future reference, please use the feature request form (linked from the top of the task creation page) to create feature requests, and fill in all the sections in the template. Thanks.

Okay, my bad. I had thought this was a bug since it seems like it would be normal behavior to have it included.