Scope: "Paragraphs EXPERIMENTAL" Widget

Scenario:
- Widget is configured with a default edit mode of "preview".
- An editor clicks the "Edit" button to open the paragraph sub form.
- An editor makes some edits.
- An editor clicks the "Collapse" button.

Current Results: The widget is displayed in the "closed" state with a paragraphs summary.
Expected Results: The widget is displayed in the "preview" state display the rendered preview with the updated values.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

recrit created an issue. See original summary.

recrit’s picture

Status: Active » Needs review
FileSize
696 bytes
miro_dietiker’s picture

Status: Needs review » Needs work

Yeah, it kinda makes sense. :-)

But even if a paragraph is expanded=open by default, a user might want to define that the widget should display the Preview instead of the closed summary, if he clicks on "Collapse". I'm still not happy though to add a new setting. I feel like we should change the states and only have a "closed" state and determine if it displays summary or preview. Then the default mode setting just determines if Edit or Closed.
We still can care about this proposal in a follow-up.

But this issue should at least start with adding test coverage to check for the closed=preview expectation.

miro_dietiker’s picture

This is related to the autocollapse. :-)

miro_dietiker’s picture

Status: Needs work » Postponed

Postponing on that. Let's discuss it afterwards.

miro_dietiker’s picture

Status: Postponed » Fixed

We have committed the autocollapse feature in Paragraphs EXPERIMENTAL widget.

Thus, you can enable that all paragraphs except the one in edit is collapsed.

At the same time, we refactored the closed mode: If a paragraph is collapsed, it always shows consistently a summary OR the preview based on configuration.

That makes this issue resolved. :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

recrit’s picture

@miro_dietiker Thank you! I've just upgraded to 1.2+ and it works great!