Fixed
Status Update
No update yet.
Comments
il...@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!
ap...@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 )
il...@google.com
We've fixed this internally and it'll be available in the next version of Fragments.
Description
Version used: 1.1.0-alpha09
Not sure why you're doing this, but there's a back pressed listener being added to the dispatcher in the initializeChildFragmentManager method, which itself is only called in performOnCreateView. Why isn't the child fragment manager just instantiated when the fragment is first initialized? There are so many bugs around this. Anyway, this means any back pressed listener added in the Fragment's onCreate is essentially pointless since it will always be overridden by the fragment manager's one which pops the back stack. However, back pressed listeners added in onViewCreated work since they're after the FM's listener.