Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
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!
jb...@google.com <jb...@google.com> #3
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 )
Description
The new MenuHost API has addMenuProvider methods that can take a Lifecycle and handles the association of the Fragment to the menu based on that Lifecycle. Fragments should pass their ViewLifecycleOwner to the addMenuProvider methods so ensure that the menu items are properly tied to the fragment's view.
We should add a lint rule to help inform developers of this.