Log in or register to post comments
Last post
Minor CKFinder popup issue with firefox
The issue when clicking image properties and browse server in CKEditor for first time, the CKFinder will popup and went behind the master/main page. Then you need to click and focus back the CKFinder windows from taskbar.

It only happen for first time clicking the browse server with new session/clear cache. Open firefox and go to http://ckeditor.com/demo. Then click the image properties and browse server. It will popup behind the main screen. After that, close the CKFinder screen and click browse server, it will popup correctly without going behind the main screen.
Re: Minor CKFinder popup issue with firefox
Unfortunately same here with FF 16.0.1 on WIN7 64bit (but not on WINXP SP3)... it is as if CKFinder loses focus the first time it is loaded (the focus returns to the CKEditor "browse server" button), then everything works until you close the browser and restart over again (in my case even if I don't clear cache/cookies, in "-safe-mode" and regardless of the position of the tab).

The only thing I noted is javascript console (each time I click the "browse server" button) reports:
Error: this.docShell is null
Source file: chrome://global/content/bindings/browser.xml
Row: 323

that point to:
<property name="webNavigation" readonly="true">
    <getter>
        <![CDATA[
            if (!this._webNavigation)
/* #323 */      this._webNavigation = this.isRemoteBrowser ? this._remoteWebNavigation : this.docShell.QueryInterface(Components.interfaces.nsIWebNavigation);
            return this._webNavigation;
        ]]>
    </getter>
</property>

but I don't think it has anything to do: the error happens every click (also in WINXP), the problem only with the first (never in WINXP).

I hope someone find the cause, so #9433 can fix the problem in the next release... thanks in advance! :)

[edit]
The above error in javascript console doesn't happen in "-safe-mode", so I'm pretty sure that it has nothing to do with the problem.
This bug still occurs in

This bug still occurs in Firefox 18.01!