Search and Top Navigation
#10954 closed bug (invalid)
Opened February 03, 2015 01:13PM UTC
Closed February 18, 2015 08:51AM UTC
tooltip appearing at [0,0] when the element disappears
Reported by: | amik | Owned by: | amik |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.tooltip | Version: | 1.11.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Sometimes with furious clicking elements with tooltips that appear on hover over master element, the element is not visible/is destroyed before the tooltip appears. Then, the tooltip appears on [0,0] and does not disappear any more. This check for visibility fixes this behavior.
The minimum working example that I was able to produce can be found here:
tested in lastest Chrome - when you hover over the element, it starts rapidly blinking and the tooltip appears for a short time at [0px, 65px]. Normally (when removed the onmouseenter in the fiddle), the tooltip should appear at [50px, 115px].
I know that the jsfiddle is not very realistic case, but still it demonstrates a bug. The same bug appears on my site with very complex structure of elements with tooltips, which 1) I cannot publish 2) is too complicated to demonstrate a simple bug 3) occurs quite randomly.
Suggested simple solution can be found at https://github.com/jquery/jquery-ui/pull/1442 , which was closed as posting as a bug report was requested.
Attachments (0)
Change History (2)
Changed February 03, 2015 01:16PM UTC by comment:1
owner: | → amik |
---|---|
status: | new → pending |
Changed February 18, 2015 08:51AM UTC by comment:2
resolution: | → invalid |
---|---|
status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Replying to [ticket:10954 amik]:
A bug in code that would never exist doesn't matter.
Without a realistic reduced case, we will not change the code.