To reproduce:

- Create an iframe entity browser that has auto_open option enabled
- Configure it to be used on a field and enable "Replace" option on the field widget configuration.
- Create an entity and make sure the field that we created is populated.
- Edit the entity and hit "Replace"
- Expected behaviour: One entity browser opens
- Actual behaviour: Two entity browsers open

CommentFileSizeAuthor
#2 2997731_2.patch1.04 KBslashrsm

Comments

slashrsm created an issue. See original summary.

slashrsm’s picture

slashrsm commented
Status: Active » Needs review
StatusFileSize
new 2997731_2.patch1.04 KB

Fix attached.

  • slashrsm committed 48d9fda on 8.x-1.x 
    Issue #2997731 by slashrsm: "Replace" button on entity browsers with...

  • slashrsm committed da3eb65 on 8.x-2.x 
    Issue #2997731 by slashrsm: "Replace" button on entity browsers with...
slashrsm’s picture

slashrsm commented
Status: Needs review » Fixed

Committed. Thanks!

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Hi!

> Committed. Thanks!

Talking to yourself? Should I be worried? ;)

Unfortunately, this caused a regression for us. See #2998317: Improve replace selector to make sure it matches the element with a data-uuid attribute.

I guess you tested this with an iframe display that doesn't have the path field?

Status: Fixed » Closed (fixed)

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