Closed Bug 1135910 Opened 5 years ago Closed 5 years ago

[Customizer] Persist "Move", "Remove", and "Append Child" operations on DOM nodes

Categories

(Firefox OS Graveyard :: Gaia, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: drs, Assigned: justindarc)

References

Details

(Whiteboard: [spark])

The "Edit" view is very clear in its results, as you must hit "Save" for changes to be persisted. However, the "Move" and "Remove" operations are currently unclear in whether or not they're persisted. Perhaps we should add a confirmation, or maybe it's ok to simply persist them as soon as an action is taken, e.g. an element deleted.
Jacqueline, Justin, any thoughts here?
Flags: needinfo?(jsavory)
Flags: needinfo?(jdarcangelo)
Justin, I'm assigning this to you since you know the add-on generation code well.
Assignee: nobody → jdarcangelo
No longer blocks: 1133835
See Also: → 1133970
Priority: -- → P1
Summary: [Customizer] Persist "Move" and "Remove" operations on DOM nodes → [Customizer] Persist "Move", "Remove", and "Append Child" operations on DOM nodes
Resolved: https://github.com/fxos/customizer/commit/648339ffd02c9f15f17521c75e79d3e25144a0d1
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(jdarcangelo)
Resolution: --- → FIXED
Removing flag here as bug has been fixed and answered in the spec.
Flags: needinfo?(jsavory)
Whiteboard: [lightsaber] → [ignite]
Whiteboard: [ignite] → [spark]
You need to log in before you can comment on or make changes to this bug.