Skip to content
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

Clear preferred version setting "cookie" when new version is released #149

Open
huonw opened this issue Feb 14, 2024 · 4 comments
Open

Clear preferred version setting "cookie" when new version is released #149

huonw opened this issue Feb 14, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@huonw
Copy link
Contributor

huonw commented Feb 14, 2024

It seems the "default" version is 2.18, but we've released 2.19.0 stable, so 2.19 should be the default. For example, the links in the navbar are:

@huonw huonw added the bug Something isn't working label Feb 14, 2024
@huonw
Copy link
Contributor Author

huonw commented Feb 14, 2024

Hm, I cannot reproduce this locally either with npm start or npm run build. 🤷

@tgolsson
Copy link
Contributor

tgolsson commented Feb 14, 2024

🍪 . (Though actually local storage: docs-preferred-version-default: 2.18). Will fix the title.

@tgolsson tgolsson changed the title Default version is 2.18, despite 2.19 being released Clear preferred version setting "cookie" when new version is released Feb 14, 2024
@huonw
Copy link
Contributor Author

huonw commented Feb 14, 2024

Huh, good catch! Do you know if that cookie can be controlled by users explicitly and/or how it gets set?

Just thinking that if a user is, say, using 2.16 and sets that as their preferred version, it'd be suboptimal to clear it. (It's probably tolerable, just trying to explore the possible "breakage" explicitly.)

@kaos
Copy link
Member

kaos commented Feb 15, 2024

I experimented a bit with this after reading Tom's comment as well.. and from what I could tell, the "preferred version" is only set when selecting a particular version from the drop down, which is limited to only the most recent few versions.. if I go back to the "all versions" page there are (currently broken) links, which doesn't seem to stick when followed. Which makes this less of an issue I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants