This page has archives. Sections older than 90 days may be automatically archived by Lowercase sigmabot III when more than 15 sections are present.
This page is for discussing Navigation popups and reporting bugs you encounter with it. Please be aware that the original author of Popups (Lupin) is no longer active on Wikipedia. All issues are handled at the discretion of other experienced editors. Note that this project has an associated Phabricator project where implementation-related discussion happens.
result in tooltips with url code between the action term and 'Hint', like: un|watch for any watch/unwatch, and delete for images (hover to see). I guess the altering of action needs to be moved to the switch statement in the wikiLink function (starting at line 6178).
Another one is email user – the i18n key 'EmailuserHint' (line 7049) needs a capital U.
With kind regards — Mar(c). 12:20, 7 January 2019 (UTC)
IPv6 /64 ranges
It would be useful if links for IPv6 addresses (in contributions and watchlists), when moused over, could have an option to produce a list of contributions for the /64 range to which the address belongs instead of just the specific /128 address.[1]
One way to do this would be by splitting the link into two pieces, like this:
When you mouse over the left side, you should get the contribs for the 2A02:C7F:202:7500::0/64 range (which currently doesn't work). When you mouse over the right side, you get the contribs for just the specific 2A02:C7F:202:7500:14B3:9AA7:46A3:B9E0/128 address.
References
^As I understand it, IPv6 addresses are typically allocated in /64 blocks for each user by the provider. E.g., instead of your ISP allocating you a single IPv4 address of 189.201.223.245 (/32), and your router doing network address translation to your internal network of about 256 addresses in a block like 192.168.1.0/24 in a private use range, for IPv6 they will allocate 2A02:C7F:202:7500::0/64 to you and your internal network devices are assigned their addresses from that block (2A02:C7F:202:7500::0 through 2A02:C7F:202:7500:FFFF:FFFF:FFFF:FFFF).
Since some weeks in german WP the visual diff view is active. But there the navigation popups dont work. They works only if I switch to the old wikitext mode.
Is there a bug, or must I do some settings?
Technical (I am web developer): It seems to me, there exists no event listeners for mouse movement.--Hlambert63 (talk) 17:42, 18 April 2023 (UTC)[reply]
It might be a race condition: if the visual diff loads first, by the time NavPopups loads, the diff is there and therefore the popups are added; however, if NavPopups loads first, it doesn’t find the visual diff on load, and later it doesn’t check it again (due to visual diffs not notifying it by firing the hook). —Tacsipacsi (talk) 00:43, 23 April 2023 (UTC)[reply]
@Tacsipacsi When the timing is the reason: Is it possible to load or re-ping / restart the NavPopups later in my Users common.js? (currently I activated it via a checkbox in my Settings)
@Tacsipacsi I meant, not I will find a way, but I could find a way for this, but I dont know, what function I must call to reload or restart NavPopups to re-establish the mouse-event-listeners.--Hlambert63 (talk) 13:19, 1 June 2024 (UTC)[reply]
I have found a 2nd bug: In Visual Diff the links to references leads to the article diff, I'd expect a link to the ref in ref-section (but it may be a collision with other popup-tools / -settings! – sorry *streichel* – I know a bulk of incoming bugs! ;-) )--Hlambert63 (talk) 18:04, 4 June 2023 (UTC)[reply]
No dab links when using {{Place name disambiguation}}
I can't duplicate that behaviour. Here, hovering over Central Coast (which uses {{place name disambiguation}}) or Clark County (which uses {{geodis}}) both yield pop ups with their content. The difference I notice is that the pop ups for the former don't offer "Click to disambiguate this link to:", which is annoying and might be worth fixing. -- Michael Bednarek (talk) 05:16, 26 October 2023 (UTC)[reply]
Yes, when I said it will not display dab links, I meant the "Click to disambiguate..." followed by each of the links. I just changed Mount Reynolds back to using {{place name disambiguation}} and it currently illustrates the issue. I wonder if the number of redlinks it currently has is what is causing the issue. In the case of Central Coast I wonder if the headings are causing the issue. RedWolf (talk) 19:08, 26 October 2023 (UTC)[reply]
Indeed it depends on the template name. This is again an ancient feature that doesn’t make use of features introduced to MediaWiki in the past decade or so. It matches the page wikitext against the regexp
/\{\{\s*(d(ab|isamb(ig(uation)?)?)|(((geo|hn|road?|school|number)dis)|[234][lc][acw]|(road|ship)index))\s*(\|[^}]*)?\}\}|is a .*disambiguation.*page/im
Apparently, {{Place name disambiguation}}, and others, call {{dmbox|type=disambig}} which then emits that magic word. Could Popups use that? Which text is interrogated by that regex? The wikitext an editor sees, or an expanded version that gets displayed? Can Popups see categories applied by templates, or only those specified in the wikitext? -- Michael Bednarek (talk) 14:27, 27 October 2023 (UTC)[reply]
I went the easier route, modifying my popups configuration:
popupDabRegexp='(\\{\\{\\s*disambig(?!uation needed)|disambig\\s*\\}\\}|disamb\\s*\\}\\}|disambiguation\\}\\}|dab\\s*\\}\\})|\\{\\{\\s*(((geo|hn|road?|school|number)dis)|[234][lc][acw]|(road|ship)index)(\\s*[|][^}]*)?\\s*[}][}]|is a .*disambiguation.*page';
PS: I just noticed that I took the code for popupDabRegexp from the overleaf documentation as my starting point, not from mw:Gadget-popups.js; they are slightly different. The decentralised discussions and documentation are irritating. -- Michael Bednarek (talk) 01:48, 29 October 2023 (UTC)[reply]
I now took the regex at mw:Gadget-popups.js as my starting point and came up with:
popupDabRegexp='disambiguation\\}\\}|\\{\\{\\s*(d(ab|isamb(ig(uation)?)?)|disambiguation\\}\\}|(((geo|hn|road?|school|number)dis)|[234][lc][acw]|(road|ship)index))\\s*(\\|[^}]*)?\\}\\}|is a .*disambiguation.*page';
Talk page timestamp links have been deployed to multiple wikis (all except English Wikipedia at the moment, example) and this gadget tries to show a preview when you hover on them, however as the fragment does not correspond to a section, the preview is always just of the entire talk page, which isn't very useful. I would suggest that any link with the class ext-discussiontools-init-timestamplink be ignored. More generally you may also want to ignore any hash fragment starting #c- or #h- as these don't correspond to a page section. ESanders (WMF) (talk) 13:05, 30 January 2024 (UTC)[reply]
The feature isn't available on English Wikipedia yet as we are still back-filling the index table required to do the redirecting when a comment is archived. In the meantime you can enable clickable timestamp links using my commentlinks.js user script (example). ESanders (WMF) (talk) 07:44, 31 January 2024 (UTC)[reply]
I noticed this hovering over a link for Eurofighter Typhoon - the article's infobox has both an SVG logo used in branding and an image of the plane. in the code, this is accomplished thus:
In this case, the popup displays the logo, which is less useful than showing the image. I guess it does need to be able to use either | logo or | image, but which is more appropriate is conditional - an example of an article with an infobox containing both an image and a logo where the logo is more appropriate would be Bayer. Improving this might be a pain - use the image by default, but the logo if the article is categorised using any of the categories within Category:Companies? One cookie (talk) 13:51, 6 February 2024 (UTC)[reply]
@One cookie: I wouldn't worry about it, as this tool is aimed at editors not readers. As the documentation says, the code just picks the first image it comes across in the wiki text. At User:John of Reading/X2 I've swapped the parameters over, and popups is displaying the plane rather than the logo. -- John of Reading (talk) 14:25, 6 February 2024 (UTC)[reply]
Feature request: popups at bottom of page should not be cut off by bottom of page
When hovering over a link that is near the bottom of a page, it'd be awesome if the popup was displayed at the top of the link instead of going out of frame at the bottom, just like classic article previews. Thanks a lot! Cocobb8 (💬 talk • ✏️ contribs) 16:20, 22 February 2024 (UTC)[reply]
By “classic article previews”, you mean mw:Page Previews, which is about a decade younger than NavPopups, right? 🙂 There are some differences (apart from the time difference of a decade) because of which the always-bottom display makes more sense in case of NavPopups than it would in case of Page Previews:
Page Previews always shows a constrained-length popup, while NavPopups popups can get very long (e.g. if I hover over the “contribs” link in your signature, I get a popup that’s almost twice as tall as my entire screen), thus
it’s much more likely that the popup doesn’t fit in the screen either way, and it’s even possible that it doesn’t fit the document; if a popup overflows at the bottom (or right) of the screen, browsers usually extend the scrollbar so that even the very bottom/right of it is visible, but if it overflows at the top (or left), it’s clipped and the overflowing part is inaccessible;
if some part of the popup doesn’t fit the screen, it makes more sense for it to be the bottom, as the first sentence of the article (which defines what it’s about), the latest page history entries (which are usually the most relevant) etc. are on the top.
NavPopups features a lot of tools and links, which are all at the top; if the popup was displayed on the top, one would move the pointer more to reach them. Page Previews has a single tool (the settings), which is hardly ever needed, its only purpose is to show the preview of the article. (Notice the difference in the name: Navigation popups is for navigation, Page Previews is for previews.) —Tacsipacsi (talk) 15:27, 23 February 2024 (UTC)[reply]
Articles that are protected in some sort (such as the POPUPS page) have protection padlocks as topicons. They normally have hover text to indicate duration. However, navpops replaces that with a preview of the linked page, and doesn't display the hover text anywhere for some reason. Aaron Liu (talk) 11:41, 14 March 2024 (UTC)[reply]
I'm not saying it doesn't show the linked page; I'm saying that the hover text, like "Editing of this page is restricted to autoconfirmed users indefinitely", doesn't show. Aaron Liu (talk) 12:47, 14 March 2024 (UTC)[reply]
Feature request: Support for colored text
Hello!
I've come up with a potential upgrade that could make NavPopups even better than they already are:
Having preview popups support colored text would be a win! This would not find any uses in the mainspace, but would be quite useful in showing an accurate preview of people's user pages that include specially formatted/colored text.
Currently, the "revert" function does not allow users to add an edit summary explaining the revert. Only the default edit summary (Revert to revision xxxxxxxxxx dated yyyy-mm-dd hh:mm:ss by User using popups) can be used.
My question is: Would it be possible to modify Navigation Popups to allow users to put more information in the edit summary, in addition to what already exist? Unexplained reverts are bad for Wikipedia, especially when a good faith edit is reverted without reason in the edit summary. InTheAstronomy32 (talk) 12:11, 25 April 2024 (UTC)[reply]
Wiki tags are always excluded
Howdy, may I ask a hopefully simple question. At the moment, any text between any wiki tags is always excluded from the navigation popup. This applies to standard tags like <span> but also to self-defined tags used in a small private extension. <span> is a very common way to modify the appearance of text, e.g. <span style="color:#FF0000"> but of course we would like to see the spanned text within the popup. Is there a way, or will there be plans, to define a list of wiki tags/html tags that will simply be stripped off the article without also removing the embedded content text? 2003:C2:3F21:FD00:FD5B:946E:6956:E8CF (talk) 10:46, 3 May 2024 (UTC)[reply]
No objections here. But it's more limiting and frustrating that a popup only seems to be shown below the link, even when it's on the bottom of the screen. -- Michael Bednarek (talk) 12:05, 24 June 2024 (UTC)[reply]
Perhaps width logic can be modified to allow something similar... Though I think there where some options that influence width (so it might be dynamic...). Not sure. Nux (talk) 21:12, 24 June 2024 (UTC)[reply]
Yeah, I already do it for myself (and similar at non-Wikimedia wikis), but perhaps others might appreciate it? As we grow older, things look smaller! Quiddity (talk) 21:23, 24 June 2024 (UTC)[reply]
Property values on Wikidata
On Wikidata, when a user hovers over the value of a property, it would be useful if the popup displayed the description of the linked item, in the user's preferred language, if present.
For example, on Black Sabbath (Q47670), the value of location of formation (P740) is Birmingham (Q2256), whose description in English is currently "city in West Midlands, England". the title is useful for disambiguating the target from others with the same name, such as the one in Alabama. A null description would alert the user that one is required, at Wikidata.
Whenever I hover over an item that shows the name of somebody in their native language, your app or whatever zaps it, as if "I'm not interested in those funny foreign characters". Well, that is the whole point of me wanting to see the mouseover. For instance, hover over Kawahara Keiga. We see "Kawahara Keiga ( , also known as..." You see that "( ,"? That's where the silliness occured. Jidanni (talk) 21:38, 18 October 2024 (UTC)[reply]
It has nothing to do with “funny foreign characters”: simply all templates are removed, whether they contain Japanese text, English text or non-text content. This is a known limitation, and one that’s unfortunately not likely to go away in the near future. —Tacsipacsi (talk) 08:44, 19 October 2024 (UTC)[reply]
