t05h Posted June 14, 2022 Posted June 14, 2022 (edited) Hi, Been seeing an issue with both managed/non managed chromebooks of various models where the captive portal page will be centered in the bottom right of the screen so most of the buttons are non-visible. Issue is that this type of window can't be moved by dragging it Anyone seen this or know a fix? I've a hunch its caused by updating to v102.0.5005.75 Thanks Edited June 14, 2022 by t05h
jthompson Posted June 14, 2022 Posted June 14, 2022 Do the page-zoom keyboard shortcuts work? That might bring required page elements into view.
sbodeen Posted June 14, 2022 Posted June 14, 2022 We started experiencing the same thing with version 102. The keyboard zoom shortcuts did not work for us. We are able to use the tab key to move from field to field (blindly) and get users logged in. I haven't seen a fix for this yet. 1
Reverend_Dan Posted June 15, 2022 Posted June 15, 2022 We dont have Chromebooks, However had you had a look at customising the capture portal page. Most firewalls/wifi allow customisation of the page, you could try changing the page or the css in the page. Ive done this with ours to remind the pupils they only need username in our and not the full email address
RegisMK5 Posted June 16, 2022 Posted June 16, 2022 (edited) I made an account just to comment that we're having the same issues with our Chromebooks. Also started after updating to ChromeOS 102. (from 98). I tried updating to beta 103 and had the same results. To give some extra details: -The window cannot be moved, dragged, or closed -No keyboard shortcuts work to manipulate this window. -Blindly typing my username/password is the only way past this screen. -The issue only happens in a pre-login situation. Un-enrolled devices are able to log into their accounts first and have a fully usable browser to log into the firewall with. -Powerwash doesn't help. My next step is to try rolling the Chromebook back to older versions and determine which version the issue first started on. Edit: I can confirm that the issue does not happen on 98 or 101. The issue does exist on 102 and beta103. I'm restricting ChromeOS updates to 101 until the issue is resolved and rolling back the few devices that have updated to 101 via USB. Edited June 16, 2022 by RegisMK5
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now