When the CssFiles property is set to external stylesheets some of the tools become none responsive when used through FireFox browsers. By external I mean that these stylesheets are defined by absolute uris with a different domain. I am specifically noticing that the Hyperlink Manager dialog button is non responsive and the ApplyClass dropdown list are non-responsive.
I have used FireBug from FireFox 2 to find that an error is occuring when these tools are clicked:
Error Message: access to restricted uri denied" code: "1012
Location: ScriptResource.axd.... (line:8397)
Function: _getStyleSheetRules(...)
When I set the CssFiles property to a local domain stylesheet or do not set the property at all those features work fine in FF.
The error seems to be a security error specific to FireFox browsers. We have a need to reference cross domain stylesheets in the CssFiles property. I am hoping that there is some possible workaround for this.
I have used FireBug from FireFox 2 to find that an error is occuring when these tools are clicked:
Error Message: access to restricted uri denied" code: "1012
Location: ScriptResource.axd.... (line:8397)
Function: _getStyleSheetRules(...)
When I set the CssFiles property to a local domain stylesheet or do not set the property at all those features work fine in FF.
The error seems to be a security error specific to FireFox browsers. We have a need to reference cross domain stylesheets in the CssFiles property. I am hoping that there is some possible workaround for this.
1 Answer, 1 is accepted
0
Hi,
Unfortunately there is no way to accomplish this on the client side - client browser security prevents code originating from one domain to access resources from another domain.
Some of the editor tools and dialogs need to process the css files specified to the editor in order to provide their respective functionality (e.g. the ability for the user to pick up a css class).
Our suggestion in this case is to come up with some server scheme that requests the files from the remote server, and then serves them to the browser - so that everything on the editor's page originates from the same server. This seems to be the only way to achieve your scenario.
Regards,
Tervel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Unfortunately there is no way to accomplish this on the client side - client browser security prevents code originating from one domain to access resources from another domain.
Some of the editor tools and dialogs need to process the css files specified to the editor in order to provide their respective functionality (e.g. the ability for the user to pick up a css class).
Our suggestion in this case is to come up with some server scheme that requests the files from the remote server, and then serves them to the browser - so that everything on the editor's page originates from the same server. This seems to be the only way to achieve your scenario.
Regards,
Tervel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center