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

When configuring a block grid data type, blocks cannot be dragged to an arbitrary location #17798

Open
stephen-sherman opened this issue Dec 12, 2024 · 1 comment
Labels
area/frontend category/front-end state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@stephen-sherman
Copy link

stephen-sherman commented Dec 12, 2024

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

15.1.0

Bug summary

When configuring a block grid data type, blocks can only be dragged to the end of a row of blocks, not to an arbitrary location between other blocks.

In the below examples, the green checks indicate where a block may be dragged to depending on the size and wrapping of the editor UI.
image
image

Specifics

No response

Steps to reproduce

  1. Install a new Umbraco 15.1.0 solution
  2. Configure a block grid data type with a handful of blocks
  3. Attempt to sort the list of blocks by dragging and dropping

Expected result / actual result

Expected result

  • Blocks can be ordered arbitrarily by dragging them to the desired location

Actual result

  • Blocks can only be dropped at the ends of rows of blocks

Workaround

  • It is still possible to get blocks in the correct order, it just requires a lot more effort than it should

This item has been added to our backlog AB#47064

Copy link

Hi there @stephen-sherman!

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 🤖 🙂

@nielslyngsoe nielslyngsoe added state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks area/frontend category/front-end labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend category/front-end state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

2 participants