Issue metadata
Sign in to add a comment
|
Investigate whether WebappActivity#initializeChildProcessCreationParams() causes bad behavior on OOPIF or multiple windows. |
||||||||||||||||||||||||
Issue descriptionThis function is introduced to set the parameters when creating a child process for WebAPKs, but we aren't sure whether the logic work with multi window or with --site-per-process. Fire a bug to track this issue.
,
Jul 20 2016
,
Jan 17 2017
Peter, I don't know enough about this one to triage -- do you think it remains a launch-blocker?
,
Jan 18 2017
It is not a launch blocker because the user can't tell the difference
,
Jan 28 2017
Do you mind expanding a tiny bit? What can the user not tell the difference between?
,
Jan 28 2017
Bumping to P1 as it's currently marked as blocking launch, but feel free to mark non-blocking and set priority lower if we've confirmed this is fine as it is.
,
Jan 31 2017
owencm: Regardless of whether the WebAPK's renderer is running in a Chrome process or a WebAPK process, the WebAPK's UI and functionality are the same. In the long term I think we should make the WebAPK's renderer run in the Chrome process because there are no wins in having it run in Chrome's renderer
,
Jan 31 2017
,
Feb 13 2017
,
May 11 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by yfried...@chromium.org
, Jun 30 2016