You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no reason to have cards aligned to the left, as the upcoming card can go before of after with the same probability.
So I would suggest to have cards center aligned like this:
I did the needed CSS changes in Flaburgan@bfd6dd6 however I have a weird misalignment when drag and dropping the card.
2024-03-10.14-07-24.mp4
First of all, the gap is initially created on the left of the card which is under the picked card. That is not much an issue for the users, but it shows that the computing point is not at the right place.
And then, you can see this again when the card is actually dropped, it's first displayed on top of the other one and then properly placed.
Could anyone help me investigate this? I guess it isn't a big deal, but I don't know if that's because of something in this repo or in the beautiful-dnd lib config somewhere. Thank you!
The text was updated successfully, but these errors were encountered:
There is no reason to have cards aligned to the left, as the upcoming card can go before of after with the same probability.
So I would suggest to have cards center aligned like this:
I did the needed CSS changes in Flaburgan@bfd6dd6 however I have a weird misalignment when drag and dropping the card.
2024-03-10.14-07-24.mp4
First of all, the gap is initially created on the left of the card which is under the picked card. That is not much an issue for the users, but it shows that the computing point is not at the right place.
And then, you can see this again when the card is actually dropped, it's first displayed on top of the other one and then properly placed.
Could anyone help me investigate this? I guess it isn't a big deal, but I don't know if that's because of something in this repo or in the beautiful-dnd lib config somewhere. Thank you!
The text was updated successfully, but these errors were encountered: