RESOLVED MOVED 220086
AX: <details> element cannot be interacted with using Voice Control
https://bugs.webkit.org/show_bug.cgi?id=220086
Summary AX: <details> element cannot be interacted with using Voice Control
Oliver Byford
Reported 2020-12-22 08:11:39 PST
Created attachment 416664 [details] Screenshot of numbers overlay without an overlay for the details element Given the following markup: <a href="https://www.google.com">Google</a> <br><br> <details> <summary>Details</summary> <p>These are the details!</p> </details> <br><br> <button type="button">Click me</button> <br><br> <a href="https://www.google.com">Google</a> With Voice Control enabled, say 'Click Details' Expected behaviour: The details element should be expanded. Actual behaviour: Nothing happens. Alternatively, you might try saying 'Show numbers' – Expected behaviour: A number overlay should appear near the 'Details' summary, allowing you to interact with it by saying 'Click [number]' Actual behaviour: No number overlay is shown for the 'Details' summary element (see screenshot)
Attachments
Screenshot of numbers overlay without an overlay for the details element (738.98 KB, image/png)
2020-12-22 08:11 PST, Oliver Byford
no flags
Example HTML (417 bytes, text/plain)
2020-12-22 08:12 PST, Oliver Byford
no flags
Patch (2.55 KB, patch)
2021-03-08 00:54 PST, Joone Hur
cfleizach: review-
Radar WebKit Bug Importer
Comment 1 2020-12-22 08:11:50 PST
Oliver Byford
Comment 2 2020-12-22 08:12:01 PST
Created attachment 416665 [details] Example HTML
Joone Hur
Comment 3 2021-03-08 00:54:14 PST
chris fleizach
Comment 4 2021-03-09 12:44:59 PST
Comment on attachment 422549 [details] Patch Hi Joone. Thanks for the patch. But I think this needs to be fixed by Voice Control. Marking this as a button is not technically correct. VC needs to allow this object to be tappable I think
chris fleizach
Comment 5 2021-03-09 12:46:13 PST
Moved to internal component. Voice control will need to support this
Oliver Byford
Comment 6 2021-03-10 01:38:30 PST
Thanks both for looking into this. Is there any way to stay up to date with the bug now it's been moved to Voice Control? Or is it just internally tracked from here?
chris fleizach
Comment 7 2021-03-10 07:11:05 PST
Unfortunately not really. You could create a duplicate feedback and follow along with that but that’s a bit of unnecessary work.
Note You need to log in before you can comment on or make changes to this bug.