What problem does this address?

The Quick Edit Drawer in the Pages DataView currently includes both:

• A close button in the Drawer header
• A dedicated Cancel action

This creates ambiguity around the outcome of closing the Drawer.

When a user selects the close button, it is unclear whether changes will:

• Be saved
• Be discarded
• Trigger confirmation
• Behave differently from Cancel

Having two affordances that appear to perform similar actions but imply different intent increases cognitive load and makes the interaction less predictable.

What is your proposed solution?

Remove the header close button and rely solely on the existing Cancel action.

The interaction model would become:

• Save → commit changes
• Cancel → discard changes and exit

Rather than:

• Close (?)
• Cancel
• Save

Additional context

This pattern already has precedent in the existing component library.

AlertDialog intentionally removes the close button because dismissal actions can be ambiguous and the user should make an explicit decision through the provided actions.

The Quick Edit Drawer has a similar characteristic: it represents an editing flow with meaningful completion actions, so relying on explicit Save and Cancel actions would provide a clearer interaction model.

Side note

Drawer lacks an option to remove the close button, so that's something we'll need to consider adding. It's not a blocker to this issue though, becasue I don't believe the quick edit panel uses Drawer yet.