Steps to reproduce
When there is a link in the bottom-right of a webpage, and a user tries to hover over the link, then the URL tooltip occludes the link and the user can’t click that link.
The user has to first click the tooltip to close it, and then without moving the mouse at all has to click the link again. If the mouse is moved, then the tooltip reappears.
What should happen:
The URL tooltip should move to the right side of the screen when the pointer moves towards the bottom-left.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Ibrahim O.”
Changed Status to “External”
Thank you for your feedback. This issue appears to be a duplicate of one of our internal bugs that has been identified previously which is also publicly unavailable. We would like to inform you that we are currently investigating this issue. Thanks again for your assistance in the investigation.
All the best,
The MS Edge Team
The author of the bug report made a mistake in his first sentence, he said "bottom-right", but I think he meant “bottom-left” as that is where the tooltip pops up.
It is now March 21, 2017 and it has been over seven months to fix what would seem a fundamental aspect of a web browser, the ability to click on a link!
This issue still exists in Edge 41.16299.15.0 - This is easy to replicate and really shouldn’t take too much 'investigation’! Back to Chrome for now!
I just tested in Microsoft Edge 42.17134.1.0 (April Win 10 Update).
It works - IF the hovered element is at the bottom.
URL Tooltip for elements NOT at the bottom is displayed at bottom.
New behaviour: But tooltip for elements at bottom are displayed ABOVE the element. So the hovered element is not hidden by the tooltip anymore.
trying to watch a video and the navigation bar is covered by the url. for some reason all youtube videos insist on showing me the url at the bottom even when fullscreen. as you can see in this screenshot I am at 0:28 of a video and unable to scroll back to 0:00. (this issues happens on other sites as well, as mentioned by many other users.)
this is a duplicate issue to the following, known for years and still not fixed: