387249 - Javascript window.close not working within TYPO3 Dataset Chose window

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Andreas Balzer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a6) Gecko/20070629 GranParadiso/3.0a6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a6) Gecko/20070629 GranParadiso/3.0a6

If you click on an entry within the Dataset Chose Window of a TYPO3 CMS (typo3.org) 4.1.1 installation, an entry gets sent back to the parent window and the Dataset Chose window is closed through JavaScript. In the actual Gran Paradiso Alpha 6 the window does not close.

Reproducible: Always

Steps to Reproduce:
Currently I can't specify and instruction. If you have a TYPO3 system installed:
1) Go to page module
2) create a new content element "Text with Image"
3) try to select an image by clicking on the title of the image
Actual Results:  
The window does not close

Expected Results:  
It should close on selection

Comment 1

[Andreas Balzer]

Forgot: Other browsers such as Fx 2.0.0.4 have no problem.

Comment 2

[Chris Lawson (gone)]

Call me paranoid, but I smell a browser-sniffing problem. If you put the word "Firefox" somewhere in your user-agent string and try again, do you still have the problem?

Comment 3

[bugzillamozilla05]

I'd just like to confirm/add to this bug report:
My university runs a typo3 v4.0.4 (yes, I know, old, but there's nothing I can do about it).
FF 2.x works fine.
FF 3 beta 2 has the problem described above. A simple way of reproducing it is to:
Launch Rich Text Editor. Mark some text. Click "Add link" button. A new window opens, in which I can type the link. On "Set link", the window is supposed to close and set the link in the "parent window". The window does not close and the link is not set in the parent.

Comment 4

[Chris Lawson (gone)]

David: when you go here

http://gemal.dk/browserspy/basic.html

do you see the word "Firefox" in the UserAgent line of the table?

If no, this is probably bad sniffing.

If yes, this might still be bad sniffing, just not of the extremely simplistic kind. If that's the case, try copying your Firefox 2 user-agent string into Firefox 3's general.useragent.override pref and see if that fixes the problem.

cl

Comment 5

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.10 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 6

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 7

[bugzillamozilla05]

I just tested this on the 4.0 beta 7 and the bug seems to be resolved.