Extension talk:Popups/2014

Patrolling and maintenance

Navigation popups as we know them are in big part, or even chiefly, about patrolling actions (and other maintenance like disambiguation): see for instance w:en:Wikipedia:Tools/Navigation popups#Features. Are these going to be in scope for this extension on a later stage, after the basics currently mentioned on the page?

If yes it will be useful to ask contributions/suggestions to the maintainers of Navigation popups in various languages, LiveRC (mainly French and Italian), RTRC (mainly Commons), FastButtons (mainly Spanish) and Ajax sysop (mainly cross-wiki). A project idea with a brief outline of requirements/theory of change could be collaboratively edited as a section in Mentorship programs/Possible projects.

After all, what all these have in common is the aim to Make MediaWiki more AJAXy. Nemo 13:47, 11 February 2014 (UTC)

Yes, the design team is working on rolling out Popups for different kind of pages. Please view the progress and leave any suggestions here - https://www.mediawiki.org/wiki/Talk:Beta_Features/Hovercards

These links might also prove useful to you -

1. https://www.mediawiki.org/wiki/Navigation_Popups_(Restyling_and_Enhancements)#Priorities

2. https://www.mediawiki.org/wiki/Talk:Beta_Features/Hovercards#Priority_of_popups_to_roll_out

3. https://trello-attachments.s3.amazonaws.com/51acdf853e84334c1b0005f8/51ace5b6ecc3199919003492/764b146dd360f35eb2017b7ba24d0330/references-popups-07.png

I am currently working on making this extension feature complete and then cleaning up some code. After that I think it'll become a lot easier for people to contribute \o/ Prtksxna (talk) 04:47, 17 February 2014 (UTC)

Thanks. I had read those pages, but they don't mention at all the kind of features I'm talking about, hence my question (which belongs here). I like «it'll become a lot easier for people to contribute \o/», does that mean that patches extending the current scope of the extension will be accepted?

In the meanwhile LiveRC 1.0 was released! It was made so extensible that it.wiki is now able to include it without forking it on a local page. See also w:fr:Wikipédia:LiveRC/Documentation/Présentation/en. Note that LiveRC includes since 2008 or so some features that the WMF recently implemented elsewhere, like a m:Thanks button. Nemo 08:07, 7 March 2014 (UTC)

Suggested feature: popup location based on mouse location

Background: Currently, popup location is based on the element that triggered it. sometimes it's preferrable to use the mouse location instead.

Rationale: two cases come to mind:

1. the "element" is an internal link that's split (word-wrapped) across 2 lines
2. the "element" is a large image

in both cases (and probably others, too), the "element" location may be far away from the mouse pointer, and popping the popup there can be surprising.

note that browser's tooltip is typically relative to the mouse pointer, not the element.

the change is not that hard:

// instead of
 $( '#mw-content-text a' ).on( 'mouseenter focus', function ()
// do
 $( '#mw-content-text a' ).on( 'mouseenter focus', function (event)

pass the event to createBox(); and to sendRequest(), and in createBox(), if event.type === "mouseenter", use event.pageX and event.pageY instead of $el.offset() to calculate popup location. i guess you can't do it on "focus", though.

peace. קיפודנחש (talk) 16:30, 2 April 2014 (UTC)

This feature would be a good solution to fix my problem : the popups are shifted to the right when you use this CSS code to set a max-width to the site layout. Have you or anyone else succeeded to implement mouse location popups? Varlin (talk) 17:57, 31 December 2017 (UTC)

Pop Up is Stuck in Pop Up

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Thanks in advance for any help I can get here. I have installed the following extensions on my version 1.24.1 MW. Text Extract Page Images Popups

The installation went well, the popup functions but it hangs, and will not disappear. I think I am not understanding how to configure the Show/hide timing. I am unable to understand what type of page I am too create and install the following // Time to wait in ms before showing a popup on hover. Default = 500 // @property POPUP_DELAY mw.popups.render.POPUP_DELAY = 1000; // Time to wait in ms before closing a popup on de-hover. Default = 300 // @property POPUP_CLOSE_DELAY mw.popups.render.POPUP_CLOSE_DELAY = 300; // Time to wait in ms before starting the API queries on hover, must be <= POPUP_DELAY. Default = 50 // @property API_DELAY mw.popups.render.API_DELAY = 500;

Do I create a page verbatum per the configuration instructions? Should I create a page Special:MyPage/common.js and then add the code for Show/hide timing? I have done that, and the popup still hangs up.

Any help is greatly appreciated.

Here is the link to our test page at http://www.tpwtestuser.com/mediawiki/index.php?title=Main_Page Please see under "Getting Started" the link "The Hardware Store Page", at this point in our test there is no image popup. John Morris (talk) 07:33, 31 December 2014 (UTC)

Do you want to change the timing just for yourself, or for all users of your wiki? –Quiddity (talk) 01:11, 5 January 2015 (UTC)

Thank you Quiddity, I want to change it as a global. For all users. Thanks for any help! John Morris (talk) 04:34, 5 January 2015 (UTC)

The popup is hanging due to an incorrectly managed dependency on the event logging module - https://phabricator.wikimedia.org/T70341. I have submitted a patch (https://gerrit.wikimedia.org/r/#/c/183765/) to fix this. Prtksxna (talk) 02:22, 9 January 2015 (UTC)

That worked wonderful, all fixed, thanks so much for the fix Prtksxna, this is awesome! Cheers! John Morris (talk) 04:51, 9 January 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.