Opened 5 years ago

Last modified 5 years ago

#11124 open bug

Resizable: Does not adjust positioning for RTL markup

Reported by: OlegK Owned by:
Priority: minor Milestone: none
Component: ui.resizable Version: 1.11.3
Keywords: Cc:
Blocked by: Blocking:

Description

The demo http://jsfiddle.net/OlegKi/cadhyvuL/1/ uses the simplest code

$("#test").resizable({handles: "e,w"});

where the <div id="test"></div> is inside of outer div (or body) having dir="rtl" attribute.

If one drag the RIGHT edge of the block and start to resize it then the position of the LEFT edge will be changed, which is wrong.

If one drag the LEFT edge of the block and start to resize it then the position of the both the RIGHT and the LEFT edges of the block will be changed. The position of the block during resizing will be absolutely wrong. One can easy move the block OUT OFF the visible part of the page.

The bug exist in different version of jQuery UI.

Best regards Oleg oleg.kiriljuk@… http://stackoverflow.com/users/315935/oleg https://github.com/OlegKi

Change History (3)

comment:1 Changed 5 years ago by Scott González

Status: newopen
Summary: risizable works wrong inside of RTL blockResizable: Does not adjust positioning for RTL markup

comment:2 Changed 5 years ago by OlegK

Hello!

Please could you confirm the bug and to inform about some plans to fix it?

The problem is not pure RTL problem. The demo http://jsfiddle.net/OlegKi/cadhyvuL/3/ uses just float:right in the outer div and one have the same problem as before:

  • the position of resized block will be calculation in the wrong way
  • the block can be moved in not visible part of the page (negative margin-left)
  • the LEFT edge of the block will be moved on resizing of the RIGHT edge. Both right and left edges will be moved during resizing of the left edge. As the result the block can be moved out of invisible part of the HTML page.

Best regards Oleg

comment:3 in reply to:  2 Changed 5 years ago by Scott González

Replying to OlegK:

Hello!

Please could you confirm the bug and to inform about some plans to fix it?

It's already been confirmed, that's why it's marked open and not new. There are no plans to fix this prior to the interactions rewrite.

Note: See TracTickets for help on using tickets.