May be related to #2919678: Collapse all button incorrectly shown

Problem/Motivation

Given you use paragraphs experimental widget and configure it to use edit mode "Closed (same as in #2919678: Collapse all button incorrectly shown). Then create a new node with at least to paragraphs and save it. Now edit the node again. You should see all paragraphs closed. if you click on the first paragraphs "Edit" button you see the "Collapse all" button:

Close all paragraphs again and click on the second paragraphs Edit button. Now you see the "Edit all" button:

Proposed resolution

Display the "Collapse all" button both cases.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

daniel.bosen created an issue. See original summary.

miro_dietiker’s picture

This is by design.

As written in the other issue, the collapse all button responds to the state of the first children.

We decided that we always want to show one of the two actions at that place for UI consistency. It was not that important which one in some situations. And the implementation should not cost performance.

How else would you expect it? And how does that other implementation provide really big additional UX value?

miro_dietiker’s picture

Status: Active » Postponed (maintainer needs more info)

The other issue is a bug. But what you describe her is the intentional behavior of the Edit All / Close All buttons.

How could it be different (and still easy to implement) and of better value for end-users?