Whole canvas as image drop target?
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Hi, excited for the project, thank you.
I was working on my first posts, a photo blog from my recent trip, and as I was putting photos in I dropped one too far over to one side, I think, and the browser full-screened the file and unloaded the orkl site. When I went back, the work in progress was gone!
Several ideas here.
* Make the `` tag the receiver for image drops
* At intervals, save a WIP to local storage in case of accidental navigation or browser close.
* Or have an option for auto-saving... not sure how that works out with DAT and app performance though.
I haven't had time to dive into the code myself but I'll probably fiddle around with making some of these changes myself soon, if feedback here doesn't guide me in an alternate direction.
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is identified. First clarify whether the goal is whole-page image drops, local-storage recovery, or configurable autosave; done would require an agreed approach that preserves work after an accidental navigation or browser close without unacceptable app-performance impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100