Collection exploration bug

In cases where two separate collections are open in tabs (e.g. first ToRead, then Favorites), clicking "next page" in the ToRead list will bring up the second page of the Favorites list.

That's not really a bug. Which collection is in use is set by cookies. If you want to see different collections at the same time, you need to use two browsers.

>2 MarthaJeanne: I feel iike I'm going crazy. I always thought it worked like you described. However, I just cannot get it to work anymore.

I'm logged into LibraryThing in multiple sessions (main browser, other browser, private window, a (Firefox) Multi-Account Container) and which collection is in use seems to be set server-side. I.e. if I change collection in one browser, in the other browser and other sessions not sharing cookies, the active collection gets changed as well.

If it ever worked like you described (and I remember), this might be a bug?

Can staff chime in on whether the selected Collection is set locally using cookies, or set globally on the server? Is it supported to simultaneously view two different collections in two different browsers?

>4 ianreads: I'm pretty sure it used to be session-based rather than user-based but I've yet to receive clarification from developers. I'll post here once I have an update, thanks!

>5 kristilabrie: Bump!

Bump

Are there any other users at all interested in clearing up this confusion? I'm just asking for clarification at this point, not even a fix or a request. If not, I'll stop bumping this...

It is stored at the server level (not a cookie on the browser). So you won't be able to have a different collection selected per browser window.