Last modified: 2014-06-20 14:39:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T68301, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66301 - Hovercards: increase delay to 500 ms
Hovercards: increase delay to 500 ms
Status: RESOLVED DUPLICATE of bug 64234
Product: MediaWiki extensions
Classification: Unclassified
Popups (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-07 01:51 UTC by kipod
Modified: 2014-06-20 14:39 UTC (History)
5 users (show)

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


Attachments

Description kipod 2014-06-07 01:51:57 UTC
currently delay is 150ms. this is way too quick, and is inconsistent with common UI practice. 
without hovercards, tooltips appear after 300-1000 ms (depends on browser, i guess. i believe ms-word uses 1000). tipsy's default is 300.

there have been numerous complains from users about premature presentation of hovercards. 
IMO, 500 is the right number, but it should never be less than 300ms.

other tickets mentioned in several places that the premature presentation issue is going to be fixed, but i can't see any indication that this is indeed so.


i tried to search for "best practice" for acceptable value for tooltip delay. could not find authoritative source, but it seems that the common values range from 500 to 1500 ms. there's no doubt 150ms is way too short, and this is reflected in users' feedback everywhere.


peace.
Comment 1 Bartosz Dziewoński 2014-06-20 14:39:37 UTC

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

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


Navigation
Links