Chrome Version       : Stable 61.0.3163.100
OS Version           : Win10
Screenreader         : NVDA


It is inconvenient especially when a popover is auto-prompted (e.g. Extension added) and the user is triggering a shortcut (e.g. Ctrl+W, Ctrl+Q). Repro the issue by setting focus on the following popovers:
- Bookmark (e.g. Ctrl+D and Ctrl+W)
- Save password
- Permission
To compare, tab modals (e.g. Resubmit form) allow shortcuts for the same rationale. Popovers should not have higher restrictions than tab modals. On OSX, popovers allow shortcuts as well, as desired.

Recommended fix:
- Popovers to allow shortcuts


Videos* (.. - issue):
- https://drive.google.com/open?id=0B1VXa3kr2lYjSEJpMHlveWQ0bnc
- Extension added: https://drive.google.com/open?id=0B1VXa3kr2lYjTGV3R1VMNGIwT0U

Videos* (not issue, correct references):
- Mac OSX: https://drive.google.com/open?id=0B63LqjsMmAX_QUxoSFZXNENQNGs
- Win Tab modal: https://drive.google.com/open?id=0B1VXa3kr2lYjZWRHMnlPSWhZRVE

Full doc*: go/ar-dialogs-win-2017
*: Docs and videos are google internal


Recommended fixes:
- If an implementation to fix this bug covers all other dialogs in the same type, it will be ideal.
- If it's a spot fix for a listed dialog, we can still use the fix as a reference for future fixes for others. 
- Please discuss if the issue needs to be clarified further, and/or if there's an alternative fix. 
- Independently, expanded tests are needed for 1) Harmony flag enabled, 2) Win10+JAWS, 3) CrOS+ChromeVox, and 4) OSX+VO, and also modification of this bug is needed if the same issue occurs on 1)-4).

Thanks!

 

Chrome Version       : Stable 61.0.3163.100
OS Version           : Win10
Screenreader         : NVDA


It is inconvenient especially when a popover is auto-prompted (e.g. Extension added) and the user is triggering a shortcut (e.g. Ctrl+W, Ctrl+Q). Repro the issue by setting focus on the following popovers:
- Bookmark (e.g. Ctrl+D and Ctrl+W)
- Save password
- Permission
To compare, tab modals (e.g. Resubmit form) allow shortcuts for the same rationale. Popovers should not have higher restrictions than tab modals. On OSX, popovers allow shortcuts as well, as desired.

Recommended fix:
- Popovers to allow shortcuts


Videos* (.. - issue):
- https://drive.google.com/open?id=0B1VXa3kr2lYjSEJpMHlveWQ0bnc
- Extension added: https://drive.google.com/open?id=0B1VXa3kr2lYjTGV3R1VMNGIwT0U

Videos* (not issue, correct references):
- Mac OSX: https://drive.google.com/open?id=0B63LqjsMmAX_QUxoSFZXNENQNGs
- Win Tab modal: https://drive.google.com/open?id=0B1VXa3kr2lYjZWRHMnlPSWhZRVE

Full doc*: go/ar-dialogs-win-2017
*: Docs and videos are google internal


Related notes:
- If an implementation to fix this bug covers all other dialogs in the same type, it will be ideal.
- If it's a spot fix for a listed dialog, we can still use the fix as a reference for future fixes for others. 
- Please discuss if the issue needs to be clarified further, and/or if there's an alternative fix. 
- Independently, expanded tests are needed for 1) Harmony flag enabled, 2) Win10+JAWS, 3) CrOS+ChromeVox, and 4) OSX+VO, and also modification of this bug is needed if the same issue occurs on 1)-4).

Thanks!

 

Chrome Version       : Stable 61.0.3163.100
OS Version           : Win10
Screenreader         : NVDA


It is inconvenient especially when a popover is auto-prompted (e.g. Extension added) and the user is triggering a shortcut (e.g. Ctrl+W, Ctrl+Q). Repro the issue by setting focus on the following popovers:
- Bookmark (e.g. Ctrl+D and Ctrl+W)
- Save password
- Permission
To compare, tab modals (e.g. Resubmit form) allow shortcuts for the same rationale. Popovers should not have higher restrictions than tab modals. On OSX, popovers allow shortcuts as well, as desired.

Recommended fix:
- Popovers to allow shortcuts
- When closing parent tab/window or quitting Chrome, dispose their belonging popovers (i.e. prevent a bug like crbug.com/605374)

Videos* (.. - issue):
- https://drive.google.com/open?id=0B1VXa3kr2lYjSEJpMHlveWQ0bnc
- Extension added: https://drive.google.com/open?id=0B1VXa3kr2lYjTGV3R1VMNGIwT0U

Videos* (not issue, correct references):
- Mac OSX: https://drive.google.com/open?id=0B63LqjsMmAX_QUxoSFZXNENQNGs
- Win Tab modal: https://drive.google.com/open?id=0B1VXa3kr2lYjZWRHMnlPSWhZRVE

Full doc*: go/ar-dialogs-win-2017
*: Docs and videos are google internal


Related notes:
- If an implementation to fix this bug covers all other dialogs in the same type, it will be ideal.
- If it's a spot fix for a listed dialog, we can still use the fix as a reference for future fixes for others. 
- Please discuss if the issue needs to be clarified further, and/or if there's an alternative fix. 
- Independently, expanded tests are needed for 1) Harmony flag enabled, 2) Win10+JAWS, 3) CrOS+ChromeVox, and 4) OSX+VO, and also modification of this bug is needed if the same issue occurs on 1)-4).

Thanks!

 

Chrome Version       : Stable 61.0.3163.100
OS Version           : Win10
Screenreader         : NVDA


It is inconvenient especially when a popover is auto-prompted (e.g. Extension added) and the user is triggering a shortcut (e.g. Ctrl+W, Ctrl+Q). Repro the issue by setting focus on the following popovers:
- Bookmark (e.g. Ctrl+D and Ctrl+W)
- Save password
- Permission
To compare, tab modals (e.g. Resubmit form) allow shortcuts for the same rationale. Popovers should not have higher restrictions than tab modals. On OSX, popovers allow shortcuts as well, as desired.

Recommended fix:
- Popovers to allow shortcuts
- When closing parent tab/window or quitting Chrome, dispose their belonging popovers (i.e. prevent a bug like  crbug.com/605374 )

Videos* (issue):
- https://drive.google.com/open?id=0B1VXa3kr2lYjSEJpMHlveWQ0bnc
- Extension added: https://drive.google.com/open?id=0B1VXa3kr2lYjTGV3R1VMNGIwT0U

Videos* (not issue, correct references):
- Mac OSX: https://drive.google.com/open?id=0B63LqjsMmAX_QUxoSFZXNENQNGs
- Win Tab modal: https://drive.google.com/open?id=0B1VXa3kr2lYjZWRHMnlPSWhZRVE

Full doc*: go/ar-dialogs-win-2017
*: Docs and videos are google internal


Related notes:
- If an implementation to fix this bug covers all other dialogs in the same type, it will be ideal.
- If it's a spot fix for a listed dialog, we can still use the fix as a reference for future fixes for others. 
- Please discuss if the issue needs to be clarified further, and/or if there's an alternative fix. 
- Independently, expanded tests are needed for 1) Harmony flag enabled, 2) Win10+JAWS, 3) CrOS+ChromeVox, and 4) OSX+VO, and also modification of this bug is needed if the same issue occurs on 1)-4).

Thanks!