Open sanjay1909 opened 6 years ago
Summary of the Issue
Issue 2 was addressed here, https://github.com/nvaccess/nvda/issues/4903 . Thanks
Was this in browse or focus mode.
It's in Browse Mode with Checkbox selected for Automatic focus for focus changes
https://codepen.io/anon/pen/MGdYRW In this example, I removed the tabindex on the child, But still, the click event attached for the
cc: @jcsteh, @feerrenrut I think I can reproduce this issue in NvDA 2019.1.1 but since I canot use a pc without a screen reader I cannot really tell what happens when testing without NVDA running.
Without getting into the details, I'm not 100% sure what the test code is telling us. I got the following results without NVDA running: Pressing space with the parent div focused
ParentClick[0] ParentKeypress[1] ChildClick[0] ChildKeypress[0]
- parentKeyPress
Clicking on the child div:
ParentClick[1] ParentKeypress[0] ChildClick[1] ChildKeypress[0]
- childClick - parentClick
This issue requires work to clarify. The template has not been followed correctly and the expected results of the test case are also not explained. There should also be some explanation as to why the expected behaviour should be the case. The issue is unlikely to get worked on in it's current state.
@sanjay1909 how is this behavior in NVDA 2019.3 Beta 1? Could you please give an update?
@sanjay1909 try listening to keyup event on child, possible event timeline:
FYI: I encountered this situation when using material ui component, my solution is to move focus to child on keyup instead keydown.
@sanjay1909 is this still an issue with NvDA 2024.2 or 2024.3 Beta?
Steps to reproduce:
Expected behavior:
Actual behavior:
System configuration:
NVDA version: 2018.1
NVDA Installed or portable:
Windows version:
Name and version of other software in use when reproducing the issue:
Other questions:
Does the issue still occur after restarting your PC? Yes
Have you tried any other versions of NVDA?