Project

General

Profile

Actions

Bug #18203

closed

Firefox 3.0 mixes up frames (TYPO3 4.2 and later)

Added by Christian Hernmarck almost 17 years ago. Updated over 14 years ago.

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

0%

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

Description

With firefox 3.0b3:

Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9b3) Gecko/2008020513 Firefox/3.0b3

I tried the backend from Typo3 4.2beta1, 4.1.5 and also 4.0.8
When Klicking on "Page" in the left frame, the URL changed to ".../typo3/alt_mod_frameset.php?..." and the left frame disappeared. I could not go back to the 3 column view without reloading the whole site .../typo3/

Seems to be in all links in "Web" and "Files" - where a center frame appears...

install linux :-)
Install ff 3.0b3 for linux
load typo3 backend > Typo3 4.0 and login
klick on Web\Page

I didn't check it on Windows...
it's on my todo list...
(issue imported from #M7516)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #18121: workspace selector doesn't work wellClosedIngo Renner2008-02-05

Actions
Has duplicate TYPO3 Core - Bug #18290: Firefox 3.0 mixes up frames (versions before TYPO3 4.2)ClosedIngo Renner2008-02-24

Actions
Actions #1

Updated by Ingo Renner almost 17 years ago

fixed in latest SVN revision 3155

Actions #2

Updated by Christian Hernmarck almost 17 years ago

Sorry for reopening - that was a fast patch... but this might be a solution for Typo3 4.2.x only.

There's also a problem with older Typo3 versions. I'm not sure if it's a firefox or Typo3 "bug" - I just want to say: there's a problem and when ff 3.0 get's released the problem should be fixed... (at least for the still supported Typo3 versions...)

I'll do some more checks (also with windows/ff).

Actions #3

Updated by Michael Wallner almost 17 years ago

Downloaded latest SVN revision 3159

Issue is still present and blocks the usage of the backend when using Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3

Actions #4

Updated by Andreas Balzer over 16 years ago

Happening with Firefox 3 beta 3 on Windows Vista 64 Bit aswell.. but Firefox seems to be the only browser affected.

Actions #5

Updated by Ingo Renner over 16 years ago

I still can't reproduce this with FF3b3 on OS X and Windows. please let me know if you have some special settings.

please also note that a fix for 4.1 will be only available after the 4.2 final release

Actions #6

Updated by Ingo Renner over 16 years ago

or even better: please write down what exactly you do to make this happen. also try the old backend by changing backend.php to alt_main.php and see whether it's happening there, too. also check the startup module settings in your user settings.

Actions #7

Updated by Ingo Renner over 16 years ago

if this is fixed for you with TYPO3 4.2, please also report so that we can finally mark this issue as resolve. You can the open a new issue for older versions of TYPO3 and set them as duplicate of this one so that we can keep track of them and also target them for 4.1.6 and 4.0.5.

Actions #8

Updated by Christian Hernmarck over 16 years ago

I rechecked again with an empty profile (ff 3.0b3 on Linux):
Typo3 4.2.0b1 (same version as above):
backend.php: -> left frame/column dissappears
alt_main.php: -> all 3 frames/columns stay there -> it works well!
Typo3 4.1.5 & 4.0.8:
alt_main.php: -> left frame/column dissappears

strange, the old way works on the new version...

Actions #9

Updated by Ingo Renner over 16 years ago

of course you must not use beta1, but a current checkout from SVN!

Actions #10

Updated by Christian Hernmarck over 16 years ago

ok, svn 3214 - still the same:
- backend.php > error
alt_main.php -> works

Actions #11

Updated by Ingo Renner over 16 years ago

what do you do to get this error? what's your startup module?

Actions #12

Updated by Christian Hernmarck over 16 years ago

I log into the BE of typo3, no special startup module - just the welcome & overview screen.
then I click on Web/Page (Web/Seite - "Seiten-Info und Inhalt") > then it happens: left "frame" dissappears, instead the middle "frame" gets left and the remaining is the right/content "frame" - but I cannot click in the tree"frame" (no reaction in the content)...

Actions #13

Updated by Ingo Renner over 16 years ago

console.debug($('content').contentDocument.getElementsByName('nav_frame')[0]);

Actions #14

Updated by Michael Stucki over 16 years ago

I just created a new bug entry #18290 for versions older than 4.2. Apparently this needs to be solved differently, although the reason for the problem seems to be the same of course...

Actions #15

Updated by Kasper Ligaard over 16 years ago

Same problem here, svn rev. 3304. Firefox 3 beta 3 on Ubuntu Hardy Heron.
- alt_main.php works.
- backend.php does not work. Every time I click on any submodule of the Web-module, the module menu disappears.

Actions #16

Updated by Christian Hernmarck over 16 years ago

I tested again -
with typo3_src-4.2.0beta3 the problem seems gone - at least on ff 3 beta 4.

Seems to be some sort of mix firefox beta and typo3 beta...

Maybe others can confirm?

Just saw in the other bug http://bugs.typo3.org/view.php?id=7646 that this is rather a firefox problem (or at least a change in ff)

Actions #17

Updated by Florian Seirer over 16 years ago

It also happens on TYPO3 v3.8...

Actions #18

Updated by Ingo Renner over 16 years ago

TYPO3 3.8 is not supported anymore, move along =)

You could of course help yourself by backporting the patch

Actions #19

Updated by Ingo Renner over 16 years ago

Anybody can confirm this issue with Firefox 3 beta 4? If there's no confirmation within a week from now on I'm going to close this issue.

Actions #20

Updated by Michael Wallner over 16 years ago

checked with latest trunk (3414) issue is still present with firefox 3 beta 4

if i use the beta3 package, the backend works as expected with firefox 3 beta 4

Actions #21

Updated by Andreas Balzer over 16 years ago

"if i use the beta3 package, the backend works as expected with firefox 3 beta 4 " +1

Actions #22

Updated by Steffen Kamper over 16 years ago

so this can be closed as it is resolved in beta3?

Actions #23

Updated by Andreas Balzer over 16 years ago

yes
Error non reproducible on T3 beta3, Fx2b4 on Win Vista 32 Bit T3 installer

Actions #24

Updated by Christian Hernmarck over 16 years ago

if I understand the post of Michael Wallner right, then the issue did reappear after beta3 - so we need to check this again.

Actions #25

Updated by Steffen Kamper over 16 years ago

no - trunk is not relevant as we work on 4_2-branch, trunk will be updated after 4.2 final release

Actions #26

Updated by Kasper Ligaard over 16 years ago

Problem still exists in 4_2-branch, revision 3443 in Firefox 3 beta 4 on Ubuntu Hardy Heron.

Firebug reports the following:

top.fsMod is undefined
alt_db_navframe.php?&currentSubScript=mod%2Fweb%2Fperm%2Findex.php()alt_db_navframe.p... (line 123)
[Break on this error] Tree.highlightActiveItem("",top.fsMod.navFrameHighlightedID["web"]);

Line 123: Tree.highlightActiveItem("",top.fsMod.navFrameHighlightedID["web"]);

Actions #27

Updated by Steffen Kamper over 16 years ago

tested with BETA4 - no problems.

Actions #28

Updated by Ekkehard G¼mbel over 16 years ago

I do have those problems, using BETA4.

Actions #29

Updated by Ingo Renner over 16 years ago

with a pure core installation? if you have any extensions installed - which are that?

Actions #30

Updated by Ekkehard G¼mbel over 16 years ago

I just reproduced with a fresh 4.1.6 src+dummy installation.
Firefox is running on Windows XP in my case.

Actions #31

Updated by Christian Hernmarck over 16 years ago

for typo3 versions before 4.2 there is another issue:
http://bugs.typo3.org/view.php?id=7646

here, we only discussing about Typo3 4.2 (beta) with the new firefox 3 (beta)

Actions #32

Updated by Ekkehard G¼mbel over 16 years ago

oops, sorry for the confusion :-\

Actions #33

Updated by Ingo Renner over 16 years ago

ekki, nevertheless, what extensions do you have installed in 4.2?

Actions #34

Updated by Ekkehard G¼mbel over 16 years ago

Sorry Ingo, also the first test was not with 4.2 but 4.1.6. Stupid me.

Actions #35

Updated by Kasper Ligaard over 16 years ago

I rechecked this issue with latest from 4-2 and it works. I am looking into what went wrong when I tested previously, but for Typo3 the problem seems solved. (and thus I retract comments 19849 and 20434 above).

Actions

Also available in: Atom PDF