Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#3882 closed bug (fixed)

Resizable - Left Margin Calculated Incorrectly (Using Containment)

Reported by: braddunbar Owned by: scottgonzalez
Priority: critical Milestone: 1.7
Component: ui.resizable Version: 1.6rc5
Keywords: Containment Cc:
Blocked by: Blocking:


When using containment, the right side of a resizable does not stop at the edge of the containment. It stops at the left offset of the containment element.

A revised version of the basic resizable demo is included to demonstrate this. The only changes are to the containing div.demo, and the containment option.

I believe this is due to the calculation of woset in the containment plugin.

Change History (8)

comment:1 Changed 8 years ago by scottgonzalez

  • Milestone changed from TBD to 1.6
  • Priority changed from minor to critical

comment:2 Changed 8 years ago by eduardo

  • Resolution set to fixed
  • Status changed from new to closed

Fixed when #3733 was fixed

comment:3 Changed 8 years ago by braddunbar

If the ".demo" element has "position:relative;" then the incorrect behavior is still present.

I am continuing to look into this.

comment:4 Changed 8 years ago by rdworth

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:5 Changed 8 years ago by braddunbar

When the container element is positioned relatively and is also the parent of the resizable element, woset should not include the container offset.

I added the following lines starting at line number 706 to fix this issue:

var isParent = self.containerElement.get(0) == self.element.parent().get(0),
    isParentRelative = self.containerElement.css('position') == 'relative';

if(isParent && isParentRelative) woset -= self.parentData.left;

The isParent and isParentRelative checks should be placed in the start function to prevent calling them over and over, but I thought including them here would make the concept easier to grok.

Note that this may also be the case for absolutely positioned parent elements. I will look into this.

comment:6 Changed 8 years ago by braddunbar

This does indeed seem to affect absolutely positioned parent containers, changing the patch code to:

var isParent = self.containerElement.get(0) == self.element.parent().get(0),
    isOffsetRelative = /relative|absolute/.test(self.containerElement.css('position'));

if(isParent && isOffsetRelative) woset -= self.parentData.left;

comment:7 Changed 8 years ago by rdworth

  • Owner set to scott.gonzalez
  • Status changed from reopened to assigned

comment:8 Changed 8 years ago by scottgonzalez

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed in r2107. Thanks for the patch.

Note: See TracTickets for help on using tickets.