Resizable criticals bugs

21 views
Skip to first unread message

Eduardo Lundgren

unread,
Jan 27, 2009, 1:46:34 AM1/27/09
to jquery...@googlegroups.com
I just fixed all criticals tickets for Resizable with one exception http://ui.jquery.com/bugs/ticket/3842 (In Opera, if you resize the top resizable first, the bottom resizable jumps down)

This jump is a very small jump (~3px) it happens because when we set position:absolute with top|left:auto on opera the element re-position itself to respect the auto. It's a very weird bug.

If someone have ideas how to work around this bug I really appreciate.

--
Eduardo Lundgren
Software Engineer
Liferay, Inc.
Enterprise. Open Source. For Life.

Richard D. Worth

unread,
Jan 27, 2009, 5:25:55 AM1/27/09
to jquery...@googlegroups.com
Looking good. Thanks Eduardo. I just entered a couple more:

resizable: se handle not visible in IE6
http://ui.jquery.com/bugs/ticket/3953

resizable: containment option, container size changes during resize in IE6
http://ui.jquery.com/bugs/ticket/3954

That first one is a regression in trunk since rc5. On the second one, as I played with it, I think I found another issue regarding containment. It seems to me containment should be bound by the container's padding (not allowed to go all the way to the border of the element). This is one reason it's so critical that specifications are written

Resizable: Specifications needed
http://ui.jquery.com/bugs/ticket/3748

Thanks.

- Richard

Paul Bakaus

unread,
Jan 27, 2009, 8:20:06 AM1/27/09
to jquery...@googlegroups.com
On Tue, Jan 27, 2009 at 11:25 AM, Richard D. Worth <rdw...@gmail.com> wrote:
Looking good. Thanks Eduardo. I just entered a couple more:

resizable: se handle not visible in IE6
http://ui.jquery.com/bugs/ticket/3953

resizable: containment option, container size changes during resize in IE6
http://ui.jquery.com/bugs/ticket/3954

That first one is a regression in trunk since rc5. On the second one, as I played with it, I think I found another issue regarding containment. It seems to me containment should be bound by the container's padding (not allowed to go all the way to the border of the element). This is one reason it's so critical that specifications are written

I think the padding should be included actually. It's part of the inner element, so it should extend to the padding. This is how draggable/sortable work as well.
 


Resizable: Specifications needed
http://ui.jquery.com/bugs/ticket/3748

Thanks.

- Richard


On Tue, Jan 27, 2009 at 1:46 AM, Eduardo Lundgren <eduardo...@gmail.com> wrote:
I just fixed all criticals tickets for Resizable with one exception http://ui.jquery.com/bugs/ticket/3842 (In Opera, if you resize the top resizable first, the bottom resizable jumps down)

This jump is a very small jump (~3px) it happens because when we set position:absolute with top|left:auto on opera the element re-position itself to respect the auto. It's a very weird bug.

If someone have ideas how to work around this bug I really appreciate.

--
Eduardo Lundgren
Software Engineer
Liferay, Inc.
Enterprise. Open Source. For Life.








--
Paul Bakaus
UI Architect
--
http://paulbakaus.com
http://www.linkedin.com/in/paulbakaus

Richard D. Worth

unread,
Jan 27, 2009, 8:25:38 AM1/27/09
to jquery...@googlegroups.com
On Tue, Jan 27, 2009 at 8:20 AM, Paul Bakaus <paul....@googlemail.com> wrote:


On Tue, Jan 27, 2009 at 11:25 AM, Richard D. Worth <rdw...@gmail.com> wrote:
Looking good. Thanks Eduardo. I just entered a couple more:

resizable: se handle not visible in IE6
http://ui.jquery.com/bugs/ticket/3953

resizable: containment option, container size changes during resize in IE6
http://ui.jquery.com/bugs/ticket/3954

That first one is a regression in trunk since rc5. On the second one, as I played with it, I think I found another issue regarding containment. It seems to me containment should be bound by the container's padding (not allowed to go all the way to the border of the element). This is one reason it's so critical that specifications are written

I think the padding should be included actually. It's part of the inner element, so it should extend to the padding. This is how draggable/sortable work as well.

The upper-left of the element does not extend into the padding. If you wanted it to, you'd have to give it a negative margin. While the padding is part of the element, it's not part of the available space of the element as a container. A child with height: 100% and width: 100% will not go beyond the padding, so why should this element that you're manually resizing to have effectively 100% available width and height?

If draggable and sortable work in the same way, I'd consider that a bug for the same reason.

- Richard

Scott González

unread,
Jan 27, 2009, 8:30:07 AM1/27/09
to jquery...@googlegroups.com
On Tue, Jan 27, 2009 at 8:25 AM, Richard D. Worth <rdw...@gmail.com> wrote:
The upper-left of the element does not extend into the padding. If you wanted it to, you'd have to give it a negative margin. While the padding is part of the element, it's not part of the available space of the element as a container. A child with height: 100% and width: 100% will not go beyond the padding, so why should this element that you're manually resizing to have effectively 100% available width and height?

If draggable and sortable work in the same way, I'd consider that a bug for the same reason.

+1

Paul Bakaus

unread,
Jan 27, 2009, 8:31:03 AM1/27/09
to jquery...@googlegroups.com
Convinced, could you please create a ticket for all components?

Richard D. Worth

unread,
Jan 27, 2009, 8:43:28 AM1/27/09
to jquery...@googlegroups.com
On Tue, Jan 27, 2009 at 8:31 AM, Paul Bakaus <paul....@googlemail.com> wrote:
Convinced, could you please create a ticket for all components?

droppable: padding space should not be used in certain calculations
http://ui.jquery.com/bugs/ticket/3956

draggable: padding space should not be used in certain calculations
http://ui.jquery.com/bugs/ticket/3957

sortable: padding space should not be used in certain calculations
http://ui.jquery.com/bugs/ticket/3958

They're quite generic. Whoever works on them may want to add details to the ticket as to how it applies to each one. Thanks.

- Richard

Reply all
Reply to author
Forward
0 new messages