LivelyKernel / LivelyKernel/lively.morphic

[browser] detect unsaved changes + warn on navigation

Open
#94 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13
Forks
1
PR merge metrics
No merged PRs in 30d

Description

  • put red dot (save indicator) into code panel
  • prompt on navigation if unsaved

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the browser code panel and the navigation handling mentioned in the issue. The work is done when unsaved edits show a red save indicator and navigating away prompts before those changes are lost.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.