In T301056#7693446, @alexhollender_WMF wrote:

@Jdlrobson @BrandonXLF is it possible to see a before & after comparison of this change?

In T301058#7693466, @alexhollender_WMF wrote:

@BrandonXLF what operating system and browser are you on? also to note, from the screenshot it looks like this is the non-JS version of the ULS

I've submitted https://gerrit.wikimedia.org/r/746005 to resolve T64722, which could make this task unnecessary. With the change, the log entry would look like:

The fix that was used on the beta cluster only applies to the tabs that are added by the skin, and not the ones added by user scripts using mw.util.addPortletLink.

This was brought up at the English Wikipedia's Village Pump https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Remove_footnotes_from_a_copy%3F

@Jdlrobson I split the part of this task about the new Vector skin off into T288367 since it was not addressed by the reason you closed this task and its really a separate issue.

In T288336#7266567, @Jdlrobson wrote:

Vector doesn't officially support nested dropdowns. Why can this not be done as part of the gadget that adds that nested dropdown?

Possibly some overlap with T287052

In T153367#7137447, @Tranve wrote:

More styles should be added to improve the appearance, and wikipage.content hook should be fired.

A query shows that there are 6 million unique non-automatic edit summaries that use this syntax https://quarry.wmflabs.org/query/54289 and considering normal links are already handled like this, I don't see why templates shouldn't be.

Sounds good, hoping for the best!

@Krinkle How would I work on this if there's no active owner? I would love to work on this as it could solve the same issues that the UseResource extension can, but if there's no one to review my commits what's the point?

From what I can tell the only way to solve this would be to add more fields to existing tables that track if the transclusion is directly caused by wikitext, create a new table that stores "template links" rather than transclusions, or to only store direct transclusions in the templatelinks table. The first two options would require changes to the database.

T19571 could also provide similar functionality.

That mostly works, but there are still issues if it's done that way. Let's say template A redirects to template B. If page 1 transcludes template A and template B, but page 2 just transcludes template A, they will appear the same in the templatelinks table, making it impossible for WhatLinksHere to correctly display links.

The task couldn't be implemented without adding new functions and config options to HTMLForm to avoid potential XSS injections.

One major use case would be the {{Empty section}} and {{Expand section}} templates at the English Wikipedia. The templates would be able to use this magic word in edit links by adding &section={{SECTION}] to the links. This would make it easier for editors to help expand these sections and not have to navigate to them by scrolling through the editor for the entire page. See this section on the Village Post.

In T275402#6849357, @Legoktm wrote:

This seems to solve a long-standing request for the Gadgets extension T63007: Allow specifying when a gadget should load (conditional category, action, or namespace) among others. But I think adding a separate extension for this will just add more technical debt, and we're already in a lot of debt with Gadgets. I think working on finishing Gadgets 2.0 would be a much better use of resources than trying to deploy and maintain a separate extension, if you'd be interested in working on that.

In T275402#6849230, @RhinosF1 wrote:

How does the differ from TemplateStyles?
Is there any plan to deploy this to WMF sites? just seen

I've gone through the prerequisites at https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment and all of the ones that need to be done have been completed.

There are several ways the behaviour of the magic word can be implemented since templates can have sections.