Was looking at what was left in blink for mojo conversions. Do we have a plan for attack for the
RevocableInterfacePtr?
I wonder if it is really necessary to keep this plumbing. It seems that it is used in
1)
Speech Recognition, this already is a ContextLifecycleObserver so it could just close the binding and the receiver in the ContextDestroyed callback.
3)
CacheStorage is a ContextClient but it could be upgraded to a ContextLifecycleObserver.
4) NativeFileSystem, seems to create a bunch of them in their call graphs but they can all get a handle to the ExecutionContext so I believe they could be LifecycleObservers.
Kentaro any opinions, I presume we should close some of these mojo channels for frozen tabs too...