Custom Query (7259 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 7259)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#4823 invalid Droppable tolerance "intersect" did not work properly when in exact grid fjosefsson fjosefsson
Description

I have created a draggable object with its "grid" property having a width exactly as wide as the droppable object. The draggable object is precisely so wide that it fit over one or more droppable objects (example: three droppable objects are 50px 50px 50px 50px 50px, the draggable object is 100px, and the grid property has a width of 100).

It did not work -- ie it reported "false" -- when there were exactly two fields for it to span over. It worked with three fields. I did not try with more or less fields.

I changed

	case 'intersect':
			return (l < x1 + (draggable.helperProportions.width / 2) // Right Half
				&& x2 - (draggable.helperProportions.width / 2) < r // Left Half
				&& t < y1 + (draggable.helperProportions.height / 2) // Bottom Half
				&& y2 - (draggable.helperProportions.height / 2) < b ); // Top Half
			break;

into

	case 'intersect':
			return (l <= x1 + (draggable.helperProportions.width / 2) // Right Half
				&& x2 - (draggable.helperProportions.width / 2) < r // Left Half
				&& t < y1 + (draggable.helperProportions.height / 2) // Bottom Half
				&& y2 - (draggable.helperProportions.height / 2) < b ); // Top Half
			break;

and it worked.

Maybe you can confirm?

Perhaps the same change needs to be done with "&& t < y1 + (draggable.helperProportions.height / 2)" , if height of the draggable must match the height of one more droppables.

#4884 invalid IE: Jumping out of focus on click Jaggi Jaggi
Description

This bug only seems to happen in IE, when you click a element it jumps to focus to the top of the parent element this is however a bug as for example if you have a small work area (800x600) it'll move the clicked element out of view which is obviously not a desired behaviour. It should probably focus on the clicked element or do as firefox and just not move out of view of anything.

#4946 invalid Portlets prefer to go where they were taken from, rather than where they are being dragged. ramblinman ramblinman
Description

When a portlet is taken from a column, moved to another one and then to the original one, it doesn't go where it should. Here's a video: http://www.youtube.com/watch?v=GS9Dw-d09-U After a bit more movement it finally jumps into the right place, but still, it doesn't look good. It happens in every browser.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.