degmods/degmods.com
6
1
Fork 0
Code Issues 24 Pull Requests Actions Packages Projects 3 Releases Wiki Activity

Cache field data of the current active page, in mod submission, remain? #166

New Issue
Closed
opened 2024-12-01 11:12:06 +00:00 by freakoverse · 1 comment
freakoverse commented 2024-12-01 11:12:06 +00:00
Owner
Copy Link

Idea here is, if the user is in the mod submission page, fills up the fields with data, clicks publish, but for some reason it hangs or doesn't publish, and the only option left for the user is to refresh the page, then doing so would clear all fields. If possible, can field data remain upon refresh (but if they go to a new tab or close the current tab, said data would of course go away).

Idea here is, if the user is in the mod submission page, fills up the fields with data, clicks publish, but for some reason it hangs or doesn't publish, and the only option left for the user is to refresh the page, then doing so would clear all fields. If possible, can field data remain upon refresh (but if they go to a new tab or close the current tab, said data would of course go away).
freakoverse added the
Kind/Enhancement
Priority
Low
 labels 2024-12-01 11:12:06 +00:00
freakoverse added this to the Issues project 2024-12-01 11:12:06 +00:00
enes commented 2024-12-02 10:48:18 +00:00
Collaborator
Copy Link
  • Local storage for the cache
  • Wipe storage on successful publish
  • Add form reset button (with confirmation Are you sure?)
- [x] Local storage for the cache - [x] Wipe storage on successful publish - [x] Add form reset button (with confirmation `Are you sure?`)
freakoverse moved this to Done in Issues on 2025-01-15 12:35:49 +00:00
freakoverse moved this to Done in Issues on 2025-01-15 16:41:42 +00:00
enes moved this to Done in Issues on 2025-01-15 18:12:52 +00:00
enes moved this to Done in Issues on 2025-01-15 18:33:38 +00:00
enes moved this to Done in Issues on 2025-01-15 19:23:34 +00:00
freakoverse moved this to Done in Issues on 2025-01-27 11:54:34 +00:00
freakoverse moved this to Done in Issues on 2025-01-28 01:09:46 +00:00
freakoverse moved this to Done in Issues on 2025-01-28 01:12:01 +00:00
freakoverse moved this to Done in Issues on 2025-01-30 17:30:51 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Enhancement
Priority
Low
Milestone
No items
No Milestone
Projects
Clear projects
No project Issues
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: degmods/degmods.com#166
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?