Pages won't load after a period of time
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start by reproducing the failure in Firefox 152: open a book page, leave the tab for a couple of days, then try to open another page. Trace the page-loading flow from the site entry point; done means navigation completes normally or fails quickly with a reload prompt instead of leaving an endless progress bar.
Written by the indexing model from the issue text.
Description
Repro:
- open some page of the book
- wait a couple of days
- get back to that tab
- try to open another page (e.g. the next one)
- it won't load, showing you a fake-ish progress bar on the top which never completes
It should either work as expected, or at least fail quickly and prompt to reload the tab (or maybe reload the tab by itself, idk if that's a thing).
Firefox 152, both Desktop and Mobile.
My humble opinion on vuepress
While your website styling looks nice, the overall site not as clean and "balanced" as a simple mdbook. I've never ran into issues like this one with mdbook and I can also see that it's working much better on mobile when you use landscape orientation: I tested both on iPad and on my Android smartphone and found out that 1. Vuepress sites doen't collapse the header despite it uses a lot of screen estate in such scenario. 2. The sidebar is always shown without the ability to hide it - same behavior as in desktop version. 3. "go up button" is overlapping "next page" button when you're at the end of the page, etc.I've had a very similar experience with https://sotrh.github.io/learn-wgpu/ which also uses vuepress, except it was even more basic.
I appreciate the effort, just want to indicate that the experience can be made better without spending much resource.
- Dominant language
- TypeScript
- Stars
- 258
- Forks
- 561
- Avg merge
- 3h 20m
- Merged PRs (30d)
- 15
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.
More from nushell/nushell.github.io
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
nushell/nushell.github.io#2081 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
nushell/nushell.github.io#767 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
nushell/nushell.github.io#2232 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
nushell/nushell.github.io#2209 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
nushell/nushell.github.io#2155 · 1 comment ·
All issues in nushell/nushell.github.io
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100