I have an issue, especially with blocks with greater height, where it becomes very difficult to drop them onto other columns. I have figured out the sweet spot. You have to actually drag the block so that the vertical middle of the block is actually above the top of the target column. Once you do that, the column will expand in size to accommodate the new block but it took me a few hours to find out how to make that work.

As a test, I tried making the column very tall using Firebug. When the column is tall, it is very easy to drag and drop into it, even when blocks are tall.

I plan to do a little more digging around but it seems like there should be some combination of jQuery settings that would allow this to be more user friendly.

A dirty hack would be to add some height to each column when the drag starts. I'm hoping there's a better way.

Come to think of it, even when dragging small blocks to the bottom of other columns, there is no user feedback. You pretty much have to drop them on the top of the column.

It's possible that this is a theme issue whereby the spacing on my blocks and columns messes up the placeholder columns.

CommentFileSizeAuthor
#1 homebox_bug.png8.66 KBmlconnor

Comments

mlconnor’s picture

StatusFileSize
new8.66 KB

It appears that this is being cause by the placeholder columns not being tall enough to hold the widgets. See attached screen shot. Does anyone know if this happened in any of the stable releases?

mlconnor’s picture

All columns have been set to have a height of 40px when I look at them in Firebug. Something is setting those to 40px and this is causing the usability issue. Oddly enough, the column wrapper has a suitable height, only the .homebox-column .ui-sortable has the 40px height.

jrowny’s picture

I have the same issue :(

jrowny’s picture

Status: Active » Needs review

Fixed it!

On line 360 of homebox.js I changed

currentHeight = $(this).height();

to

currentHeight = $(this).parent('.homebox-column-wrapper').height();
Shadlington’s picture

Status: Needs review » Active

jrowny, you're still looking at 6.x-2.1, this issue is about the dev version - where the code you are referring to is quite different.
Also I think you're meant to submit a patch to set the status to 'needs review'.

jrowny’s picture

okay, I'll see if I can't drum up a patch and test out the dev version.

brianV’s picture

Status: Active » Fixed

This looks like it is fixed in current dev.

Status: Fixed » Closed (fixed)

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

dsnopek’s picture

@mlconnor: I just created a patch that should fix the problem shown in your screenshot:

http://drupal.org/node/1219412

Please let me know if it works for you!

Regards,
David.