In T31118#9042921, @cscott wrote:

There's a long discussion in the parent task, T25932, summarized by "wikitext is not a superset of HTML". If we want to allow markup like:

<details open>
<summary>(short description)</summary>
;Name
:Lorem Ipsum
</details>

then the best way forward (in terms of future maintainability) is not to "just" allow arbitrary use of <details> and <summary> tags in wikitext, but instead to start by adding a new parser function, say {{#details|short description|content}} which will emit the structure that you want. (The 'content' block is a good use of heredoc arguments, T114432.) That is "more semantic" in tat the wikitext author is writing a semantic description of the details box (or whatever), and it allows us the ability to change the exact markup emitted for that parser function in the future. We're not committed to emitting exactly those particular HTML tags in that particular tree structure for all time.

Works like a charm, as long as we remember wikitext isn't a subset of HTML 5, as indicated in one of the task linked above (thanks a lot Izno for the pointers).

Interesting points

Apparently, already done as part of 07e2100f.

We use périmé in French for out of date medication, expired document, broken links. Outdated or obsolete are the best translations I guess.

Not relevant, it bumps against an update issue from *before* the issue 1198609 wants to fix.

Can repro if we point to Commons too, my local development wiki has this:

Thanks :)

One of the huge advantage of <details> and <summary> is about accessibility, especially screen readers.

See also

Do we currently have any migration guide if we take this path?

Who are the ones responsible for this review?

Per discussion with Harmonia and Ash Crow we aren't sure to still need and maintain this tool.

Thanks :)

I've asked the local village pump for feedback (permanent link).

There are indeed two parts on this request:

We can indeed do the first thing, remove any account creation limit.

in addition each label is now inline rather than block

That was already the case before, but there were hidden 0 to fill the space you highlighted as empty.

Closing per previous comment.

That's a most welcome change, thanks!

I've updated the description with a table with the current ideas and associated patches. Resetting assignee to mark we can contribute on that too (Yash, you can reassign yourself if you wish to go on on this task).

Closed as resolved per previous comment.

If we look at https://upload.wikimedia.org/wikipedia/commons/0/05/Pagelist_Widget_Visual_Mode_Screenshot.png it seems the rationale for the 001 instead of 1 was to offer right alignment in the pages buttons. It's indeed an odd choice.

[ Assigning so it's more clear we've a merge request for that one. ]

Discussed on IRC #wikimedia-tech between @Anoop and @RhinosF1.

Typo in the task reference, this patch was for another task.

Actually, you can use the compiler of redirect.dat as a software to output to stdout the result:

Current status

Thanks for the reminders.

I concur, those are significant contributions to the extension.

A discussion to explicitly remove the feed. Note there is also a CNIL discussion on the talk page on the page you've linked, so perhaps open there a new section would be relevant.

@Jules78120 Could you edit the task description and add a link to the discussion on fr.wikipedia.org where you concluded it would be needed to remove this entry? That doesn't require a format RFC, but it should be traceable to the relevant discussion.

(pending a script to validate them, let's already prune the two problematic domains)

The two last works for me.

I've this information in my Phabricator comment box, probably the relevant message key: authmanager-authn-autocreate-failed

This extension isn't developed anymore. Yes, we can archive it.

@Ayush8745: a requirement for this task is to ensure all logos have a 135px width size, ie resize logos here: https://github.com/wikimedia/operations-mediawiki-config/tree/master/static/images/project-logos

@thiemowmde Did you try your username in lowercase?

For reference, the sbin folder is historically intended to contains executable with the S bit allowing privilege escalation and nowadays intended to contains tool only launchable by root or other administrative users.

The task is completed to provide the required tools to switch dblist to computed version and cached result.