BorderLayoutData .setFloatable(false) doesn't work.

[Webrat]

Hello!

I'm using RC2.

I have a BorderLayout with 3 Regions:

1. North
2. Center
3. East

I wanted to have the East-Region collapsible and floatable. That did work. When I opened my webapp in my browser (IE, FF, Chrome) the region was collapsilbe and floatable.
Now I opened my application in iPads Safari for testing purposes: When touch the collapsed regions-bar it floats over my application BUT doesn't "unfloat" after touching another part of my application. --> So on iPad this app wouldn't be usable.

OK, now I wanted to have a workaround in setting floatable to false that the application wouldn't hang on iPads Safari. So I did:

eastData = new BorderLayoutData(200);
eastData.setSplit(false);
eastData.setCollapsible(true);
eastData.setFloatable(false);

Unfortunately ".setFloatable(false)" doesn't work for me. The Region floats still over the rest of my application when the regions-bar is clicked.
Doesn't "setFloatable() have to behave like I supposed?

Kind regards
"Webrat"

[Webrat]

Hi again!

Also there is a problem with .setCollapsibleMini(true) in combination with .setSplit(false).
.setCollapsibleMini(true) undoes .setSplit(false).

eastData.setSplit(false);
eastData.setCollapseMini(true);

I used .setSplit(false) to disable the possibility to resize the region with the mouse by using the splitbar between the regions.
The use of .setCollapsibleMini(true) shows the splitbar again and makes the region resizable by using the splitbar.

Regards
"Webrat"

[ovaris]

Any plans on fixing this issue? I have confirmed that in GXT 3.0.0 this issue is still valid, CollapsePanel method protected void onBarClick(Event event) {.... does not respect borderlayoutdata.setFloatable(false) at all. My workaround is to extend CollapsePanel (via deferred binding) and override onBarClick method.

Kind regards
Olli

[WesleyMoy]

Thanks for reconfirming the bug. I've examined the code and have noticed that the floatable property is never checked. I've now filed a ticket against the team and will update here with any changes.

[SiBurgess]

This also freezes Chrome and other browsers on Andriod 4.0.3 so seems a common problem on touch devices.

[SiBurgess]

And freezes the page on Android 2.x browsers.

[darrellmeyer]

SiBurgess - please submit the android issue as a separate bug report.