Open
Bug 1124853
Opened 10 years ago
Updated 3 years ago
Accidental refresh loses all changes
Categories
(DevTools :: Inspector, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: fitzgen, Unassigned)
References
Details
Should be able to get them back if I make a bunch of edits and then accidentally refresh.
Comment 1•10 years ago
|
||
Could you be a little bit more specific about the sort of edits you have in mind? Just all of them (new/changed attributes in the markup-view, edited HTML, news css properties, ...)?
If we limit ourselves to CSS at first, I think the solution lies in something I wanted to get done last year but didn't: having a global resourceStore actor that knows the list of resources that have been loaded. Sort of a new cache layer for devtools, but writable. All changes made through the devtools would be written in this store, allowing us to export diffs, for instance, but also do things like re-apply the changes after a reload of the page from the server (if they still apply).
That's a big and complex project, but we need such a resource store, I'm sure (btw, it would also make style-editor/rule-view syncing much easier).
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(erabug)
Comment 2•10 years ago
|
||
Nick generously posted on behalf of a comment I made, specifically about accidentally refreshing while tweaking CSS properties. A cache layer solution that would allow me to re-apply previous changes sounds great.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(erabug)
Comment 3•9 years ago
|
||
This bug is somewhat linked to the topic of getting a diff of the user changes which was flagged as high priority during the creative tools work week (see related bugs).
If we can dynamically compute such a diff, it should be easy to save it and propose to the user a way to restore a previous session's diff after reloading the page.
For now P3/enhancement.
Inspector bug triage. Filter on CLIMBING SHOES.
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•