Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block list using inline editing updates the wrong field if more than 1 block is expanded #17312

Open
dmiller21283 opened this issue Oct 18, 2024 · 1 comment

Comments

@dmiller21283
Copy link

dmiller21283 commented Oct 18, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.3.0

Bug summary

When using a block list in inline editing mode that contains a url picker, if more than 1 block is expanded, the picker adds the new url to the first block open instead of the block where the "Add" button was clicked.

Specifics

No response

Steps to reproduce

video.mp4
  1. Create a document type as element type
  2. Add a url picker field.
  3. Create another document type and add a block list property editor
  4. Select the document type created in the first step as an available block
  5. Set the block list property editor to "Inline editing mode"
  6. Go to content and create a document with the block list
  7. Add an Item to the block list
  8. Select a url with the picker
  9. Add a second item to the block list
  10. With the first block still expanded, select a url with the picker from the second block

Expected result / actual result

Expected result:
The url should be added to the block where the Add button was clicked.

Actual result:
The url is added to the first open block instead of the block where the Add button was clicked.


This item has been added to our backlog AB#47399

Copy link

Hi there @dmiller21283!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants