| Summary: | annotation hovers not showing on chrome | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Editor | Assignee: | Silenio Quarti <Silenio_Quarti> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | john.arthorne, mamacdon, Silenio_Quarti |
| Version: | unspecified | ||
| Target Milestone: | 8.0 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Susan McCourt
I thought initially that the hovers weren't working at all, but then I saw some working intermittently. Just now I hovered on the warning marker at line 341 in bundles/org.eclipse.orion.client.core/web/orion/explorer.js and it took about 8 seconds to get the hover. It works fine for me (no long delays). I have Chrome 14.0.835.202 m. Slightly never version, but I do not think it matters. Susan, is this still happening for you? It can still be quite slow at times, about 5 seconds. Always on Chrome. Especially notice if chrome is bogging down (memory, etc.?) The tooltip creates a text view to show folding annotations. I thought this problem could be caused by the IFRAME loading stylesheets in a slow network (at least the first time the tooltip was shown since the text view was cached). This would explain why I cannot replicate it. Now that the IFRAME is gone, this is certainly not a network issue. I changed the hover delay to show the tooltip from 1 second to half second. I do not expect this to solve the problem, but 1 second seemed to long for me. http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=f62c862cc960c09b2b04de32872a6de57609507a *** Bug 374551 has been marked as a duplicate of this bug. *** Found a case where the tooltip would not show in chrome. In this case, the tooltip fading timeout was not cleared properly and it would hide the tooltip right away on the next invocations. http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=f265c07a8294e3708f21d59b2bf075f6c1be768f I am going to assuming this problem has been fixed by these changes. Please reopen, if anyone still reproduces it. |