(Resending; forgot to reply all.) > No the BrowserToolbar would have a webView property that points to the > current active webView. That is the only thing it has to know about. > > So the only thing that needs to happen when we switch a tab is: > > browserToolbar.webView = newWebView > > Or probably a bit higher level in our case: > > browserToolbar.tab = newTab > > Which can take the webView from the Tab.
I think you're describing what we already have. With the current abstraction, a Browser == a tab. It has high-level information about the page (title/URL/favicon/bf state). These are the same properties BrowserToolbar (and other tab clients) would care about. We currently expose webView simply as a UIView for layout, but this can be changed to WKWebView if needed by BrowserViewController. I'd strongly prefer to avoid interacting with the WebView directly in other places, though -- in terms of our abstraction model, we want to interact with a browser/tab interface, not a view. _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
