App Freezes on opening a new tab from chrome widgets. |
|||||||
Issue descriptionApp Version: 68.0.3398.0 canary iOS Version: 10.3.3,11.3 Device: iPhone,iPad Precondition: 1.Have few SSO accounts saved. Steps to reproduce: 1. Launch chrome & Sign in to chrome. 2. Tap on Menu > Report an Issue. 3. Tap on Dropdown button below in account selection screen. 4. Open new tab from today's view. Observed results: App freezes after new tab is opened. Expected results: App should not Freeze Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: NA Bug reproducible on Dolphin/Safari/Firefox: Safari : NA Bug reproducible on the current beta channel build : NA New UI In M68 Bug reproducible on the current beta channel build : NA New UI In M68 Video : https://drive.google.com/file/d/1HperYuZet5x3gbAXOUGSpV6MapsT_Imr/view?usp=sharing
,
Apr 18 2018
olivierrobin@ could you PTAL?
,
May 25 2018
This issue is reproducible in 67.0.3396.59 Beta Tested on iPhone 7plus(iOS 10.3.3) and iPhoneX(iOS 11.4 Beta)
,
May 25 2018
jlebel, are you owner of this UI?
,
May 25 2018
No this is not my UI. I guess it is for pkl.
,
May 25 2018
Looks like we're not dismissing the feedbackKit dialog when the app re-opens. We should have a pretty standard way of doing this for all our other dialogs. +marq since I asked him a while back to try to come up with a more general solution when we were doing cleanSkeleton. Not sure if any of that made it back into the new design patterns.
,
Jul 2
This happens *only* if user taps on FROM: to choose a from email address (see 0:05 in attached video) to report user feedback. This causes an alert view to be presented from within FeedbackKit which Chrome does not have a easy way to dismiss. Note that Chrome correctly dismisses Report An Issue UI if user wasn't in the FROM alert state.
,
Oct 6
This is still a problem. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by twelling...@chromium.org
, Apr 17 2018