Bookmarked zoom levels thrown away
-
I was told Windy does not remember your favorite view, and to use a browser bookmark instead.
OK I used
https://www.windy.com/-Rain-thunder-rain?rain,24.182,120.866,8 but
https://www.windy.com/-Rain-thunder-rain?rain,24.182,120.866,5
is where it snaps to, so what's the point?
-
I don't seem to have that problem.
Clicking your link:
https://www.windy.com/-Rain-thunder-rain?rain,24.182,120.866,8Results in the following URL for me:
https://www.windy.com/-Rain-thunder-rain?rain,24.182,120.866,8,i:pressure,p:offThe zoom level (8) is retained and my presets of Pressure On and Particle Animation Off are added.
Perhaps it is related to your particular setup? I'm using Windows 10 and Chrome v75.0.3770.80
-
I find if I "Open link in incognito window" it works correctly.
But I open it in a normal (logged in) window, it gets zoomed to the default (5) zoom.
https://community.windy.com/assets/uploads/profile/796886-profileavatar.png is my picture, so
796886 must be my UserID. So maybe one of the technical staff could see what the matter is. Thanks.
Seen in Version 75.0.3770.80 (Developer Build) built on Debian 10.0, running on Debian 10.0 (64-bit) of Chromium, but not in Firefox. Wait, happens logged out too in Chromium... But not in Incoginto window...
-
Does it also happen if you are not using the Developer Build?
(I'm starting to think that many of your issues could be related to your perhaps non standard setup)In any case let's get the Windy team to have a look too.
@TomSlavkovsky please check and reply
-
OK I went into chrome://settings/content/siteDetails?site=https://www.windy.com/ and cleared all data,
and now it is functioning properly, both logged in or logged out. But...geez! OK thanks everybody. Now on to the next issue...
-
@jidanni said in Bookmarked zoom levels thrown away:
OK I went into chrome://settings/content/siteDetails?site=https://www.windy.com/ and cleared all data,
and now it is functioning properly, both logged in or logged out. But...geez! OK thanks everybody. Now on to the next issue...Thanks for the update.
