Strange behavior where the mouseover hover dialogues become persistent and cannot be removed unless sidebar is closed and reopened or refreshed
They block mouse clicks so that tabs underneath them cannot be selected. The hover dialogues that get stuck are always for tabs that are no where near the location of the mouse pointer.
For example, I will be switching between tabs at the bottom of my Sidewise dock (I have maney tabs) and I will move my mouse horizontally back to the Chrome browser area and suddenly 2-3 hover dialogues will appear for tabs near the top of the list and get stuck. They will not go away unless the Sidewise dock is closed and reopened.
Otherwise, I think this is a pretty grood extension for Chrome.
Chrome 21.0.1180.89 m
Windows 7 x64
I think the hover dialogues that get stuck are only for pinned tabs (not sure, though).
Edit: I should mention that I am using:
- a multi-monitor setup (1920x1200 x2, Chrome on right monitor)
- Sidewise docked to the right
The bug I discuss above, I cannot reproduce in exactly the same manner on a consistent basis but it does happen very often.
Edit 2: Added screenshot (it's because I want to show that the only tabs I was switching between were the ones at the bottom of Sidewise, but for some reason it triggers the tooltips near the top. Note how the tooltips at the top are layered on top of each other and won't go away even though my mouse is at the bottom of the screen.)
Edit 3: Sorry for repeated edits, but this might be two separate issues:
- Tab tooltips (for pinned tabs only, maybe?) seem to get triggered at random even if mouse is not near the tab whose tooltip is triggered,
- When pinned tabs are mouseovered (thus showing the tooltip for the pinned tab), the tooltip likes to get stuck and not go away unless Sidewise is closed and reopened. I just tested this just now and when I ran my mouse over my pinned tabs, two of the tooltips got stuck.
Edit 4: ALL RIGHT, I can reproduce this on my system by doing the following:
Have some pinned tabs, then put mouse over the areas where pinned tabs are (tooltips do not have to be triggered), then move the mouse pointer horizontally off the Sidewise dock.
Then, while mouse is not in the Sidewise dock window area, move mouse up or down along y-axis, then move mouse back to Sidewise (so that mouse enters Sidewise dock window in a different location on the vertical axis). This will trigger the tooltip for whatever pinned tab the mouse was previously on the last time the mouse was in the Sidewise dock area.
Pretty much every time I do this, the tooltip for whatever pinned tab my mouse was near before will get triggered and will get stuck if I move my mouse back to Sidewise nowhere near the pinned tab. It seems like Sidewise is keeping track of which row was "last highlighted" and is firing the tooltip event if the mouse re-enters the Sidewise dock area.
This does not happen for normal tabs; only for pinned tabs.
Thanks.
Antwort
By hover dialogues do you mean the "tooltip" that normally appears when you hover a row in the tree, describing the row's title/url?
Yes, I mean the tooltip when you hover over a row and it shows the item's title and URL
Thanks for the awesome detailed bug report. This is now at the very top of my todo list! There's at least one other weirdness happening with respect to pinned tabs so I'm going to get everything sorted out with pinned tabs ASAP. I think I'll also add a "Pin tab" context menu item when you right click a row.
By hover dialogues do you mean the "tooltip" that normally appears when you hover a row in the tree, describing the row's title/url?
By hover dialogues do you mean the "tooltip" that normally appears when you hover a row in the tree, describing the row's title/url?
By hover dialogues do you mean the "tooltip" that normally appears when you hover a row in the tree, describing the row's title/url?
Think I found and fixed this problem! I'll post an update here when I release the fix (should be within a few days).
Customer support service by UserEcho
Think I found and fixed this problem! I'll post an update here when I release the fix (should be within a few days).