Issue metadata
Sign in to add a comment
|
Regression:'Network connection error' notification goes off immediately in 15 sec |
||||||||||||||||||||||
Issue descriptionChrome Version: 64.0.3270.0/10136.0.0 dev-channel Peppy,Paine,gnawty OS:Chrome OS What steps will reproduce the problem? (1)Recover Build->In 'Connect to network' screen ->click on any network and enter some wrong password >>'Network connection error' notification is given ->Observe it Actual:'Network connection error' notification goes off within 15-20 seconds of time Expected:'Network connection error' notification should stay until it is noticed by user. This is a Regression issue as same is working fine in 64.0.3246.0/10055.0.0 dev channel Paine Note:Issue is not seen in Linux,Windows OS @Yoshiki: Please confirm the issue
,
Jan 17 2018
Hi Yoshiki. Since this bug is tagged as a Release blocker, can you please help assign it to the right person?
,
Jan 29 2018
Pinged on IM; need to get some traction for these RBS M64 bugs
,
Jan 30 2018
Reping since the bug hasn't been updated.
,
Jan 31 2018
Let me fix
,
Jan 31 2018
,
Jan 31 2018
+estade@ for notifications +sgabriel@ for UX Was it an intentional change to have system notifications time out by default? Do we really want these notifications to persist? Personally I think that allowing them to disappear is preferable. I am unclear what the value in having them persist is. The user can still attempt to reconnect and will receive a new error if they have forgotten the passphrase.
,
Jan 31 2018
Removing RBS since not clear this is a real issue. Re-tag if otherwise.
,
Jan 31 2018
I agree, not RBS. I think it's fine to have this one go away on its own. The rest of the oobe UI makes it obvious you still need to connect to a wifi network and I don't see a need to re-summon the notification after 15 seconds. It seems likely this changed in 2395de65c82b1d877b9e6530768dd5a33ba1177c although when I look at that patch again I can't see why it would have been the culprit (it seems never_timeout wasn't true with or without the patch).
,
Feb 6 2018
As I checked, the issue itself is fixed on ToT and M65 by 2395de65c82b1d877b9e6530768dd5a33ba1177c, so the CL that I created is not fixed anything. Does it truly need to be fixed on M64? If necessary, I'll create a CL only for M64 to fix this.
,
Feb 6 2018
64 is already stable, that shipped has saled. I think we can just close it out. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kbleicher@chromium.org
, Jan 4 2018