WebContents.canGoBack/canGoForward are synchronous methods, but the mozbrowser equivalents getCanGoBack and getCanGoForward are async, so our implementations of those methods spin the event loop while waiting for the mozbrowser calls to return. We should figure out a better way to implement those methods.
WebContents.canGoBack/canGoForward are synchronous methods, but the mozbrowser equivalents getCanGoBack and getCanGoForward are async, so our implementations of those methods spin the event loop while waiting for the mozbrowser calls to return. We should figure out a better way to implement those methods.