In T368910#9974427, @bd808 wrote:

The community run https://www.mediawiki.org/wiki/Project:Support_desk system is current Flow based. It seems important that community administered tech support for MediaWiki continue to be accessible to unregistered users. The work at T365846: Assist communities in archiving Flow/StructuredDiscussions boards should maybe prioritize discussions with the mediawiki.org community to ensure that technical support for MediaWiki continue to function well with Temporary accounts.

The community run https://www.mediawiki.org/wiki/Project:Support_desk system is current Flow based. It seems important that community administered tech support for MediaWiki continue to be accessible to unregistered users. The work at T365846: Assist communities in archiving Flow/StructuredDiscussions boards should maybe prioritize discussions with the mediawiki.org community to ensure that technical support for MediaWiki continue to function well with Temporary accounts.

@Edtadros this was mistagged - please ignore for now.

In T365311#9957461, @Jdlrobson wrote:

@MusikAnimal could we add skin-theme and noinvert along with cm-mw-colorblind-colors in the mean time?

@Jdlrobson, I can't seem to get any syntax highlighting to show up in prod. Any ideas?

Anyway, here's more discussion.
https://ux.stackexchange.com/questions/1042/is-a-cancel-button-necessary-in-a-web-form

Well perhaps instead of a hacked HTML <form> cancel button, maybe have no cancel button at all.

Making this a frameless button was an intentional design choice to reduce the amount people click on it, because too many people in user tests were clicking on it and were unable to 'see' the more important preview and diff buttons next to it (a framed destructive button is very prominent).

Hello @ppelberg and Editing-team, would you mind taking a look at this enabling request, and give a 👍 if it looks good from your end?

It's readable for me but not sure if it checks all the contrast stuff, also some colours looks a bit too same to each other.

Okay that suggests notheme and skin-invert can be added effectively here which is good news!

In T365311#9957461, @Jdlrobson wrote:

@MusikAnimal could we add skin-theme and noinvert along with cm-mw-colorblind-colors in the mean time?

@Sjoerddebruin perhaps try this in your user CSS as a workaround - does that help?:

.cm-mw-colorblind-colors { filter: invert(1); }

@MusikAnimal could we add skin-theme and noinvert along with cm-mw-colorblind-colors in the mean time?

So, the edit page is now enabled for dark mode. I'm unable to do edits without syntax highlighting and I can't keep switching modes all the time...

I guess we can close this as obsolete? I fail to make Logstash display anything for me no matter which timeframe

Change #1040235 merged by jenkins-bot:

[mediawiki/extensions/VisualEditor@master] Replace hardcoded colors with Codex design tokens

https://gerrit.wikimedia.org/r/1040235

In T356196#9939679, @Stashbot wrote:

Mentioned in SAL (#wikimedia-operations) [2024-07-01T13:29:44Z] <urbanecm> mwmaint1002: [urbanecm@mwmaint1002 ~]$ foreachwiki DiscussionTools:FixTrailingWhitespaceIds (T356196)

Mentioned in SAL (#wikimedia-operations) [2024-07-01T13:29:44Z] <urbanecm> mwmaint1002: [urbanecm@mwmaint1002 ~]$ foreachwiki DiscussionTools:FixTrailingWhitespaceIds (T356196)

Mentioned in SAL (#wikimedia-operations) [2024-07-01T13:25:34Z] <urbanecm@deploy1002> Finished scap: Backport for [[gerrit:1050406|FixTrailingWhitespaceIds: Don't crash on complex conflicts (T356196)]] (duration: 08m 46s)