Firefox 3

[RiCoTeRoX]

Problems with firefox 3

Code: Select all

FCKeditorAPI is undefined

Code: Select all

var FCKeditorAPI;function InitializeAPI(...oreunload',FCKeditorAPI_ConfirmCleanup);

in fckeditorcode_gecko.js

team FCKeditor.... solution?

[DarthSonic]

Same Problem here! Since upgrading to Firefox 3.0 FCKEditor (using 2.6.1) is not working anymore.

[RiCoTeRoX]

fckeditor team.

you are working in this problem right ?

all the comunity of Mozilla is wainting ......


Thx a lot !

[martinkou]

This is a known problem with Firefox 3 when FCKeditor is opened from the local filesystem: https://dev.fckeditor.net/ticket/1645.

The issue is caused by a new security check implemented in Firefox 3 for file:// URIs. It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.

See the following Mozilla documentation for more information: http://kb.mozillazine.org/Security.file ... gin_policy

[A.M.]

It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.

A typo. Should be security.fileuri.strict_origin_policy

[DarthSonic]

It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.

A typo. Should be security.fileuri.strict_origin_policy

The developers of Firefox got a reason to secure this, so I would not prefer to disable it to get a workaround! I am waiting for a fix.

[alfonsoml]

It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.

A typo. Should be security.fileuri.strict_origin_policy

The developers of Firefox got a reason to secure this, so I would not prefer to disable it to get a workaround! I am waiting for a fix.

Then install a web server on you machine and use localhost.

At the current state of the restriction made in Firefox, it's impossible to make this work without rewriting everything to change all the locations of the files (and even then I'm not sure if it would work)

[martinkou]

The developers of Firefox got a reason to secure this, so I would not prefer to disable it to get a workaround! I am waiting for a fix.

The strict origin policy setting in Firefox 3 only applies to file:// URLs, what it does is this:

Let's say you've an HTML in the local filesystem opened in Firefox 3, and the HTML opens another file also from the local filesystem in an iframe. Now, the two documents want to communicate with each other via JavaScript. Strict origin policy means the communication will only be allowed in the following cases:

1. If the child iframe's file path is under the parent window's file path; or
2. If the parent window's file path is under the child iframe's file path

So, if you opened something like ../some_dir/some_html.html in the child iframe, Firefox 3 will determine that they are not from the "same origin" even though they belong to the same code package (e.g. FCKeditor, or Dojo, or YUI, etc.), and thus FF3 will give out permission errors.

It is clearly written in the MozillaZine document I gave you that "If you do development with local files and need to be able to retrieve other local files, you may need to set this preference to false". So disabling this security check for local web development is pretty much a standard practice in Firefox 3. Also, since the security check applies to file:// URL only, there shouldn't be any way it can be exploited by malicious remote websites, so the security risks posed by disabling the strict origin policy setting should be minimal.

[martinkou]

At the current state of the restriction made in Firefox, it's impossible to make this work without rewriting everything to change all the locations of the files (and even then I'm not sure if it would work)

It would be nice if Firefox 3 allows some way of declaring that certain directories belong to the same code package and thus are of the "same origin". Unfortunately there's no way to do this so far. I guess this new security check in Firefox 3 is causing a lot of troubles in locally filed web page as beyond just FCKeditor right now (e.g. Wikipedia on DVDs?).

[alfonsoml]

I just hope that now that Firefox 3 has been released, enough people face the problem and report it in the proper place (that's it: to the Firefox developers) that they finally add any such measure to allow this kind of pages without problems.

Waiting for a fix in FCKeditor is just wasting the time.