-
Notifications
You must be signed in to change notification settings - Fork 109
Replace webview abstraction layer with browser-engine-system component #1039
Comments
For now I'll keep that assigned to me in order to continue this experiment. I filed this issue to track and document the work happening. |
…ion components to replace WebView abstraction layer.
…ion components to replace WebView abstraction layer.
@pocmo For v3.0, we want to replace AmazonWebView with the SystemWebView #379.
|
Yes. The integration of
What's the time frame for 3.0? According to the milestone it's September 19, 2018? This seems doable.
I see issues with waiting. The WIP patch will rot and we will have to start the integration all over because too much has changed. |
…ion components to replace WebView abstraction layer.
…ion components to replace WebView abstraction layer.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
What's the time frame for 3.0? According to the milestone it's September
19, 2018? This seems doable.
Yeah, that's about right.
|
@mcomella I opened PR #1044 to share the current state. We should be able to provide most of the mentioned missing functionality in 0.21 tomorrow (not everything has landed yet though!). Based on that what's your assessment of the risk compared to doing it later? My gut feeling is to get this in earlier than later and have the ability to iterate with the whole team on it (including QA) and identify problems. Like with |
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
… to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue #379) * Removes the product flavor dimensions that are not needed anymore.
Merged. Follow-up work will continue in #1063. |
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
…ion components to replace WebView abstraction layer. As a side effect: * Replaces AmazonWebView with WebView (Issue mozilla-mobile#379) * Removes the product flavor dimensions that are not needed anymore.
In the next Android components sprints we should have implemented all the functionality to start replacing the webview abstraction layer with
browser-engine-system
(WebView
implementation ofconcept-engine
).I'm currently experimenting with a partially migrated build to identify missing pieces in our engine implementation.
As part of this migration we should be able to use the
feature-session
component here to automatically update the state (browser-session
) from the engine events. With that we no longer need the Proxy and Callback objects.With that finished Firefox for Fire TV should be the first app that uses the core components (
browser-session
<->browser-engine-*
). This will hopefully be the foundation to componetize more functionality and pull in other components that build on top of this core.The text was updated successfully, but these errors were encountered: