Check we do something reasonable when launching WebAPK if user has not completed FRE |
|||||||||||
Issue descriptionDon't crash when launching WebAPK if user has not completed FRE
,
Jan 20 2017
,
Jan 20 2017
After talking to Sam, we still need to figure out the UX for this
,
Feb 10 2017
,
Feb 10 2017
,
Feb 10 2017
,
Feb 10 2017
We should test this, but I don't think this will happen much in practice: the user would have had to open Chrome to install the WebAPK and go through the FRE. Right now we don't have backup & restore, so the only way I can see them getting the FRE is if they install it from Chrome, clear all of Chrome's data, and then open the WebAPK.
,
Feb 10 2017
Tested this: you get the FRE when you open the WebAPK and then Chrome opens with the start_url. I continued to get Chrome with the start_url on subsequent invocations until I re-enabled WebAPKs in chrome://flags (lost this when data was cleared.)
,
Jun 14 2017
Sounds like there's renewed interest in this. Sam: do you have pointers to the existing "short FRE"?
,
Jun 16 2017
,
Jun 16 2017
,
Jun 29 2017
,
Jun 29 2017
I don't think this is an important case for WebAPKs per #7, as long as it doesn't crash or do anything pathological. Sounds like that's the case per #8 so long as WebAPKs are enabled.
,
Sep 11 2017
Issue 574425 has been merged into this issue. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by pkotw...@chromium.org
, Jan 17 2017