Download & Extend

CKEditor does not appear on windows with non-empty window.opener

Project:CKEditor - WYSIWYG HTML editor
Version:6.x-1.1
Component:User interface
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

CKEditor does not appear in Firefox 3.6. I have followed all the troubleshooting steps, but found that if run the same site in IE8 side by side it works perfectly. I even tried clearing cache with no luck. What did work was logging out of Windows and logging back in. I have had this same problem on a W7 and Vista machine.

Comments

#1

Status:active» postponed (maintainer needs more info)

Can you provide me information about FF version and installed extensions, toolbars etc... ?

#2

IE 8 always works.

Firefox 3.6 fails, no toolbars. Extentions - Logmein, New tab Home Page, Mcafee Site Adviser.

My further testing shows that by disabling Mcafee Site Adviser it will work for a while and then fail again, but what is more interesting is that CKEditor will fail again after some usage, then by turning Mcafee Site Adviser back on, CKEditor starts to work again.

I will continue testing the other Plugins and report back.

#3

@ElegantSolutions after disabling Mcafee, clear browser cache, restart the browser and check whether the problem still exists.

#4

I have similar problems with Firefox 3.6 on Windows 7 (also appeared on Linux with Firefox 3.5.8). Drupal module version is 6.x-1.0, CKeditor version is 3.2

I've done some investigations and here are steps to reproduce this bug:

  • Open page containing link to node with attribute target="_blank" and click it. Node will be opened in new tab.
  • Go to node edit page (click on "Edit" tab)
  • There will be no Ckeditor, only plain textarea. You can even edit URL and go to another node edit page, Ckeditor will not appear. But if you create new tab and go to the same node edit page, Ckeditor will appear! Very strange.

I'll try to build clear testing environment later to confirm that target="_blank" is the reason of this problem.

#5

I am having the same issue with my site.

Have you received any solution on this issue?

#6

Hi,

i've noticed same issue, only in ff:

Might be because of a (system) update but tille yesterday i did not have or notice the issue.

But as said by Dmitriy.trt in #4 it might be because of the target="_blank": I added the attribute yesterday after having multiple tabs with my adminpages openend, that might explain why i didn't notice it before.

using: Mozilla/5.0 (X11; U; Linux x86_64; nl; rv:1.9.1.8) Gecko/20100214 Ubuntu/9.10 (karmic) Firefox/3.5.8

Opening an extra tab with logged in page solves the issue.

#7

Title:CKEditor does not appear in Firefox» CKEditor does not appear on windows with non-empty window.opener
Version:6.x-1.0» 6.x-1.1
Status:postponed (maintainer needs more info)» needs review

So, I've determined reason of this problem. In function Drupal.ckeditorTeaserInfo you've assumed windows with non-empty window.opener are ckeditor popup window, but it is not always true. Attached patch adds global variable inside ckeditor.popup.html and in function we check for non-empty window.opener and this global variable to be sure we are inside ckeditor popup window. It's a dirty fix, maybe we need to wrap variable inside some namespace or give it other name.

Also, I think #703960: The CKEditor fails to load sporadically if the teaser of the node is empty is also a consequence of this wrong detection, and only checking for tv variable even solves our bug, but there are other hidden problems (such as wrong teaser detection...). I've removed tv check, but you can leave it, this is not important.

Also patch fixes scroll to top of page after click on link which opens ckeditor popup window.

Patch was made from ckeditor-6.x-1.1

AttachmentSize
ckeditor-6.x-1.1-fix-popup-detection.diff 2.36 KB

#8

Status:needs review» fixed

Dmitriy.trt thanks for patch, changes commited into cvs.

If you have any lack of clarity about issue, feel free to reopen it.

#9

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.