Project

General

Profile

Actions

Bug #18096

closed

New backend problems in FireFox, Safari, OmniWeb and Camino

Added by Dmitry Dulepov almost 17 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
-
Target version:
-
Start date:
2008-02-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

New backend has a problem on all above mentioned browsers:
- content iframe is far below the menu (see be-in-ff-on-macos.gif)

Safari and OmniWeb (=anything-based on Apple WebKit) does not resize backend correctly. It appears that TYPO3 resize manager is called when BE is not fully loaded and it receives wrong height of toolbar (something close to 171 instead of 25). See webkit-resize-bug.jpg)

The attached patch fixes both problems.

(issue imported from #M7352)


Files

be-in-ff-on-mac.jpg (75.2 KB) be-in-ff-on-mac.jpg Administrator Admin, 2008-02-02 11:05
webkit-resize-bug.jpg (68.5 KB) webkit-resize-bug.jpg Administrator Admin, 2008-02-02 11:06
be-gui-fixes-7352.diff (933 Bytes) be-gui-fixes-7352.diff Administrator Admin, 2008-02-02 11:09
Actions #1

Updated by Ingo Renner almost 17 years ago

fixed in trunk

Actions #2

Updated by Stefano Cecere almost 17 years ago

what i see (in Safari at least) is still a problem with the top roght menus..
the popups div are broken (the break the whole page layout9 untile you do a manual resize of Safari's window. then they work right

Actions #3

Updated by Ingo Renner almost 17 years ago

what version of Safari do you use?

Actions #4

Updated by Ingo Renner almost 17 years ago

ok, they should be fixed now, too. Same issue as with the first resizing: switch from the dom:loaded event to window.load - at this point all external resources like css files (for positioning and layout) are loaded, whereas this is not the case with dom:loaded (the DOM is ready but no styles are attached to the elements)

I recommend this book: http://www.pragprog.com/titles/cppsu , it's worth every cent and very current with explaining prototype 1.6 (now in 4.2).

See page 101 for the explanation of event handling and the issues involved with this bug.

Actions

Also available in: Atom PDF