FCKeditor 2.6 RC released

In Opera, all toolbar items are inverted. What should be grayed out is not (and the other way around).

Opera 9.50 beta Build 9864 Windows XP

Not working option 'Load' in image popup, also whith 'Flash'
We run here and in our server

Hi, when some dialog is being showing, if I is use the TAB key I can use the objects of back of the dialog...

In the dialog LINK, the UPLOAD function doesn't work. Same problem on my server and in the demo at this site.
And in the dialogs FLASH and IMAGE the UPLOAD doesn't work either.

I use method RegisterDoubleClickHandler() to listen the double click event in the editing area and custom my handle functions,I find two bugs with this method:
1.when I use RegisterDoubleClickHandler() to listen event on the <select> element in firefox,error occurs always,the js script stops and error increases after mouse clicks!
Error info in firefox:
[Exception... "'Ö^' Text.nodeType öCP ³' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]

My codes likes following:
function FCKeditor_OnComplete(editorInstance) {
oApi = FCKeditorAPI.GetInstance('editor1');
oApi.Focus();
...
oApi.RegisterDoubleClickHandler(handle1, 'input');
oApi.RegisterDoubleClickHandler(handle1, 'select');
...
}
2.the RegisterDoubleClickHandler() method is invalid with the <input type="hidden" /> element,I don't know why?

It seems that the new "inline CSS cache" feature is breaking the old way of simply loading the CSS file.

My setting:

FCKConfig.EditorAreaCSS = '/mysite/stylesheets/gateway.css';

but no style is applied to the editor area.

Same code is working correctly in v 2.5.1.

Wanted to post my findings to save others time that may be experiencing the EditorAreaCSS not working in 2.6 problem. It had nothing to do with FullPage settings in my case. I was appending a cache buster random number to the css url which caused cssFileOrArrayOrDef to think that it was a style and not a url.

Ex:
http://someplace.com/style.css?123483745 would be returned in style tags.
http://someplace.com/style.css is valid and would be returned in a link tag.

Maybe it isnt necessary anymore, but I remember at one point it was not refreshing the style sheets automatically. IE issue I am sure, but the random number originally fixed it. The regular expression that checks to see if it is a valid url, doesnt take query strings into consideration, so to keep cache busting, just append a valid extension to your cache busted url.

Ex:
http://someplace.com/style.css?123483745.css