Lgtm, please add a recording of the flow to the description.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Lgtm, please add a recording of the flow to the description.
Also, added additional comments.
boolean shouldBlock = mBlockAccessibilityEvents;The `shouldBlock` appears to be redundant. You can directly `return false` inside the if conditions where blocking is desired, and let the final `return super.requestSendAccessibilityEvent(child, event);` handle the non-blocking case.
CharSequence className = event.getClassName();
boolean isSeekBarClass =
className != null
&& (className.toString().contains("SeekBar")
|| className.toString().contains("Slider"));
boolean isTextViewClass =
(className != null && className.toString().contains("TextView"));Instead of checking class name strings, which can be fragile and very generic as part of the class name can match, could you check if `event` is an instance of the specific classes - SeekBar or Slider or TextView?
Gurmeet KalraLgtm, please add a recording of the flow to the description.
Also, added additional comments.
I personally doubt that we should do this. Because this issue happens outside of the immersive playback, and the fix will make the behavior inconsitent. If we want to apply the same approach to other seekbars, it is no longer a Chrome XR issue.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
CharSequence className = event.getClassName();
boolean isSeekBarClass =
className != null
&& (className.toString().contains("SeekBar")
|| className.toString().contains("Slider"));
boolean isTextViewClass =
(className != null && className.toString().contains("TextView"));Instead of checking class name strings, which can be fragile and very generic as part of the class name can match, could you check if `event` is an instance of the specific classes - SeekBar or Slider or TextView?
That's the ugly part here. I have tried many other approaches, and none of them works. The problem is the element is nested in the Slide. We don't have any access.
Gurmeet KalraLgtm, please add a recording of the flow to the description.
Yong Li (xWF)Also, added additional comments.
I personally doubt that we should do this. Because this issue happens outside of the immersive playback, and the fix will make the behavior inconsitent. If we want to apply the same approach to other seekbars, it is no longer a Chrome XR issue.
Not sure, what you mean by `I personally doubt that we should do this.`.
Adding a recording to the cl description to demo the impact of the change that is it is not announcing current progress during talkback is possible, right?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Gurmeet KalraLgtm, please add a recording of the flow to the description.
Yong Li (xWF)Also, added additional comments.
Gurmeet KalraI personally doubt that we should do this. Because this issue happens outside of the immersive playback, and the fix will make the behavior inconsitent. If we want to apply the same approach to other seekbars, it is no longer a Chrome XR issue.
Not sure, what you mean by `I personally doubt that we should do this.`.
Adding a recording to the cl description to demo the impact of the change that is it is not announcing current progress during talkback is possible, right?
Sorry for confusing. I mean I am not sure we should try to merge this CL. I personally don't think we should merge this CL.
1. it is ugly
2. it is inconsistent with other seekbar behaviors.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Gurmeet KalraLgtm, please add a recording of the flow to the description.
Yong Li (xWF)Also, added additional comments.
Gurmeet KalraI personally doubt that we should do this. Because this issue happens outside of the immersive playback, and the fix will make the behavior inconsitent. If we want to apply the same approach to other seekbars, it is no longer a Chrome XR issue.
Yong Li (xWF)Not sure, what you mean by `I personally doubt that we should do this.`.
Adding a recording to the cl description to demo the impact of the change that is it is not announcing current progress during talkback is possible, right?
Sorry for confusing. I mean I am not sure we should try to merge this CL. I personally don't think we should merge this CL.
1. it is ugly
2. it is inconsistent with other seekbar behaviors.
Agree, lets discard this change and come up with better alternate to solve the problem.
Consider using `instanceof` checks or comparing with `ClassName.class.getName()` if possible for more cleaner approach.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Gurmeet KalraLgtm, please add a recording of the flow to the description.
Yong Li (xWF)Also, added additional comments.
Gurmeet KalraI personally doubt that we should do this. Because this issue happens outside of the immersive playback, and the fix will make the behavior inconsitent. If we want to apply the same approach to other seekbars, it is no longer a Chrome XR issue.
Yong Li (xWF)Not sure, what you mean by `I personally doubt that we should do this.`.
Adding a recording to the cl description to demo the impact of the change that is it is not announcing current progress during talkback is possible, right?
Gurmeet KalraSorry for confusing. I mean I am not sure we should try to merge this CL. I personally don't think we should merge this CL.
1. it is ugly
2. it is inconsistent with other seekbar behaviors.
Agree, lets discard this change and come up with better alternate to solve the problem.
Consider using `instanceof` checks or comparing with `ClassName.class.getName()` if possible for more cleaner approach.
Done
CharSequence className = event.getClassName();
boolean isSeekBarClass =
className != null
&& (className.toString().contains("SeekBar")
|| className.toString().contains("Slider"));
boolean isTextViewClass =
(className != null && className.toString().contains("TextView"));Yong Li (xWF)Instead of checking class name strings, which can be fragile and very generic as part of the class name can match, could you check if `event` is an instance of the specific classes - SeekBar or Slider or TextView?
That's the ugly part here. I have tried many other approaches, and none of them works. The problem is the element is nested in the Slide. We don't have any access.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
LGTM. Also please add a recordings of the flow that prevents the talkback to announce current progress when accessibility is enabled and other one with progress on toolbar continues when no accessibility/talkback not set.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |