Improve manifest editor save / validate UX

RESOLVED WONTFIX

Status

()

Firefox
Developer Tools: WebIDE
P1
normal
RESOLVED WONTFIX
4 years ago
3 years ago

People

(Reporter: jryans, Assigned: jryans)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [manifest editor])

The initial version of the manifest editor integration from 922193 relies on the user to click "Update" to do the following:

* Re-validate the manifest
* Save the manifest

Should re-validation happen immediately after you make a change in the editor?  (Probably.)

Should the manifest be save immediately, or will that confuse / surprise users?  If it requires pressing a button, should be part of the "Update" button, or some new button ("Save", etc.)?
Blocks: 912912

Updated

4 years ago
Priority: -- → P1
Paul, what do you think about the questions in comment 0?
Flags: needinfo?(paul)

Comment 2

4 years ago
(In reply to J. Ryan Stinnett [:jryans] from comment #0)
> The initial version of the manifest editor integration from 922193 relies on
> the user to click "Update" to do the following:
> 
> * Re-validate the manifest
> * Save the manifest
> 
> Should re-validation happen immediately after you make a change in the
> editor?  (Probably.)

I think so.

> Should the manifest be save immediately, or will that confuse / surprise
> users?  If it requires pressing a button, should be part of the "Update"
> button, or some new button ("Save", etc.)?

Automatic saving would be nice. But we can't "undo" yet in the manifest editor. So you can easily lose stuff if you mess up with the manifest editor.

For the moment, I think we should save only when the user click on "update", and I believe we should add a "save" button too.

But adding a new button would make me sad.

Do you think you can wait until we figure out what we want to do with bug 919502? I'll be working on that this week.
Flags: needinfo?(paul)

Updated

4 years ago
Whiteboard: [manifest editor]

Comment 3

3 years ago
This code will be removed soon: bug 1007061.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.