Variants are not kept in memory on the user side
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 29k
- Forks
- 4k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 71
Description
When accessing documentation created with GitBook, the page doesn’t seem to keep in memory which variant/version you saw last. Whichever has been set as "home" on the creator side is the default, so users have to switch to whichever variant they use every single time they access the page, which is a bit annoying.
How to replicate:
- Open a site with variants (such as this)
- Change to a non-default variant
- Open the site in a new tab - It will automatically go to the default version, even when accessing through a search engine
Thank you for your help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue on a GitBook site with variants, such as https://beta.docs.soda.io, by selecting a non-default variant and opening the site in a new tab or through a search result. Trace the frontend entry point that selects the active variant and make the last-selected variant persist across navigation; done when the selected variant opens again instead of the creator's default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100