Opened 10 years ago

Closed 10 years ago

#10399 closed defect (wontfix)

fullscreen Editor as child of BorderContainer resize problem

Reported by: roaming Owned by: Jared Jurkiewicz
Priority: high Milestone: tbd
Component: Editor Version: 1.4.0b
Keywords: Cc: Adam Peller, Jared Jurkiewicz
Blocked By: Blocking:

Description

When you go from fullscreen mode back to non-fullscreen mode on an Editor that is a direct child of a BorderContainer?, the Editor doesn't "resize back" properly - it hides the top pane of the BorderContainer? (in FF 3.5.5, Safari 4.0.4) Calling resize() on the BorderContainer? fixes this.

Attachments (1)

test_resize2.html (22.1 KB) - added by roaming 10 years ago.

Download all attachments as: .zip

Change History (4)

Changed 10 years ago by roaming

Attachment: test_resize2.html added

comment:1 Changed 10 years ago by Adam Peller

Cc: Adam Peller Jared Jurkiewicz added
Component: GeneralEditor
Owner: anonymous deleted

comment:2 Changed 10 years ago by bill

Owner: set to Jared Jurkiewicz

See also #10398.

comment:3 Changed 10 years ago by Jared Jurkiewicz

Resolution: wontfix
Status: newclosed

The problem here is with how BorderContainer? works. It directly modifies the children dom nodes. This messes up Editor/FS in this case. Ideally we could reparent the editor to body when going in FS, and put it back when coming out ... but that doesn't work on Firefox.

The reason it doesn't work is that FireFox? reloads the iframe whenever the dom node is moved. So moving the editor reloads the iframe, which breaks a ton of stuff. So ... we can't reparent, which puts it at the mercy of the BorderContainer?.

To avoid this, wrap the editor with a contentpane. No other solution is known at this time. Closing this issue as wontfix for now, as it's a browser limitation with movement of iframes.

The other issue #10398 was worked around through some CSS class manipulation and should make FullScreen? generally viable in most layout containers. More work will continue to be done on this plugin over time.

Note: See TracTickets for help on using tickets.