New line numbers alone is fine. Could also do something like "Line X became line Y".
Sat, Sep 30
Wed, Sep 27
I am pretty sure this task is a duplicate of already-linked T334941: Vector 2022: consider displaying References in two columns on narrow screens. I can follow-up on anything specific to the template.
Sat, Sep 23
Fri, Sep 22
Tue, Sep 19
I don't think it's appropriate for a cache not to expire inside a week. The content was reverted on September 6, now some 11 days ago.
Mon, Sep 18
The upstream for Firefox was https://bugzilla.mozilla.org/show_bug.cgi?id=1547294
Sun, Sep 17
Sat, Sep 16
Provide a parser function for adding Codex button markup
Fri, Sep 15
I use wikEdDiff and have definitely gotten used to reading diffs in sans-serif. So personally I'm fine with as-built.
Wed, Sep 13
Mon, Sep 11
There are discussions also happening around T296689 that it is probably worth discussing with them also.
(Given how few uses of NavFrame pl.wp has (around 600, I'd be happy to make it so you don't need that default loading anymore ;).)
Sun, Sep 10
Fri, Sep 8
Sep 2 2023
I think you're looking for https://toolhub.wikimedia.org/tools/patchdemo ?
Aug 31 2023
Aug 28 2023
Aug 27 2023
I guess this is https://en.wikipedia.org/wiki/Help:Pictures#Vertical_alignment , which I had no idea you could set in an image.
Aug 26 2023
Aug 25 2023
Aug 24 2023
Right now the gadget syntax checker doesn't even let you write ES6
A minor point, but this is not true. requiresES6 can be set in the gadget definition which allows ES6 syntax (basically by turning validation off entirely right now and leaving it to the author to ensure their software is void of error).
T164009: Add a HTML5 validator to output of Special:Expandtemplates also exists but would be much more limited in scope I think.
(While looking around for tasks, T200562: Consider not outputting content model violations to help editing clients showed up where ironically I had almost said the exact same thing regarding it and just never posted it. So maybe I haven't mentioned it....)
Aug 23 2023
Aug 22 2023
Honestly I'm not entirely sure. I probably did mean the second part of T151362, just on ?action=info. It's long ago enough that I don't honestly remember. Declining is as good as anything now. If I need I'll file another task for what was proposed there.
That is not a resolution to this task, no. It might be reasonable to say "click the links in Special:Info and then click those edit links is good enough for the product and so we're declining this request" and/or "what you want is the part of T151362: Linter: Display lint errors for a single page which wasn't done which Izno is still sad about", but T301374 is not a resolution.
Aug 21 2023
Categories probably shouldn't even be generated for items. https://www.wikidata.org/wiki/Category:Pages_with_maps has got a few others. Maybe a leftover from some bad deployment or another?
Aug 20 2023
Aug 19 2023
First thought that comes to mind is that Hiero tends to output images that are a pretty solid size, whereas the Unicode basically fits into the size of a normal text character. So some sort of template is probably called for. https://en.wikipedia.org/wiki/Egyptian_hieroglyphs#Phonetic_reading seems exemplary for sizing. IDK if that's necessarily desirable in all places....
Aug 17 2023
Aug 16 2023
@PerfektesChaos since you recently edited the template, you might take a look here and see if anything from your edit needs adjustment?
Aug 15 2023
Aug 14 2023
Aug 10 2023
Aug 9 2023
Special:Search already has a help link (at least on en.wp, IDK what stock MediaWiki provides) in the top right of the page where indicators usually sit. Adding more help to this page doesn't seem like an interface win.