Ultrawide	16:9	16:10	4:3	5:4
2560 × 1080	1280 × 720	1280 × 800	1280 × 960	1280 × 1024
3440 × 1440	1600 × 900	1600 × 1000	1600 × 1200	1600 × 1280
3840 × 1600	1920 × 1080	1920 × 1200	1920 × 1440	1920 × 1536
	2560 × 1440	2560 × 1600	2560 × 1920	2560 × 2048
	3840 × 2160	3840 × 2400	3840 × 2880	3840 × 3072

Wide	Ultrawide	Portrait	Square
All Wide	All Portrait
16 × 9	21 × 9	9 × 16	1 × 1
16 × 10	32 × 9	10 × 16	3 × 2
	48 × 9	9 × 18	4 × 3
			5 × 4

Seen tags not loading

Posts: 3 · Views: 104

Dainyl – 7 years ago13384
The 'Seen' tags are showing up on thumbnails when I open a wallpaper in another tab but are gone when I refresh or load a different page (like my subscriptions). Looking into the LocalStorage using the dev console it seems that you're trying to store seen wallpapers as an array in 'wallhaven.seen_wallpapers' but every time I load a wallpaper it's being replaced by an array with only the new entry and even that is ignored on load.

I'm running Google Chrome Version 60.0.3080.6 (Official Build) dev (64-bit) on Windows 7.
Gandalf – 6 years ago13389
That's interesting, I've not hard of any issues like that so far. Have you checked to make sure there are no settings in your browser preventing access/persistent storage of the data in localStorage? Maybe any Addons that may be interfering?
Dainyl – 6 years ago13402
Okay. I tested it without addons and it still wasn't working. As for settings, I haven't changed anything recently and can't find anything that mentions localstorage at all but Chrome likes to hide the advanced settings so maybe I missed it. I haven't been having issues with localstorage on other sites or even local .html files. At this point I'm thinking it's a JavaScript issue with in the Chrome dev version I'm running. I'll check the Chrome support pages to see if I can learn anything.

Edit - OK. After some more debugging I discovered that the hasOwnProperty function was sometimes failing to return the correct value and causing your code to believe that there was no 'wallhaven.seen_wallpapers'. According to the Chrome bug tracker, hasOwnProperty has been acting up for a few months now and they are currently working on a fix. So it seems it was a Chrome issue after all.
Last updated 6 years ago