Last modified: 2007-10-16 19:53:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11515 - Hover functionality on footnotes
Hover functionality on footnotes
Status: RESOLVED DUPLICATE of bug 7908
Product: MediaWiki extensions
Classification: Unclassified
Cite (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-09-30 20:49 UTC by G Tony Jacobs
Modified: 2007-10-16 19:53 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description G Tony Jacobs 2007-09-30 20:49:15 UTC
This isn't a bug; it's a feature suggestion.  I hope I filled out the form correctly.

I very seldom read footnotes in articles, because they involve too much of a departure from my place on the page, and I don't feel like opening a separate tab for them.  I know you can click back from them, but that still breaks up the flow.  If I could hover the mouse over a footnote and have the first line or so of the footnote pop up on the screen, I would read a lot more of them.

If that functionality already exists, and I've just somehow managed to turn it off, please let me know, and please accept my apology for having troubled you.  Otherwise, I suggest it as a feature.

thanks for your time,

Tony Jacobs
Comment 1 Tisza Gergő 2007-10-16 19:53:35 UTC

*** This bug has been marked as a duplicate of bug 7908 ***

Note You need to log in before you can comment on or make changes to this bug.