PHP extension to allow users to enable JS-based, user-provided gadgets from their preferences page (Homepage). This is not meant for reporting bugs or problems with local gadgets themselves.
Details
Mon, May 19
I would categorically prefer a task like this to be implemented and have previously argued it when discussion of category templates was at hand (perhaps not on Phab?). Categories are almost always going to be a middleman in the context of these kinds of limited gadgets, and all the category gadgets on enwiki are closely associated to a handful of templates.
Fri, May 16
Test wiki on Patch demo by SD0001 using patch(es) linked to this task was deleted:
Mon, May 12
Change #1144605 merged by jenkins-bot:
[mediawiki/extensions/Gadgets@master] Hooks: change gadgets-section-info-$section to gadget-section-info-$section
Gadgets-, with the s, was chosen to avoid conflicting with the description messages of gadgets (which start with Gadget-, without the s). In retrospect, agreed that being consistent with section name messages (which can already name-conflict anyway) makes more sense.
Change #1144605 had a related patch set uploaded (by Novem Linguae; author: Novem Linguae):
[mediawiki/extensions/Gadgets@master] Hooks: change gadgets-section-info-$section to gadget-section-info-$section
Oh I think I see what you mean now. One starts with gadget- and the other starts with gadgets-.
My suggestion is that both should start either with Gadget- or Gadgets- (Gadget- being preferable due to being an older convention and not requiring much changes). Right now it seems unsynchronised between the two despite the messages being related (one is section header and another is section description).
It seemed OK to me. Do you have a suggestion of what we should change it to?
The message name ended up to be a bit confusing since gadget section headers use Gadget-section- convention but these new messages use Gadgets-section-info convention. Personally I think this needs to be fixed before it gets too prevalent. (I tried creating the section description by going to header description from Special:Gadgets and adding -info- and that’s how I spotted the issue.) @SD0001 @Novem_Linguae, what do you think?
Sun, May 4
Sat, May 3
Fri, May 2
Thu, May 1
Change #1109707 merged by jenkins-bot:
[mediawiki/extensions/Gadgets@master] Add support for gadgets section descriptions
This doesn't seem related to Realtime Preview as that just uses the same core feature that live preview does. I've updated the description.
Apr 23 2025
Apr 16 2025
Apr 11 2025
Resetting task status from "In Progress" to "Open" as this task has been "in progress" for more than one year (see T380300). Feel free to set that status again, or rather break down into smaller subtasks.
Apr 8 2025
Apr 4 2025
Mar 26 2025
Does this also mean all those properties get saved in the JSON page? It used to be that way originally, but was removed as it makes the schema harder to evolve (T331222).
Mar 25 2025
On wiki.gg we've implemented most of what I described, with one small difference:
Mar 24 2025
Change #1122193 merged by jenkins-bot:
[mediawiki/extensions/Gadgets@master] Use events instead of hooks where possible
Mar 22 2025
@Xover Note that browser requirements for the optional JavaScript layer are very different from browser requirements to render web pages (HTML/CSS). https://www.mediawiki.org/wiki/Compatibility#Browsers
Mar 16 2025
Mar 15 2025
Change #1109112 merged by jenkins-bot:
[mediawiki/core@master] api: Add query module for retrieving Codex icons
Mar 13 2025
Mar 11 2025
Mar 10 2025
thanks!