You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Navigate to and press enter on the "Off-screen span inside link" link to activate it.
Expected: A message box should appear saying "hi".
Actual: The system menu appears.
The problem is that the deepest node (which is the one that NVDA tries to activate) is an off-screen span, which is represented by a paragraph accessible. This accessible has no click action, so NVDA clicks at that position. Unfortunately, the node is off the top and left of the screen, so it winds up clicking the button to activate the system menu.
This is a bit tricky to fix. My first thought was to always use focusableNVDAObjectAtStart, but this would break clickables that aren't focusable. My current solution is:
Try performing the default action as we do now.
If that fails, check for the off-screen/invisible state. If it is on-screen and visible, click as we do now and return.
Otherwise, get the parent and repeat from step 1.
We need to think about whether this could cause any problems.
Note that this isn't a problem in IE. For IE, we only call HTMLNode.click() or use MSAA. I guess IE bubbles the click() up to the link, even though the span itself isn't clickable.
The text was updated successfully, but these errors were encountered:
Reported by jteh on 2010-10-15 06:23
Str:
The problem is that the deepest node (which is the one that NVDA tries to activate) is an off-screen span, which is represented by a paragraph accessible. This accessible has no click action, so NVDA clicks at that position. Unfortunately, the node is off the top and left of the screen, so it winds up clicking the button to activate the system menu.
This is a bit tricky to fix. My first thought was to always use focusableNVDAObjectAtStart, but this would break clickables that aren't focusable. My current solution is:
We need to think about whether this could cause any problems.
Note that this isn't a problem in IE. For IE, we only call HTMLNode.click() or use MSAA. I guess IE bubbles the click() up to the link, even though the span itself isn't clickable.
The text was updated successfully, but these errors were encountered: