Oh! Right, that makes sense for the simple variant, thanks.
Re: the new parser function, I cannot reproduce a successful test. (testwiki and beta cluster). But also, the patch isn't merged yet, so I'm also guessing that maybe you tested it locally?
I will delay including this entry in Tech News until next week, once everything is clearer (to me at least!). Thanks again for the details, and the drafts.

I noticed another task that mentions BCP47 at T366623: Create a parser function to get the BCP47 code for a language -- I'm not sure if that's related at all, but possibly?

For the proposed Tech News entry (per User-notice), please could someone suggest how to phrase it?
I am uncertain what aspects need to be highlighted.
Plus it seems like the latest patches may change the information.
(i.e. Is this purely an informational announcement about a bug (and is the bug now fixed? or will be soon?), or is any action required from any sub-group of editors?).
Thanks.

@Snaevar Is there an ideal listing we can link to, which provides those exact codes?
I.e. The link in your draft doesn't contain the strings en-basiceng or basiceng.

@Urbanecm_WMF For Tech News, do you have any suggestions on the wording? I'm not sure which aspects need/ought to be highlighted for editors. Thanks!

Thank you! I made a few tweaks, and have now added it to https://meta.wikimedia.org/wiki/Tech/News/2024/24 -- If any further tweaks are needed, please edit it directly there. I will be freezing it for translations in ~2 hours.

For Tech News, do you have a suggested summary we could use? (After reading the comments above, I'm still uncertain about which aspects need to be announced, and what kind of community decisions/feedback needs to be encouraged...?).
My best-guess is something like this (but I suspect it contains inaccuracies, and I hope someone can explain it more simply/concisely!):

Changes later this week

• On multilingual wikis that use the <translate> system, there is a feature that shows potentially-outdated translations with a pink background and marks them as "fuzzy". From this week, changes to the "fuzzy" status will be logged, and there is a new user-right that can be required for confirming translations, if the community requests it.

Ah, if there are no user-visible changes (or potential unintended affects) then it doesn't need inclusion in Tech News. Thank you for explaining the context though!
I'll remove the User-notice tag from here. If there's a related user-facing aspect to this deployed in the future, please add the tag to the related task!

Looks good! 2 weeks in a row with no errors, which is rare for my Tech News workflow. BIG thank you!

@Sj (Re: your comment in the mentioned task^) My user-CSS also does that! It even does it in mobile, and because I use it via Stylus, it also works in logged-out windows.
To use it yourself:

1. Copy line 2 from https://meta.wikimedia.org/wiki/User:Quiddity_II/global.css (into your equivalent)
2. and if you want it to work on your phone, also copy line 1 from https://meta.wikimedia.org/wiki/User:Quiddity_II/global.js (into your equivalent)
3. Or if you want it in anon-windows and non-SUL wikis, install it via Stylus (instead of #1)

Demo of sticky header:

P.s. I also use tiled-windows on a laptop, a lot, often 4 at once, hence I've spent a lot of time on this!

It looks like this was actually merged already and could've been announced last week.
Shall we still include an entry in next week's Tech News?
If yes, is the draft above accurate? Thanks.

For Tech News (per the User-notice tag that was added earlier), please could someone clarify when the entry needs to be announced, and what it should say? (1-4 sentences, 1-2 links). Thanks!

@aliu Yes, it does.

Thank you! I'll re-close this, and I've added an entry to https://meta.wikimedia.org/wiki/Tech/News/2024/23 - If changes to the wording are needed, please edit directly or comment here within ~22 hours, after which it will be frozen for translations. Thanks!

For Tech News

1. Timing: Please confirm if this is still going out in next week's train? (per task Description)
2. Content: I believe we just need to repeat/adapt the prior mention from https://meta.wikimedia.org/wiki/Tech/News/2024/21 - Please confirm if this (adapted) draft is accurate? (or fix!)

The HTML used to render all headings is being changed to improve accessibility. It will change this week in some skins (Vector legacy and Minerva). Please test gadgets on your wiki on these skins and report any related problems so that they can be resolved before this change is made in Vector-2022. The developers are still considering the introduction of a Gadget API for adding buttons to section titles if that would be helpful to tool creators, and would appreciate any input you have on that.

E.g. Perhaps we can add an expected timing note for Vector-2022? (I.e. Changing that sentence to something like "[...] before this change is made in Vector-2022 in a few weeks.")
Thanks!

It looks like User-notice was added here just because this task was forked from the parent-task which had it. Does it need another Tech News announcement? (possibly useful as a reminder for all?)

[re-opening until documentation is updated]
For Tech News, how should this be described? [1-4 simple sentences, 1-2 links].
And, is there any documentation to link to?

For the header, I think I've got it working well in my user-CSS customizations. I.e.

I wonder if it would be possible to simply turn these links into icons, under 720px?
My user-CSS accomplishes it like this (lines 951–1043):

I think the second link in the Description might be wrong? IIUC it should probably be
https://en.m.wikipedia.beta.wmflabs.org/wiki/Special:RecentChanges?minervanightmode=1

For Tech News, please confirm if this is an accurate summary (or tweak as needed):

Some CSS in the Minerva skin has been removed to enable easier community configuration. Interface editors should check the rendering on mobile devices for aspects related to the classes: .collapsible, .multicol, .reflist, .coordinates, and .topicon. Further details are available on replacement CSS if it is needed.

I can then add that tomorrow (Friday). (Or you can add it directly once it's good.)

Added to https://meta.wikimedia.org/wiki/Tech/News/2024/22 -- I've added the 2 links inline. Please confirm that is still accurate (and reply here, or fix it directly, if it isn't).

Thanks for the notes. For an announcement, we need to condense it down to ~1-4 sentences and ~1-2 links (ideally translatable-content-links, or at least with clear examples for non-English speakers who grok HTML).

If I understand correctly, this is currently feature-flagged and users won't notice any differences, but it is in next week's train. Hence I'm confirming my assumption by writing here.
If I'm wrong, and a Tech News entry is needed this week, please suggest possible wording for the entry. Thanks!

IIUC, this work was migrated over to T364887 so I'll move the User-notice there.

@Mrb_Rafi FYI, see the latest update above ("This has now been backported to production), because I saw you mention this bug in the hackathon telegram/IRC. This 'backport' effort from Jon means the fix should be live immediately (instead of waiting for the weekly deployment train to reach the Wikipedias on Thursday). I hope that helps a bit, and sorry the bug disrupted part of your event.
[Edit: And thank you, Jon, for working on the backport and review!]

The Etherpad copy, has now been Copied (& Cleaned-up a bit) into the task-description, so that links work (and content can potentially be updated in the future, if needed). :>

@Jdlrobson Great minds think alike! There is a bot for this, thanks to ladsgroup in Aug 2022! But it relies on the task being resolved. Copying from the description of https://phabricator.wikimedia.org/project/profile/1097/

User-notice-archive is an archive for User-notice to avoid the project getting extremely bloated and unloadable. A bot moves resolved tasks in "Already announced/Archive" column of User-notice, into the -archive, if they are not modified in the past ten days.

That helps a lot, thanks! (Both for historical posterity, and for this Tech News entry!) I'll still keep it short, but I've added it to Tech News as...

The old Guided Tour for the "New Filters for Edit Review" feature has been removed. It was created in 2017 to show people with older accounts how the interface had changed, and has now been seen by most of the intended people.

Thanks for the detailed recommendation! Updated at https://meta.wikimedia.org/wiki/Tech/News/2024/20

@Ladsgroup Added to https://meta.wikimedia.org/wiki/Tech/News/2024/20 -- Thanks for the draft wording, always appreciated!
I think I've gotten the <code> highlighting and non-translation snippets correct, but please glance-check.
It will be frozen for translations in ~20 hours, if any tweaks (or link additions/changes) are needed before then.

In T43351#9767132, @Samwalton9-WMF wrote:

I think this is worth putting in Tech News:

Nuke will now correctly delete pages which were moved to another title.

Much thanks for the cleanup!
Re: user-notice - Do you have any suggested wording for the entry in the next edition? E.g. I'm unsure how many projects this change affects, and if it's just 1 or 2 wikis then it might not need/warrant a Tech News entry. -- If it does affect many wikis, then Drafts welcome, here or in the next edition itself. :)
My best-guess would be something like this, but I suspect some nuance(s) are missing:

The old Guided Tour for the "New Filters for Edit Review" feature has been removed.

Added to https://meta.wikimedia.org/wiki/Tech/News/2024/20 -- Thanks for the draft wording (x2!), always appreciated! -- It will be frozen for translations in ~21 hours, if any tweaks (or link additions/changes) are needed before then.