925957 - Improve manifest editor save / validate UX

Status: RESOLVED WONTFIX

(DevTools Graveyard :: WebIDE, defect, P1)

Description

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

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.)?

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Paul, what do you think about the questions in comment 0?

Comment 2

[Paul Rouget [:paul]]

(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.

Comment 3

[Paul Rouget [:paul]]

This code will be removed soon: bug 1007061.