Status Update
Comments
mo...@google.com <mo...@google.com> #2
Branch: androidx-master-dev
commit 47ac9fee0e3d43b4da33f53b8a2ff590f0d46079
Author: Jakub Gielzak <jgielzak@google.com>
Date: Tue Aug 20 13:57:06 2019
Addressed issues with EditText causing scroll
EditText methods: bringPointIntoView, and handleFocusGainInternal
trigger requestChildRectangleOnScreen in ViewPager2's internal
RecyclerView.
This can cause:
- unwanted scrolling -- e.g. when typing on some API versions
- a jump to page 0 -- EditText sometimes reports over -1M px mScrollX
This fix bypasses requestChildRectangleOnScreen calculations taking
advantage of the fact that PagerSnapHelper constraints valid scroll
values to a snapped position ones, and as a result, the problem is
reduced to choosing the correct currentItem.
Bug: 138044582
Bug: 139432498
Test: ./gradlew viewpager2:connectedCheck
Change-Id: Ia4d3e4e6734183e64f261c7cc76d669deae78da5
A viewpager2/src/androidTest/java/androidx/viewpager2/widget/EditTextFocusTest.kt
M viewpager2/src/main/java/androidx/viewpager2/widget/ViewPager2.java
mo...@google.com <mo...@google.com> #3
mo...@google.com <mo...@google.com> #4
mo...@google.com <mo...@google.com> #5
Passing to Jeremy to get his thoughts
jb...@google.com <jb...@google.com> #6
What we really need is a signal to say when all transitions are done and with it running early, we don't have that. For fragments this means that we could end up moving the fragment to RESUMED
before all the transitions are actually completed and execute some code that is normally fine when the system is settled, but dangerous when it is not.
If moving onTransitionEnd()
might be too dangerous are there other options? If you are in the animateToStart
case should you even get an onTransitionEnd()
. Maybe all external listeners get is an onTransitionCancel()
since you are reversing a transition you started in the middle of it. Is that a safer signal to send back?
I think it is okay to separate the signals as long as they are explicit, but we for sure need a way to know that the Transition system is completely done doing any work and our Views are back in the original state that we passed them in.
mo...@google.com <mo...@google.com> #7
Maybe you could notify at the end of your animateToStart
lambda?
jb...@google.com <jb...@google.com> #8
Per offline discussion, we can move ahead with the solution suggested in
This will change the current order:
start transition > animateToStart > onTransitionEnd() > Runnable > finish up transition work
to
start transition > animateToStart > Runnable > finish up transition work > onTransitionEnd()
This has the implications that if developers are doing something with a specific result in their onTransitionEnd()
callback, they will also need to handle the cancellation case by overriding the new onTransitionEnd(Transition, boolean)
For example, if there is a transition from View_A
to View_B
and the onTransitionEnd()
callback has logic that expects View_B to be the final state, it will now need to add some additional logic based on the boolean in the case that View_A
is the final state.
mo...@google.com <mo...@google.com>
ap...@google.com <ap...@google.com> #9
Branch: androidx-main
commit 889b310dee76183e0f89e76d014728f728190740
Author: George Mount <mount@google.com>
Date: Wed Dec 20 14:35:35 2023
Change order of listeners for seeking transitions.
Fixes: 307624554
When TransitionSeekController.animateToStart() is used,
externally added TransitionListeners will have onTransitionEnd()
called after the animateToStart()'s lambda. Internally-added
listeners will be called before the animateToStart()'s lambda.
Test: new test
Change-Id: Ic6a55916958f85d41c54d7739bde09cfc2352d7c
M transition/transition/src/androidTest/java/androidx/transition/SeekTransitionTest.kt
M transition/transition/src/main/java/androidx/transition/Transition.java
pr...@google.com <pr...@google.com> #10
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.transition:transition:1.5.0-alpha06
Description
Component used: Transition
Version used: 1.5.0-alpha04
Expected:
When using the new
animateToStart(Runnable)
API, I would expect the Runnable to be executed before anyonTransitionEnd()
callback that were set on the transition that was being seeked.Actual:
The logs execute inside the
onTransitionEnd()
callback before the runnable.Steps:
1a. Use predictive back and cancel the gesture
1b. Launch the app and click the "Animate" button, then click the "Cancel Animation" button