Thanks for this!

In T406940#11263134, @Aklapper wrote:

This shouldn't be hidden but disabled.

T398529: Message: icons can get cut off depending on message text length is fixed but it's still persistent on https://www.wikimedia.org/ unless that website 'hasn't upgraded'.
Proposed solution: (Add to .donate-emoji CSS selector to https://www.wikimedia.org/ lines 1541 to 1545 of (index) if that helps)

.donate-emoji {
    min-height: calc(var(--min-size-icon-medium) + 2px);
    min-width: calc(var(--min-size-icon-medium) + 2px);
}

✅ Works for me, even if I use Incognito, and DevTools to throttle and turn off JS.

I assume it has been disabled because it now no longer generates an object. Also on enwiki https://en.wikipedia.org/wiki/Template:Sandbox/sandbox and Beta Cluster .

In T406114#11234813, @jhsoby wrote:

I just noticed that the same happens in Wikidata too when I visit something like https://www.wikidata.org/wiki/Q42#P26 . So this should be fixed in Vector-2022 and not DiscussionTools.

Seems the issue could be the Special:GoToComment link? If you use the link on the timestamp of the comment [https://no.wikipedia.org/wiki/Wikipedia:Torget/Arkiv/2024/august#c-Znuddel-20240731074400-%C3%85rstall], that takes you to the exact spot you're wanting. I wonder why Special:GoToComment doesn't target that same spot, seems it targets something different because I'm finding it impossible to generate or go to my example below's Special:GoToComment link on nowiki??? It's so unintuitive... There's no instructions, it's not the right click Copy link address one, it's not the click the timestamp and it copies to clickboard one....

@elukey @Muehlenhoff Thanks for working on this!

Hi. @Jdlrobson-WMF: On English Wikipedia, inputbox is mostly used in edit request or draft creation scenarios (button-only), or submit nomination, for search boxes in documentation/guidelines, and via extensions. Testing with macOS VoiceOver showed better accessibility than NVDA/JAWS: it correctly identified button labels, (I wonder if that was because I was on the test.wikimedia.org with a newer version of Codex this time?) states, and used placeholder text as labels. Behaviour seems to vary across screen readers.

Ah okay. I did check the Wikimedia Status website, but it was all clear at the time. Probably should've checked after a few minutes. Sorry about that

Thanks!

Sorry, what I meant is the input elements type=search isn't set, this would mean there isn't AUTO labelling. See first example here for how to type it.

I'll claim it, try my best. If I don't win can I put it back into triage?

Sure thing. I've never done it via command line though, but I'll certainly figure it out. Just quick question, I have a developer account, but do I need a special user group or permission to push changes/make commits?

[ Moved this comment to its own task. ] - T403564: Buttons and search bar have no text or labels exposed to accessibility technology

Yeh been working for me all day with great response time.

@Salujapushpit I didn't dot the T's and cross the I's because I thought this would be discussed a little first and then merged. So please use the cleaned SVG code:

Like the idea! I think it it's important to clarify though if what is meant is that the Parser replaces backticks with <code> or <syntaxhighlight> HTML tags, or creates "monospaced text" as is mentioned in the main task which would be more like: <span style="font-family: monospaced;"> so there'll be no background, kind of like the enwiki template {{mono}}

And please label them. This is currently on en-wiki how screen reader reads when starting from eyeglasses icon: "Entered navigation - Menu pop-up Expanded, Button - Appearance":

• "Text"
• "List with 1 items - Appearance" (whilst highlighting all 3 radio buttons...)
• "Item 1 - List item - Small Standard Large" (whilst highlighting all 3 radio buttons.)
• "Checked, Radio button" (whilst highlighting first radio button, no alt text provided :-( )
• "Unchecked, Radio button"
• "Unchecked, Radio button"
• "Width
• "List with 1 items - Appearance"
• "Item 1 - List item - Standard Wide"

etc.

I hear the concerns about churn and translation workload. My intent has been to reduce confusion, not create more of it. I can see that some of my edits contributed to this confusion; I’ll pause non-urgent changes on these pages while we align on wording. 👍

Summary:
Recent edits have described OOUI as either deprecated or in maintenance mode, creating confusion, reversions, and extra translation workload. We need clear guidance from developers/design system maintainers so that documentation across pages can be updated consistently.

Found: visualeditor-dialog-media-info-audiofile for a mw-message. English is "Audio file"

Hmmm this would have been great.

In T124168#11055673, @DLynch wrote:

^ for discussion, here's a patch that adds an API method to MobileFrontend that would make it possible to fetch whatever content was removed from a given page by MobileFormatter. It could potentially serve as the basis of a feature that added some sort of "show excluded content" button on mobile that opened an overlay containing whatever had been stripped out. (Or filtered it down to just the excluded content that's a .navbox, of course.)

Hi. I ensured all icons in Commons at https://commons.wikimedia.org/wiki/Category:Wikimedia_Codex_icons.

In T383077#11073019, @TheDJ wrote:

In T383077#10433947, @Volker_E wrote:

Also note, that for historic reasons (inheriting from OOUI) our icons (package) is MIT licensed, the icons itself CC BY 4.0.

wait wut ? how does that make any sense ? the icons are never used in a way where you can link to their author and license ??????

In T401943#11087624, @Quiddity wrote:

... believe it might be clearer to just mention the single key-combination that works for all major browsers, as currently written in the first 2 sentences of Enwiki's custom version at https://en.wikipedia.org/wiki/MediaWiki:Clearyourcache

Fixing T401943: i18n: [clearyourcache] Incorrect message will slim the message down quite a bit

In T361508#11073814, @DTorsani-WMF wrote:

Our designated application design tokens can be found here.

One thing you can take away from the documentation written on the project page is the intention we built into the new color palette that is described in this section. Essentially, it describes the darkest value a background color can be to put text on and still maintain proper contrast for Level AA WCAG 2 accessibility.>

An attempt was made to create this before, see https://gerrit.wikimedia.org/r/c/mediawiki/extensions/BetaFeatures/+/84625

In T361508#9849065, @DTorsani-WMF wrote:

The team who builds Codex is currently working on an expansion to our color palette

Nope. fn+F1 nor F1 on macOS does nothing, when using Safari or Chrome.

! In T288161#11069714, @MusikAnimal wrote:

This task could proceed with CodeMirror 5 if we really want to, but I would advise against it. Imposing syntax highlighting on that many more users will bring more feedback to a product that will soon be permanently retired, so I say we should try to hold out for another month or two.

?

Someone veyr kind uploaded all the black SVGs yesterday. Well I haven't even confirmed if it was all 249 icons (because I have no idea how to that efficiently.

In T377663#11056003, @Nardog wrote:

@Waddie96 Are you trying to enable or disable autocompletion? This task was closed as resolved because it was turned on by default.

Update documentation with changes to keyboard shortcuts:

• https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
• https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
• Extension:WikiEditor/Keyboard shortcuts
• CodeEditor keyboard shortcut display
• CodeMirror keyboard shortcut display

(See Ace default keybindings: [https://github.com/ajaxorg/ace/wiki/Default-Keyboard-Shortcuts#line-operations])

• etc.

See Commons upload request for Codex icons: https://commons.wikimedia.org/wiki/Commons:Batch_uploading/Wikimedia_Codex_icons

Are these any solution help:

• 963840: Implement <mw-button> tags in wikitext for Codex button
• 249453: Implement <mw-icon> and <mw-button> tags in wikitext for OOUI icons/buttons

Also MW doc needed for: T21044: Document LanguageConverter

Does Parser::getTargetLanguage() or any other stuff need to be updated on the MW doc pages:

• mw:Manual:Parser.php
• mw:Manual:Language
• LanguageConverter

This is fixed. Works in macOS with command-F in Chrome and Safari, I assume fixed in Windows?

In T401042#11056013, @Nardog wrote:

FWIW you can press F1 and select "Show settings menu".

How do I know when it's live on Beta Cluster?

The cogg appears in MediaWiki-extensions-CodeMirror 's manual: https://www.mediawiki.org/wiki/Help:Extension:CodeMirror

Consider a combination of these icons... .

In T288161#9154585, @SD0001 wrote:

To take this forward, I think we need an RfC with consensus to enable this by default for all users (not just for new users – that's not happening).