Verify that WebAPKs and Chrome don't use the same renderer if they both display the same page |
|
Issue descriptionIf a user is using a WebAPK with tests.peter.sh/notification-generator/ and is also viewing tests.peter.sh/notification-generator/ I think that Chrome might use the same renderer If Chrome uses the same renderer for both, uninstalling the WebAPK will cause the Chrome page's renderer to crash (because the renderer is hosted in the WebAPK)
,
Mar 8 2017
When clank is showing the same page as the webapk and the webapk is running in the background, if i manage to crash the webapk on resume showing clank has stopped working, on reload, clank would show a blank page and reload, the webapk would show a blank page and reload as well. I think there is a chance that they're using the same renderer.
,
Mar 9 2017
We care about this in the context of the render for WebAPKs running in the WebAPK process. In particular, we want to ensure that uninstalling the WebAPK does not crash Chrome. In the case of the WebAPK using a renderer in Chrome's process I expect Chrome to use the same renderer for a page in the WebAPK and in Chrome with the same URL
,
May 1 2017
|
|
►
Sign in to add a comment |
|
Comment 1 by pkotw...@chromium.org
, Feb 15 2017