MoeraOrg / MoeraOrg/moera-issues
Make bfcache usable
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Caching in the browser's back-forward cache (bfcache) allows Moera client to be loaded instantly when user returns to it by pressing Back button (https://habr.com/ru/company/yandex/blog/496360/). But there are many restrictions for placing a page into bfcache. For example, WebSockets connection should be closed on pagehide and restored on pageshow. Need to solve all these issues and ensure that Moera client is cached in bfcache successfully.
Also, Moera browser extension does not distinguish when a page is restored from bfcache and injects the standard script into it that kills the whole content of the page and reloads the client.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the linked bfcache restrictions and the browser client's pagehide/pageshow handling, then inspect the Moera browser extension's injected script behavior. Done means the client can be restored from bfcache without a destructive reload, with WebSocket connections handled across restoration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100