Noting for the record, i've deleted those 2 pages now, just to help empty the Category:Pages with broken file links.

Thank you for the reply and the draft @JJMC89 , much appreciated.
I will postpone including this in Tech News for now, in the hopes that someone can write/update the related documentation.

Ah, right, then I believe this is essentially covered by the mention in last week's Tech News. Thanks.

For Tech News, please could anyone propose a clear description of the context for the problem and how editors familiar with SVG can most effectively help?
My best guess is something like this:

If you are familiar with editing SVGs, you can help to fix some files that use invalid syntax, which do not display correctly anymore due to stricter standards in web browsers and due to the recent software library update for our thumbnail system.

For Tech News, please could someone confirm or describe what exactly needs to be communicated? I'm uncertain if it's essentially just informing everyone about a temporary bug that was fixed, or if there's any followup edits that might (or do) need to made by editors. If it's the former, I would hesitantly propose using this wording:

• Two weeks ago there was a problem with the displayed size of some images that are used within tables. This was fixed last week.

P.s. @hnowlan I see there's an unmerged patch connected to this task, yet the task is marked as resolved. Does that status need to be changed?

Hi @Snaevar (or anyone), given that the proposed parser function hasn't been merged yet, I'm wondering if you have any suggestions on how to most clearly help the editors who might need some guidance?

In T366419#9886194, @Quiddity wrote:

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.

Hi, for Tech News, please could someone advise on the wording and timing of the entry?
I see it is tagged as 1.43.0-wmf.11 and hence rolling out next week, but I'm not sure if it needs to be announced in the upcoming edition, or if there's perhaps a good reason to delay it by a week or more (e.g. to write/update any related documentation that we'd link to from the entry). Thanks.

Hi, thanks for adding the User-notice tag. For a Tech News entry, please could someone suggest what needs to be communicated to editors, and also when it is best to announce it?
I.e. Are there any immediately visible changes in next week's deployment train that technical editors (or interface admins) will need to prepare for, at any or all wikis?
Plus, is there any documentation that can be linked to from the entry? (or if documentation still needs to be written/updated, should we postpone the Tech News entry until it is ready?) Thanks.

Please confirm if this is an accurate and suitable draft for Tech News, or if anything needs to be changed or added. (e.g. Are there any links to add to the text, or perhaps an example before/after image for the top of the Description here). It will be frozen for translation in ~24hours:

The colors used for visited-links, hovered-links, and active links, was slightly changed last week to improve their accessibility.

Added to Tech News with this wording. Thanks for the draft!

You can copy permanent links to talk page comments by clicking on a comment's timestamp. This feature did not always work when the topic title was very long and the link was used as a wikitext link. This has been fixed. [1]

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).