Closed Bug 1054111 Opened 11 years ago Closed 11 years ago

"pointer-events: none;" prevents link title from rendering on mouseover

Categories

(Core :: General, defect)

31 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: duncan, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140715214327 Steps to reproduce: Create a file with the following contents, and open it in Firefox: <!DOCTYPE html> <html> <head> <title>title bug</title> </head> <body> <a href="#" style="pointer-events: none;" title="...and here is the reason why">this link is disabled</a> </body> </html> Actual results: The page is rendered, and the link is disabled; nothing happens if I click on it. However, the title is not rendered as a tooltip when I mouse hover over the link. This means that I can't use a tooltip to explain to the user why the link has been disabled, and suggest actions that might enable it. Expected results: I expect that, even though the link is disabled, the title will still render as a tooltip on mouse hover.
pointer-events="none" means be transparent to the mouse so you won't get tooltips. Other UAs work the same e.g. Opera 12 (although you have to use SVG there so see it).
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
Robert, if that's the intended behaviour, what's the recommended approach to explain to a user _why_ the mouse events have been disabled on a link?
There are many alternatives. You could add/remove the href You could recolour it grey so it's more obvious and keep the cursor as default. You could put another link on top that has the tooltip but no href. You could then z-order that away when its enabled.
> You could add/remove the href This is the right way to do it, fwiw, without messing up accessibility. That actually makes it not a link, which is what it sounds like you want Note that a link with "pointer-events: none" is not actually disabled. A user can still tab to it and hit enter.
Boris, thank you. Embarrassingly that never occurred to me; I sometimes fear that years of Windows development has crippled my brain in some way.
You need to log in before you can comment on or make changes to this bug.