Status Update
No update yet.
Comments
jb...@google.com
ap...@google.com
possible dup
jb...@google.com
coming back to this issue. I see this is because we just cannot really drag handle behind the screen (because the "pointer" of the handle is where we select the text, so the handle need to be out of the screen to select the last letter).
That being said, if being super careful I'm able to select the whole first word even with no padding (sometimes takes a few attempts).
Siyamed, how do you deal with this in the platform text? Frankly, I expect no text to be at the very edge of the screen in the real apps, and since it's possible to select by just raising the selection handle higher (positionning at the line above seelcted the whole line) idk how big the problem is.
Anyway, reassigning to Siyamed to investigate the selection in the platform for clues or ask someone from the text team to do it.
Description
Component used: Core
Version used: 1.7.0-alpha02. Also affects Activity
1.4.0-alpha01and up.When using the
addMenuProvidermethods that take aLifecycle, callingremoveMenuProviderdoesn't actually remove the underlyingLifecycleObserverthatMenuHostHelperadds.This has a couple of implications:
removeMenuProvideris called when the Lifecycle is below the givenstate,removeMenuProviderdoesn't remove theMenuProviderand when the Lifecycle reaches the given state, it still gets addedremoveMenuProvideris called when the Lifecycle is above the givenstate,removeMenuProviderdoes remove theMenuProvider, but if the Lifecycle goes down and then back up again, it gets re-added.ActivityResultRegistryhandles these cases (registerwith aLifecycleOwner, then callingunregister) byLifecycleOwner+LifecycleObserverinstancesMenuProvideras the key.