Make WordPress Core

Opened 20 months ago

#56082 new defect (bug)

Block editor does not unset changed/dirty flag for nested types

Reported by: starbuck's profile Starbuck Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Editor Keywords:
Focuses: Cc:

Description

Edit a template and change a template parts or Reusable blocks. Go to save and there is an expected prompt to save the component. Don't save. Ctrl-Z to undo the change. The main template being edited still shows the Save button enabled, and on Save the component is still showing as changed.

Uncheck to Not save the component. Edit another template. The Save button remains enabled because the component is still "floating around" with the unsaved flag set.

The only way to clear this seems to be to simply re-save any template that includes the component, for a net effect of no change ... but this will still be recorded as a change, where the site is logging activity, even if just with a new timestamp.

The problem: The user doesn't know if they have actually changed a component, and potentially affected a large number of existing published posts. The "are you sure" prompt is asking the user if they are sure they want to make such a change when there actually is no change being made.

Expected behavior: The UnDo feature, and exiting without saving, should unset the dirty flag on any block or nested block or template where the current version equals the original.

Change History (0)

Note: See TracTickets for help on using tickets.