MediaWiki talk:Gadget-ReferenceTooltips.js


 * Note: There is also discussion at User talk:Yair rand/ReferenceTooltips

Sync
Could an admin please re-copy User:Yair rand/ReferenceTooltips.js to this page to add the recent bug fix? Thanks. --Yair rand (talk) 19:19, 4 April 2012 (UTC)
 * Done.  Sandstein   17:27, 11 April 2012 (UTC)

Could someone synchronize the pages again, please? --Yair rand (talk) 21:35, 19 April 2012 (UTC)
 * Yes check.svg Done -- Red rose64 (talk) 22:15, 19 April 2012 (UTC)
 * Thank you. --Yair rand (talk) 22:25, 19 April 2012 (UTC)


 * I've made some changes to User:Yair rand/ReferenceTooltips.js and User:Yair rand/ReferenceTooltips.css, to add a delay to the tooltip, functionality for touch screens, and a settings menu including options to change both and a disable button. Could someone please copy them over MediaWiki:Gadget-ReferenceTooltips.js and MediaWiki:Gadget-ReferenceTooltips.css, respectively? Thanks. --Yair rand (talk) 03:05, 11 June 2012 (UTC)
 * ✅ &mdash; Martin (MSGJ · talk) 17:19, 11 June 2012 (UTC)

Hm
Where is element ? Also, disabling of this gadget isn't work (Firefox 13). Saint Johann (ru) 15:48, 17 June 2012 (UTC)


 * is at the bottom of the page, holding the "Privacy policy", "About Wikipedia", and "Disclaimers" links, but only in Vector skin. I had forgotten to also include the equivalent elements for other skins. There was also another bug in working with other skins that I had missed. Now that both bugs, as well as the problem in Firefox, are fixed, could an admin please copy User:Yair rand/ReferenceTooltips.js and User:Yair rand/ReferenceTooltips.css over MediaWiki:Gadget-ReferenceTooltips.js and MediaWiki:Gadget-ReferenceTooltips.css again? (Sorry for having to ask so frequently.) --Yair rand (talk) 19:52, 17 June 2012 (UTC)
 * Yes check.svg Done -- Red rose64 (talk) 20:08, 17 June 2012 (UTC)
 * Thanks. --Yair rand (talk) 20:13, 17 June 2012 (UTC)


 * MediaWiki:Gadget-ReferenceTooltips.js and MediaWiki:Gadget-ReferenceTooltips.css need yet another sync, to fix this bug. Thanks. --Yair rand (talk) 21:06, 2 July 2012 (UTC)
 * Yes check.svg Done -- Red rose64 (talk) 22:33, 2 July 2012 (UTC)


 * Sorry, I made a mistake in the edit to User:Yair rand/ReferenceTooltips.js. Could someone please re-sync the pages to fix this? Sorry about that. --Yair rand (talk) 00:03, 3 July 2012 (UTC)
 * Done. Thank you. Rjd0060 (talk) 02:29, 3 July 2012 (UTC)


 * There was a bug with the script working with iPads, hopefully the recent change to User:Yair rand/ReferenceTooltips.js fixes it. Could an admin sync the gadget page again, please? --Yair rand (talk) 04:56, 5 July 2012 (UTC)
 * Yes check.svg Done -- Red rose64 (talk) 10:26, 5 July 2012 (UTC)


 * Could someone please sync this with User:Yair rand/ReferenceTooltips.js again? Thanks. --Yair rand (talk) 23:40, 21 August 2012 (UTC)
 * Yes check.svg Done -- Red rose64 (talk) 16:13, 22 August 2012 (UTC)

Protected edit request on 11 July 2014
Hello!

Could someone apply these changes to the script?

Helder.wiki 21:22, 11 July 2014 (UTC)
 * ✅ Ruslik_ Zero 19:43, 18 July 2014 (UTC)

NotFoundError
This gadget causes the error: NotFoundError: Node was not found. See T109486. Helder 17:54, 18 August 2015 (UTC)
 * Checked Chrome/FF/IE on Window 7, could not reproduce. What browser were you using? --Yair rand (talk) 18:09, 18 August 2015 (UTC)

I was using Iceweasel 38.2.0. On Google Chrome it is a little more verbose: Helder 18:55, 18 August 2015 (UTC)
 * PS: it also happens when I'm not logged in. Helder 18:56, 18 August 2015 (UTC)

Formatting by stylesheet
To allow users to use custom styling of the highlighted reference, please replace: Note that this class is already defined in MediaWiki:Gadget-ReferenceTooltips.css. Petr Matas 14:44, 9 January 2016 (UTC)
 * Hm, this was actually in the changes that I made to the version in my userspace, but I never ended up requesting a merge, and I can't remember why... Eh. --Yair rand (talk) 04:08, 11 January 2016 (UTC)
 * Yes check.svg Done — Mr. Stradivarius  ♪ talk ♪ 07:25, 13 January 2016 (UTC)

Tooltip is not shown if the reference is above the visible area
Problem description: Open [//en.wikipedia.org/w/index.php?title=Quantum_state&oldid=699514891#cite_note-18 Quantum state#Ref-14]. Reference 14 contains a link to reference 1. If you hover on the link to reference 1, no tooltip is shown, although reference 1 is off-screen (above the visible area). This is because the check for the reference being below the visible area is implemented, but above is not.

Fix: Please replace if( !isTouchscreen && ( window.pageYOffset || document.documentElement.scrollTop || document.body.scrollTop || 0 ) + $(window).height > $( h ).offset.top + h.offsetHeight ) { with var windowTop = window.pageYOffset || document.documentElement.scrollTop || document.body.scrollTop || 0; if( !isTouchscreen && windowTop < $( h ).offset.top && windowTop + $(window).height > $( h ).offset.top + h.offsetHeight ) { Petr Matas 13:20, 13 January 2016 (UTC)
 * Probably easier if you dump the whole code in a sandbox next time, so I can just copy/paste. But ✅ &mdash; Martin (MSGJ · talk) 09:25, 14 January 2016 (UTC)
 * Ok, thanks :) Petr Matas 12:00, 14 January 2016 (UTC)

Sync request
Could an admin please merge these changes? Changes include: --Yair rand (talk) 23:04, 14 January 2016 (UTC)
 * Nested references can have tooltips.
 * Links inside reference tooltips are compatible with hovercards, for those who have the beta feature enabled.
 * Messages are grouped at the top and use mw.msg, for easier localization when imported to other language projects.
 * Reference Tooltips now runs in the Draft namespace.
 * Minor general cleanup.
 * ✅ &mdash; Martin (MSGJ · talk) 09:24, 15 January 2016 (UTC)

jQuery 3
This script contains the lines "" and "" which cause the following warning in the console: JQMIGRATE: jQuery.fn.hover is deprecated Helder 22:54, 7 October 2017 (UTC)
 * Red question icon with gradient background.svg Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. &mdash; Martin (MSGJ · talk) 07:13, 27 October 2017 (UTC)
 * This was resolved by Krinkle —Th e DJ (talk • contribs) 12:38, 1 November 2017 (UTC)

Update suggestion
Hello! I would like to suggest to update to the new version of this gadget I've presented at mw:Topic:Ueqlcc482l9yw8gv. There are numerous bugfixes and added features like Harvard-style citations support. Tooltip style & animations are also updated to be consistent with Page Previews' style & animations. It has been tested thoroughly and used in Russian Wikipedia for several months with no complaints.

Jack who built the house (talk) 11:18, 29 December 2018 (UTC)
 * JS: User:Jack who built the house/Gadget-referenceTooltips.js
 * CSS: ru:MediaWiki:Gadget-referenceTooltips.css
 * All in one for testing purposes: User:Jack who built the house/referenceTooltips.js
 * Support. --Yair rand (talk) 19:44, 6 January 2019 (UTC)
 * ? Jack who built the house (talk) 09:54, 9 January 2019 (UTC)
 * Sorry extremely busy IRL, no time to wiki. —Th e DJ (talk • contribs) 10:43, 9 January 2019 (UTC)
 * These are significantly more changes than I had anticipated when looking at this again today.. This is gonna take me more than 15 minutes to review, so please be patient as I try to take another look later this week. —Th e DJ (talk • contribs) 16:12, 29 January 2019 (UTC)
 * Thanks in advance! Jack who built the house (talk) 23:45, 30 January 2019 (UTC)
 * Yes check.svg Done —Th e DJ (talk • contribs) 16:40, 2 February 2019 (UTC)
 * P.S. you might want to get rid of the cookies in favor of LocalStorage. That helps reduce request size and we won't be bothering the WMF servers with that info any longer. —Th e DJ (talk • contribs) 16:43, 2 February 2019 (UTC)
 * Per T179415 for logged in users it should really be replaced with toggling the gadget in preferences. Galobtter (pingó mió) 07:35, 8 February 2019 (UTC)
 * Thanks! I forgot: jquery.client and mediawiki.notify dependencies are needed too. Jack who built the house (talk) 19:52, 2 February 2019 (UTC)


 * Hello Jack, nice to see you here. My two cents: since I'm sill using Opera 12.18, I was afraid that your new version would not work for me, as for some unknown reason on ruwiki it didn't, but oddly enough that's not the case now, it does work. (Except for the absence of icon in the upper right corner, but that's bearable.) So take my congrats on the success. — Mike Novikoff 02:33, 3 February 2019 (UTC)

Mechanics

 * to be clear, is this ready to go and you would like us to replace:


 * MediaWiki:Gadget-ReferenceTooltips.js with User:Jack who built the house/Gadget-referenceTooltips.js and
 * MediaWiki:Gadget-ReferenceTooltips.css with ru:MediaWiki:Gadget-referenceTooltips.css
 * ? — xaosflux  Talk 13:52, 9 January 2019 (UTC)
 * Yes, that's correct. Right now I have both of these files in my common.js, and it's working properly. Jack who built the house (talk) 14:18, 9 January 2019 (UTC)
 * . Jack who built the house (talk) 14:20, 9 January 2019 (UTC)
 * Hello! Any updates? Jack who built the house (talk) 14:58, 11 January 2019 (UTC)


 * Seems like a good idea.... << FR 10:09, 12 January 2019 (UTC)
 * Pinging MSGJ, who helped with several prior change requests. Would you be able to merge the above changes? --Yair rand (talk) 06:12, 15 January 2019 (UTC)

Interference with links on touchscreen
As reported here, this gadget's feature to show tooltips seems to make links with tooltips unclickable on touchscreen devices: This is particularly inconvenient on navboxes, which uses to show the links on top left. Can this be fixed with a change to this JS? Nardog (talk) 09:50, 4 April 2019 (UTC)
 * TKO (from Template:Abbr)
 * We also have this problem in Ukrainian Wiki after we updated Gadget:Reference Tooltips to the last version. I think it would be the best solution if the words “view this template”, “discuss…” and “edit…” became pressable after you click on vte. If anyone can fix the bug in this way, please do this! --Gzhegozh (talk) 12:35, 5 April 2019 (UTC)
 * I am sorry to bother you, but maybe you can help fix the problem? --Gzhegozh (talk) 15:45, 7 April 2019 (UTC)

I fixed the issue together with another one, reported at en:Template talk:Harvard citation

Please update the gadget by moving the code from en:User:Jack who built the house/Gadget-referenceTooltips.js to here.

you can update in your wiki too. Jack who built the house (talk) 14:00, 10 May 2019 (UTC)
 * just want to make sure that this is the change you are asking for: DIFF. — xaosflux  Talk 19:25, 10 May 2019 (UTC)
 * Yes, I only forgot the comment on top: . Updated my code, now it's correct. Jack who built the house (talk) 19:32, 10 May 2019 (UTC)
 * Jack who built the house (talk) 19:33, 10 May 2019 (UTC)
 * ✅.  ~Oshwah~  (talk) (contribs)   10:21, 11 May 2019 (UTC)

Add support for directionality of ref tags
Since May 2018 we have the ability to use the  attribute in the   tags to specify the directionality of ref tags as right-to-left (RTL) or left-to-right (LTR). This is widely used in pages that cite both RTL and LTR sources, for example on Persian Wikipedia (fawiki, see example). Since the ReferenceTooltips code is used on many wikis, it is ideal to add support for directionality in its enwiki version so that all others who copy it would also benefit from it.

I have already implemented the solution into our copy on fawiki. Please incorporate it here too.


 * This diff shows how the JS code on this page should be changed.
 * This diff shows how the CSS code on MediaWiki talk:Gadget-ReferenceTooltips.css should be modified.

Happy to answer any questions (but please ping me). huji— TALK 14:47, 1 July 2019 (UTC)
 * (Presumably you did not mean to leave in the  there.) --Yair rand (talk) 16:40, 1 July 2019 (UTC)
 * correct; I updated the diff link above huji— TALK 16:46, 1 July 2019 (UTC)
 * The structure of the surrounding code context appears to be substantially different in enwiki's version of this script; I'm not sure it would be a straightforward cut-and-paste. Writ Keeper &#9863;&#9812; 14:54, 2 July 2019 (UTC)
 * ❌ this would need to be thoroughly tested here first, feel free to mock it up as a user script here on wiki and gain some testers. — xaosflux  Talk 19:50, 15 July 2019 (UTC)

Feature suggestion: support for book references
The Cite extension has an experimental feature called book referencing. This feature allows editors to cite multiple parts of an already-cited source using the  attribute. For instance, an editor could cite a book with the citation, and then they could cite page 42 in that book with a second citation.

Continuing with the earlier example, currently when a user hovers over the "p. 42" sub-citation, the tooltip will just contain "p. 42" without the book name. That tooltip is not especially useful. It would be nice if this gadget could handle "book references" more naturally. That is, if a user hovers over a citation of the form  attribute, it would be nice if the tooltip displayed the contents of both the   and   citations. Note that book citations can only go one level deep (you cannot extend a citation that extends another citation), which should make the implementation more straightforward. Thank you for considering this suggestion! MtMNC (talk) 06:51, 2 November 2020 (UTC)
 * The feature in Cite extension was experimental. The project was eventually abandoned unfortunately, see WMDE Technical Wishes/Book referencing. – SD0001  (talk) 07:23, 14 December 2021 (UTC)

Change 2 strings
As it turned out, it can be unclear to users what they are disabling/enabling. So please replace with Jack who built the house (talk) 20:43, 4 February 2024 (UTC)
 * ✅ * Pppery * it has begun... 21:34, 4 February 2024 (UTC)

Update request 9 July 2024
Please update the JS and CSS parts of the gadget:
 * Update MediaWiki:Gadget-ReferenceTooltips.js from User:JWBTH/Gadget-ReferenceTooltips.js (diff)
 * Update MediaWiki:Gadget-ReferenceTooltips.css from User:JWBTH/Gadget-ReferenceTooltips.css (diff)

Changes:
 * Respect the text size the user has in the "Appearance" section by using the   CSS variable and making the font size and several related properties relative (in  ) instead of absolute (in  ).
 * Encode several constants to calculate distances based on them instead of relying on magic numbers.
 * Use  element for the settings link instead of   as more semantically appropriate.
 * Use Codex design tokens in several places (, icon size).
 * Fix the appearance of the tooltip tail (anchor) in Blink browsers in Windows on bigger system font sizes.

Ping me if there are any problems. Jack who built the house (talk) 08:40, 9 July 2024 (UTC)
 * ✅ * Pppery * it has begun... 16:15, 9 July 2024 (UTC)
 * This change breaks font size on Vector 2010. Now my reference tooltip font is larger than the article size. Traumnovelle (talk) 04:41, 10 July 2024 (UTC)
 * cc – Novem Linguae  (talk) 04:47, 10 July 2024 (UTC)
 * Thanks for the report. I guess we'll have to hardcode the font size for Vector 2010 and Monobook as well. Jack who built the house (talk) 05:53, 10 July 2024 (UTC)
 * This is extremely broken for me (using Monobook). Font size is now significantly larger than body copy. (I think it was previously smaller? Or at least the same size.) Footnote boxes are the same width as before but now much less text fits on each line, so the footnote ends up taking 1.5x or more vertical space, which both makes it less legible per se and also covers an excessive amount of the page below. Long footnotes are much less likely to fit on screen. Some footnotes with wider content get cut off horizontally. –jacobolus (t) 06:50, 10 July 2024 (UTC)
 * I think it was previously smaller? It was 13px – a bit bigger than the font size in Monobook.Some footnotes with wider content get cut off horizontally. Can you give an example? Jack who built the house (talk) 06:54, 10 July 2024 (UTC)
 * Here's an example, Lemniscate elliptic functions. Arguably this is an absurdly big formula to have in a footnote (without any breakpoints), and it's possible it spilled out of the width of a popup box even before. But there are at least some number of similar examples in other pages across the wiki. –jacobolus (t) 14:10, 10 July 2024 (UTC)
 * That's very helpful, thanks. I'll make the tooltip scroll horizontally instead of having the formula spill out. Jack who built the house (talk) 14:31, 10 July 2024 (UTC)
 * The width of footnote boxes should also probably be specified relative to the font size, to some consistent number of ems (25 or so? not sure). Then there can be somewhat consistent expectation for authors that readers' view of a popup note will be relatively close to an author's own view. –jacobolus (t) 15:01, 10 July 2024 (UTC)
 * That too, yeah. Jack who built the house (talk) 15:02, 10 July 2024 (UTC)
 * Like this: English Wikipedia Lemniscate elliptic functions 2024-07-12 11-26-19.png Jack who built the house (talk) 11:27, 12 July 2024 (UTC)
 * I assume this is to be fixed by appending the WindowManager to  instead of ? (See T348286.) Nardog (talk) 06:55, 10 July 2024 (UTC)
 * Oh right, using  could actually be a better idea than hardcoding anything (note that reference tooltips are not OOUI-based).Let's see. Before the change the tooltip was 13px across all skins against 14px body size. We want to make it bigger where the body font size is bigger.   is:
 * strictly the body size (14px, 16px, or 20px) in Vector, Vector 2022, and Minerva
 * 14.44px against 15.2px body size in Timeless
 * 12.8px against 12.7px body size in Monobook
 * Here, I'm only afraid that making the tooltip smaller than the body text in Monobook wouldn't be a good idea as this would be hard to read. So, we may still hardcode the size for Monobook as a special case. An alternative would be to have the tooltip font size just equal to the body font size, like in Page Previews and Reference Previews:
 * English Wikipedia DeLancey W. Gill 2024-07-10 07-21-45.png Jack who built the house (talk) 07:25, 10 July 2024 (UTC)
 * Couldn't you just wrap it in ? Nardog (talk) 07:33, 10 July 2024 (UTC)
 * It would just give  to the root font size and bring side effects with it. Jack who built the house (talk) 07:40, 10 July 2024 (UTC)
 * What side effects? Aren't we trying to restore the previous font size (except relative) here? Nardog (talk) 08:13, 10 July 2024 (UTC)
 * Side effects of the element as well as any styles applied to  . By "root font size" I mean 1rem, so it's not relative to the body font size. Jack who built the house (talk) 08:20, 10 July 2024 (UTC)
 * How about applying  (or   or whatever) then? Nardog (talk) 08:26, 10 July 2024 (UTC)
 * There is no problem with that (currently the coefficient is 13/14 to match the usual font size in Vector, 13px); the question is, relative to what. Jack who built the house (talk) 08:33, 10 July 2024 (UTC)
 * The teleport target. Nardog (talk) 17:21, 10 July 2024 (UTC)
 * Hm. There is a problem with, and I can't yet figure out how to solve it.   is located at the end of the DOM and only has as styles. Which means its descendants will be positioned relative to the bottom of the screen, even if they have  . If I use   for a descendant, then its descendants will have fixed positioning relative to the page (which we don't need), even if they have  .If   had that would probably work, but it doesn't.   seems to be intended for fixed-positioned elements like dialogs only. Jack who built the house (talk) 12:51, 11 July 2024 (UTC)
 * Do you have a recommendation on where a script can insert tooltips so the font size etc. are the same as in the content body? Nardog (talk) 15:46, 11 July 2024 (UTC)
 * I believe that  was intended exactly for this use case. (As noted below, access it using  .) It's used by both Codex and OOUI and is meant to be usable by anything else.
 * I haven't looked at how it's used in Codex, but at least OOUI manages to use it to position not just dialogs, but also e.g. dropdown menus (like those on Special:Log).
 * You're right though that the position has to be calculated relative to the bottom of the screen… (I see things like  on those OOUI dropdowns, which is a bit silly). I would guess nobody noticed because those libraries have generic methods to position anything relative to anything else, and they coped with the weirdness automatically. You might want to file a Phab task (and CC people who worked on the feature: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/945825), or you'll have to make your code cope with it too. Matma Rex talk 16:57, 11 July 2024 (UTC)
 * Thanks for explaining. Apart from requiring negative offsets, it also has zero width which makes descendants shrink if they don't have explicitly set width, e.g. try So I'm afraid, unless you set   (which is a bit newer than Grade C browsers) together with , you can't have descendants with variable width also. Jack who built the house (talk) 17:49, 11 July 2024 (UTC)
 * You might want to file a Phab task (and CC people who worked on the feature: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/945825) https://phabricator.wikimedia.org/T369880 Jack who built the house (talk) 00:56, 12 July 2024 (UTC)
 * isn't served by HTML, so I assume you can't just expect it to be there but have to await something. Nardog (talk) 07:36, 10 July 2024 (UTC)
 * https://phabricator.wikimedia.org/source/mediawiki/browse/master/resources/src/mediawiki.page.ready/ready.js works. Jack who built the house (talk) 07:44, 10 July 2024 (UTC)
 * Also, two questions to @Jon (WMF): Is there a chance that CSS variables like  will land in skins other than Vector 2022 and Minerva? Is   reliable to be used by gadgets like this one (that seek the font size more or less equal to the body font size)? Jack who built the house (talk) 08:56, 10 July 2024 (UTC)
 * https://doc.wikimedia.org/mediawiki-core/master/js/module-mediawiki.page.ready.html#.teleportTarget is in the documentation so is therefore stable.
 * The font size variables are not stable as they are not part of https://doc.wikimedia.org/codex/latest/design-tokens/overview.html yet. (FWIW officially CSS variables are currently not covered under the stable policy but that conversation is underway). Jon (WMF) (talk) 23:04, 10 July 2024 (UTC)
 * Got it.The font size variables are not stable as they are not part of https://doc.wikimedia.org/codex/latest/design-tokens/overview.html yet Well, they are on https://doc.wikimedia.org/codex/latest/design-tokens/font.html#font-size. Jack who built the house (talk) 04:10, 11 July 2024 (UTC)
 * Yes you are correct. They are part of Codex now. My bad! Thanks for correcting me. Jon (WMF) (talk) 16:03, 11 July 2024 (UTC)
 * I think it would be fine to have the reference preview font size match the body font size if it's less work to compute. SWinxy (talk) 22:38, 10 July 2024 (UTC)
 * I agree. Having footnote popups match body copy size would be totally fine. (With the proviso that the popup box width should be set using relative units so the width is about the same number of characters, as discussed a bit above.) –jacobolus (t) 00:01, 11 July 2024 (UTC)
 * I think it would look awkward. At least harder to tell apart from body text. Why should it be made bigger? We who stayed on Vector didn't complain. 78.3.197.2 (talk) 19:40, 12 July 2024 (UTC)
 * (Plus I don't want to sound like an old person but footnotes are smaller in physical books. 78.3.197.2 (talk) 19:45, 12 July 2024 (UTC))
 * Disagree per what IP wrote. The old style was fine and I would like it restored. Traumnovelle (talk) 09:25, 13 July 2024 (UTC)
 * Several thoughts:
 * Work to compute is secondary here, but there should be a rationale for smaller font from a design perspective.
 * Technically we don't have the current font size of Reference Tooltips in design tokens that we are recommended to use. Page Previews also use the default font size, 14px.
 * "I think it would look awkward. At least harder to tell apart from body text" – in theory, yes, but in practice, I think, the tooltip content is already well-isolated by border + paddings + shadow. My hypothesis is that you'll quickly get used to the body font size once you enable it. To test this hypothesis, you can add this to your common.css and, after some time, say how it goes. I added it to mine.
 * "footnotes are smaller in physical books" – obviously WP:NOTPAPER, but if the argument goes "Footnotes are smaller in the reference section itself", the counterargument is "The reference in a tooltip is isolated and doesn't compete for space or attention with anything, so there is no reason to downsize it".
 * Jack who built the house (talk) 09:52, 14 July 2024 (UTC)
 * in theory, yes, but in practice, I think, the tooltip content is already well-isolated by border + paddings + shadow If the tooltip content is not enough isolated, we might add a bit more side padding to that end:
 * {| border=1 cellpadding=4 style="border-collapse: collapse; border-color: var(--border-color-base, #a2a9b1)"


 * Increased font size + increased padding
 * Current look
 * English Wikipedia Lemniscate elliptic functions 2024-07-14 10-33-47.png
 * English Wikipedia Lemniscate elliptic functions 2024-07-14 11-54-45.png
 * }
 * More examples with the default text size set to "Small" in the "Appearance" section: current look, increased font size, increased font size + increased padding. Jack who built the house (talk) 12:07, 14 July 2024 (UTC)
 * The main reason to make the text in the popup slightly smaller would be to better fit in a narrow text column, since the popup box is narrower than typical skins have for paragraphs of body copy. If the popup used the same font size as the article body that would also be fine though, in my opinion. It shouldn't be larger though. –jacobolus (t) 14:33, 14 July 2024 (UTC)
 * As I promised, the popup width in my updated version is relative to the font size anyway. Jack who built the house (talk) 14:45, 14 July 2024 (UTC)
 * Footnote boxes are the same width as before but now much less text fits on each line This actually made me think that probably we should also made the tooltip wider when the user opted for the large font size in Vector. Jack who built the house (talk) 06:57, 10 July 2024 (UTC)
 * Do your updates fix the gadget on Vector 2010? Traumnovelle (talk) 09:26, 14 July 2024 (UTC)
 * Yes, see . Jack who built the house (talk) 09:34, 14 July 2024 (UTC)
 * Yes, see . Jack who built the house (talk) 09:34, 14 July 2024 (UTC)

Update request 14 July 2024
This update addresses user complaints voiced in MediaWiki talk:Gadget-ReferenceTooltips.js and includes other changes.

Please update the JS and CSS parts of the gadget:
 * Update MediaWiki:Gadget-ReferenceTooltips.js from User:JWBTH/Gadget-ReferenceTooltips.js (diff)
 * Update MediaWiki:Gadget-ReferenceTooltips.css from User:JWBTH/Gadget-ReferenceTooltips.css (diff)

Changes: Jack who built the house (talk) 09:33, 14 July 2024 (UTC)
 * Make the font size in Vector 2010 and MonoBook the same as before the changes. (In the future, Vector 2010 font size should be fixed by placing the overlay inside ; see T369880.)
 * Make the tooltip width relative to the font size.
 * Increase the height of the tooltip tail (anchor) by 1px (it's hard to resize it proportionately as with other values).
 * Make a horizontal scrollbar appear when the contents of the tooltip exceed the maximum width and can't be wrapped to the next line (example).
 * Make the script reusable by other wikis (and synchronizable across wikis). They can now load it from enwiki while setting their own settings and messages.
 * Rework the settings dialog: turn the enable/disable radio input into a checkbox, turn the "Cancel" button into a close button, reword the labels.
 * Replace a 404 image illustrating the footer link from an extension with a Commons file. It appears when the gadget is disabled from its settings.
 * Fix the page footer when the gadget is disabled from its settings. A new footer link to reenable the gadget was added each time  hook fired on a page.
 * Remove old IE fix (IE is no longer supported by MediaWiki).
 * Do minor chores and code style fixes.
 * ✅ * Pppery * it has begun... 23:22, 15 July 2024 (UTC)