We need to change MailboxToSurfaceBridge / ARCore's usage of it in order to clean things up. This task includes refactoring ARCoreDevice into two classes - one that implements the ARCoreDriverAPI and lives on the GL thread and the other that handles calls to/from blink and lives on the UI thread. This will make the usage of threads clearer and hopefully clean up the code substantially - needing less callbacks etc.

klausw@ and lincolnfrog@ have plans for this

 

We need to change MailboxToSurfaceBridge / ARCore's usage of it in order to clean things up. This task includes refactoring ARCoreDevice into two classes - one that implements the ARCoreDriverAPI and lives on the GL thread and the other that handles calls to/from blink and lives on the UI thread. This will make the usage of threads clearer and hopefully clean up the code substantially - needing less callbacks etc.

klausw@ and lincolnfrog@ have plans for this:
The current usage in WebVR requires setting a surface on it before creating the context provider. I'm in favor of refactoring this, i.e. by adding multiple constructors, or by splitting into a context-establishing class that passes a freshly created method-providing class to OnMailboxBridge ready.