LivelyKernel / LivelyKernel/lively.morphic
[browser] warn if there are unsaved changes
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
... on navigate
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 locating the browser navigation handling associated with the issue's “on navigate” note. Determine how unsaved changes are represented and where navigation can be intercepted; done means the browser warns before navigating away when changes have not been saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100