Captive portal notification blocked on start screen |
||||||||
Issue descriptionGoogle Chrome 54.0.2840.59 (Official Build) beta (64-bit) Revision 0 Platform 8743.65.0 (Official Build) beta-channel samus OS: Chrome What steps will reproduce the problem? (1) Be on the start screen. (2) Connect to a network with a captive portal What is the expected output? Captive portal notification is shown and able to complete connecting to network What do you see instead? Notification bell shows +1, but notification does not show. Clicking on the bell prompts the user to sign in to see notifications. If the user's account requires GAIA reauth (as it often will while traveling) the result is a blocked state. It can be escaped by going to guest mode, but the user would need to know that and not have it blocked by policy Lots of hands touching notifications lately. CCing a few people who might know what's up.
,
Oct 17 2016
+scunningham@ to repro/categorize if this is something new in M54
,
Oct 17 2016
This is the first I've seen of notifications not displaying on the start screen. Makes total sense to not show anything user specific when not in a logged in state, but system-level notifications (captive portal, battery level, etc) should show on all screens.
,
Oct 17 2016
,
Oct 17 2016
aashutoshk@, have you seen this against our captive portal setups?
,
Oct 18 2016
+yoshiki as per chat with Albert
,
Oct 18 2016
any updates here? aashutoshk@ were you able to repro?
,
Oct 19 2016
I was not able to reproduce this issue on Testing team's captive portal network using Samus (8743.65.0 build). I tried using captive portal on OOBE, login screen (add user) and logged in as a user and it works as expected. @abodenha : Can you please provide a couple of screenshots? so we know what exactly is failing
,
Oct 19 2016
Is this a regression?
,
Oct 19 2016
I was also not able to repro this on 54.0.2840.65 (8473.67.0). I can access to the captive portal login page without problem. Step (OOBE) 1. Powerwash the ChromeOS 2. Connect a wifi with the captive portal 3. Agree the terms 4. See the captive portal notification and the captive portal login page after a sec Step (GAIA Reauth) 1. Power on and see the Chrome OS login screen 2. Connect a wifi with the captive portal 3. Enter a wrong password several times (Chrome OS falls back to GAIA login) 4. See the captive portal notification and the captive portal login page after a sec
,
Oct 19 2016
Removing RBS since others can't repro this. I'll try again when I get back to my hotel tonight and grab a screenshot.
,
Oct 26 2016
Can't repro. :-( |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by xiy...@chromium.org
, Oct 17 2016