-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Theme: Safari Private Browsing mode breaks the theme #592
Comments
I had this same issue and it really scared me briefly (feeling locked out of my server with the endless looping loading graphic in the center of the screen), not knowing how to change to a working theme! Switching from Safari with Private Browsing to Chrome fixed it for me for the moment :) Really scared me though because logging into my server with Webmin has been working just fine in Safari with Private Browsing, right up until I clicked the button to update the Authentic theme from 18.20 to 18.30 (tried logging out and then back in too using Safari). In my Dev Tools inspector the errors were all of this form: [Error] QuotaExceededError (DOM Exception 22): The quota has been exceeded. (in init.min.js and parent.min.js) I'm on CentOS 6.8 with Webmin 1.821 |
It's intended by Safari in private mode browsing. It doesn't support |
It will be fixed in 18.31 |
18.31 is out, please upgrade. |
That was fast! Works great again with 18.31, thanks so much! |
You're welcome. It wasn't fast, really but thanks! |
Not for me. |
In case it's not solved, provide the screenshot with console opened to see an error. |
Did all that. |
:) Provide extra details. Otherwise I can't help. |
OK I will try to do some more testing tomorrow, its midnight here and I really need to hit the sack. |
18.30 works in Safari so long as I am not using Private Browsing mode. In Private Browsing mode, the two sidebars show up, but never anything more than an endless blue spinner in the main content area.
This is in contrast to 18.20 working great in Safari using Private Browsing mode. Attached are the console errors when using Private Browsing mode:
The text was updated successfully, but these errors were encountered: