This was already addressed in some previous Codex release.

Duplicated in https://github.com/wikimedia/eslint-config-wikimedia/issues/576

With #14866d currently in use for validation inline messages, we achieved the contrast requriements.

These have been successfully implemented as

--background-color-backdrop-light: rgba( 255, 255, 255, 0.65 ); /* Backdrop is the term used by CSS Fullscreen API and is used to dim the background when a modal Dialog is open. Also known as overlay mask. */
--background-color-backdrop-dark: rgba( 0, 0, 0, 0.65 );

Change 738472 abandoned by Winston Sung:

[wvui@master] [DO NOT MERGE] build: Wrap the composition API plugin to disable it in Vue 3

Reason:

This project has been archived

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

This is being done as part of T350651

Removing inactive task assignee. (For future reference, please do so as part of offboarding!)

In T279108#8704706, @kostajh wrote:

@egardner @LNguyen @kchapman could I ask for a status update on this proposal, please? What is the next step in the TDF process? I think there are a lot of people who would like to see some form of a front-end build step implemented, but we need to build consensus on how that should be done, and what should/shouldn't be possible in this build step.

Some implementation suggestion that I think might help narrow the discussion and get this to a more actionable place.

@egardner @LNguyen @kchapman could I ask for a status update on this proposal, please? What is the next step in the TDF process? I think there are a lot of people who would like to see some form of a front-end build step implemented, but we need to build consensus on how that should be done, and what should/shouldn't be possible in this build step.

@Sarai-WMDE Definitely agreed. I'd also update the task description with the high-level agreements (and links) in this task.

In T303587#8667898, @Sarai-WMDE wrote:

We could add an Internationalization section in our Typography guidelines, and provide a list of languages that don't have a direct fallback in Figma, together with the specific Noto font that renders them. A similar note could also be added in the Style guide if necessary.

What do you think about this suggestion, @Volker_E and @bmartinezcalvo? I'd say this task can be considered done, but that documenting our approach would be valuable. If you agree, I can open a separate ticket to reflect that effort.

@Sarai-WMDE Definitely agreed. I'd also update the task description with the high-level agreements (and links) in this task.

We could add an Internationalization section in our Typography guidelines, and provide a list of languages that don't have a direct fallback in Figma, together with the specific Noto font that renders them. A similar note could also be added in the Style guide if necessary.