Assigned
Status Update
No update yet.
Comments
ca...@google.com
[Deleted User] <[Deleted User]>
That fix has been cherry-picked into the release branch and will be available in the Fragment 1.5.1 release.
ni...@google.com
kh...@gmail.com
vi...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. TQ3A.230705.001.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. TQ3A.230705.001.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
vi...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
Description
Therefore, this method enables accessibility implementation, such as stopping the carousel that rolls when TalkBack focuses on a specific view depending on the situation.
However, elements in WebView content cannot be checked where TalkBack is currently focusing.
In case of javascript, you can check focused element with document.activeElement method.
But this method is not work in TalkBack.
Because even if I swipe right gesture, real focus is not moving within WebView.
In case of iOS VoiceOver, once VoiceOver focus move to next element, web focus also is moving like press tab key.
So I hope TalkBack should support moving real focus with TalkBack focus.
Thank you.