This page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.Wikipedia HelpWikipedia:Help ProjectTemplate:Wikipedia Help ProjectHelp
Is there a way to use groups to prevent note lists used only for an infobox from interfering with other note lists used elsewhere in an article? For instance, here, the note "lr note" should be appearing in the "notelist-lr" section, not in the infobox. (Courtesy pinging @Bsherr, as this relates to your change.) Sdkbtalk20:12, 24 April 2024 (UTC)[reply]
The issue is that an article could be using any of the existing predefined forms, so they would all potentially interfere. We also want to keep the lower roman formatting without a visual change. Sdkbtalk21:03, 24 April 2024 (UTC)[reply]
I think Sdkb point is that they want to use {{efn-lr}} style notes, and include a {{notelist-lr}} in the infobox, but not catch Cite error: There are <ref> tags on this page without content in them (see the help page). notes from outside the infobox in that notelist. If they use {{efn-ua}} they would not want to catch {{efn-ua}} notes from outside the infobox. I don't believe there's anyway of doing this with the currently available options. -- LCU ActivelyDisinterested«@» °∆t°22:16, 24 April 2024 (UTC)[reply]
Yes, that's correct, Actively. Too bad there isn't currently a solution — is there a Phabricator ticket or some other technical project that might offer one? Sdkbtalk01:38, 25 April 2024 (UTC)[reply]
EFN only works with the predefined groups. Instead, you can use Reflist or the magic word. Alternatively, we can just remove the notelist from the template and put it at the bottom of each article, integrated with any other explanatory footnotes. --Bsherr (talk) 03:36, 25 April 2024 (UTC)[reply]
Or in other words, {{efn}} is implemented by Template:Efn, with the predefined groups that Bsherr mentioned, whereas <ref>s are implemented by the Wikimedia software, with whatever group names you legally define. So they are not symmetric. And since the {{Efn}} template is not Wikimedia software, a Phab ticket doesn't seem like the right venue. Mathglot (talk) 09:49, 25 April 2024 (UTC)[reply]
Sdkb, I tried a bunch of things, but couldn't find an alternative, but looks like Rjjiii did, and that solution ought to be added to the doc of a few templates so it can be discovered more easily. If you want to follow up at another venue, I would say Module talk:Footnotes, but anyone monitoring there is probably looking here as well, so not sure if practically speaking that will gain anything, but maybe it's worth adding a discussion advisory/feedback request there linking this discussion. Mathglot (talk) 02:04, 9 April 2025 (UTC)[reply]
@Sdkb Posting some more stuff to clarify. So, the ref tags and templates that invoke them like {{efn}} do several things:
Create an anchor link from the superscript callout down the correct footnote.
Highlight the footnote when the superscript callout link is clicked.
Display the footnote in mouseover popup on desktop.
On mobile: replace the above the 3 behaviors with a popup at the bottom of the screen containing the footnote when the superscript callout is clicked.
Automatically create a list of the references with backlinks to the superscript callouts.
The solutions I mentioned above, do the first 3 and not the second two. On mobile, they work like anchor links and there is no mouse-over popup because there is no mouse. It's probably not realistic to try to recreate the mobile behavior. Older versions of those templates used the reference class that ref tags and {{efn}} use. This worked on desktop, but the JavaScript for mobile would just break the links. I tried reporting this, but the solution was just to take out the reference class.
The {{ran}}/{{rma}} and {{listref}}/{{listref/reflist}} template pairs were both created for sort of the same reason. They are meant to avoid creating backlinks. If you cite a couple biographies a hundred times or cite the same directory hundreds of times, then the software goes buckwild and gives so many links they become useless. There is another template {{citeref}} that also does something similar and could be used. (It was made to create links between footnotes, which sounds very useful for the House of Leaves article. While trying out citeref, I started thinking that maybe the best solution isn't actually available right now.
Ran & listref both work, but say you have a navbox and infobox that both use them. In that case, you could end up with duplicate anchor links which are invalid HTML and could make the links point to the wrong target. This is less an issue with {{ran}}, because each template would be picking a letter or handful of letters. So the odds go down pretty low pretty quickly (1/26, 1/676, 1/17576). That said, I think the correct solution is to add something into the callout template and footnote template that is meant just for use in other templates. Call the parameter |tm-id= or whatever is easy to remember. Then when you invoke {{rma}} (or {{listref}} which is just a wrapper for it), you would use the same |tm-id= throughout a single template. This way, it wouldn't matter if you had six navboxes all using the template with [i] because their links would each be using an anchor that is inherently unique: #CITEREFtm-uscollegedamissions-i instead of #CITEREFi
@Sdkb & Mathglot: Changes are done in all 5 template sandboxes. I think this version will just work, and will just work for *box templates in general. If conflicts linking ever do pop up, one template can just use a more specific |tm-id=. Rjjiii (talk) 14:47, 13 April 2025 (UTC)[reply]
I've been meaning to look over the fixes, and haven't had a chance but trust your work. Much thanks for taking this on! Sdkbtalk18:04, 23 April 2025 (UTC)[reply]
"Unique" vs. "distinct
I see "unique" used to mean "distinct", when its precise meaning is the opposite. (Unique name means the same reference has only one name. Distinct names means two references don't have the same name.) I am unable to find the text to change the word. Where is the text? It appears to be linked by "refname rules", but where is that? Zaslav (talk) 23:34, 27 April 2024 (UTC)[reply]
In limited cases, the <ref> generated footnote numbers are breaking lines, even when the <ref> is correctly flush with the preceding characters, i.e. no space. It seems to only occur in Firefox, not Chrome, only in wide mode and not standard and only when logged in (Vector 2022). I used the fluorine article for testing. Just a heads up if anyone is interested. — AjaxSmack19:27, 15 July 2024 (UTC)[reply]
This has been requested before, but not on this page. It's not been done because the amount of work that would be needed simply isn't worth it: cases like this are rare, and are also dependent on factors such as browser, device width, font size etc. --Redrose64 🌹 (talk) 21:33, 15 July 2024 (UTC)[reply]
Thanks for the explanation. It doesn't bother me as long as it doesn't affect the unwashed masses. (And thanks for pointing out in your edit summary that <ref> tags don't belong in headers.) — AjaxSmack22:00, 15 July 2024 (UTC)[reply]
