Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Hi, thanks for reaching out to us and reporting this issue! Will share this to the internal teams and open a report on your behalf. Will reach back with updates as soon as I have one.
Thanks!
il...@google.com
This has created significant limitations in our app - we need to enable COEP so we can use SharedArrayBuffer for some performance-intensive code, however we currently can't do this and embed YouTube videos at the same time, which we need to support. Credentialless/anonymous iframes would theoretically also solve this issue, but this is not widely adopted in browsers (and WebKit is in fact resistant to implementing it due to user safety concerns: https://github.com/WebKit/standards-positions/issues/45 )
an...@google.com
il...@google.com
We've decided to release a Fragment 1.2.5 bug fix release and will be including this change in that release.
Description
Component used: Fragment Version used: 1.3.0-alpha03
When the Activity receives a callback to
onSaveInstanceState(), all Fragments have theirLifecyclestopped, ensuring that doing aFragmentTransactionbetweenON_STARTandON_STOPis always safe.However, the same is not done for the
Lifecycleassociated with the Fragment'sgetViewLifecycleOwner().Both should be changed at the same time.