Opened 8 years ago
Last modified 4 years ago
#17191 assigned defect
wrong constraints for parentConstrainedMoveable in a parent with position: absolute;
| Reported by: | ben hockey | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.15 |
| Component: | DnD | Version: | 1.9.0 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
a parentConstrainedMoveable that is in a parent that is absolutely positioned has it's constraints offset by the parent's position - see http://jsbin.com/ajimef/1/edit for an example.
i was expecting that the constraints would not have been affected by the parent's position.
my use case for this was a widget in the center region of a BorderContainer? that has a moveable node constrained to the domNode of the widget. the BC will use absolute positioning to position the domNode which results in the situation you see in the link above.
Change History (3)
comment:1 Changed 8 years ago by
| Owner: | set to Eugene Lazutkin |
|---|---|
| Status: | new → assigned |
comment:2 Changed 5 years ago by
| Milestone: | tbd → 1.12 |
|---|---|
| Owner: | Eugene Lazutkin deleted |
comment:3 Changed 4 years ago by
| Milestone: | 1.13 → 1.15 |
|---|
Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.
Note: See
TracTickets for help on using
tickets.
for some reason the owner wasn't assigned even though i selected the DnD component