Chrome and Safari (both Mac and PC) both fail to submit data when "FCKConfig.StartupShowBlocks = true ;" in the fckconfig.js file. The data form value reports to be "[empty string]". I am using the latest 2.6.3 version.
The problem disappears if you press the "Source" button prior to clicking on the FCKeditor's "Submit" button; that seems to refresh the actual fckeditor content to include what you have just typed in.
I tried Frederic's solution of adding a try/catch to fckshowblocks.js, but without any success. Maybe I placed it in the wrong area. Thoughts? Help!
Below is my addition of try/catch, which did not solve the problem...
if ( FCKBrowserInfo.IsIE ) { try { FCK.EditorDocument.selection.createRange().select() ; } catch ( e ) {} } else { try { var focus = FCK.EditorWindow.getSelection().focusNode ; if ( focus.nodeType != 1 ) focus = focus.parentNode ; FCKDomTools.ScrollIntoView( focus, false ) ; } catch ( e ) {} }
I noticed some strange behavior of FCKeditor (2.6.3) with Chrome.
If there are selection when I click B (bold) button, the selected text changes to bold in both browser (FF3 and Chrome). But if I write in the editor, and I click bold, and I continue writing, the text style changes to bold in FireFox 3 but it remains normal in Chrome. It is applies to all formatting functions (font type, color, text styles, etc.)
We are currently upgrading to 2.5.X to avoid the new 2.6.X, really-hard-to-customize style sheets that are replacing all popups. We want 2.5.X mostly because of Safari Support. Now that Chrome is out there, we need FCK to work for that too.
Wondering if there is a target date on the hotkey issue mentioned above? I have a few apps that rely heavily on FCKeditor, and want to move the users to Chrome, but can't until this usability issue is resolved. Not whining or bullying, as I know of course you will deliver this. If there is some sense of timing, it would help me determine how to proceed.
How about the problem when "StartupShowBlocks" is set to "true" and that causes an emptystring to be submitted? That's a big problem, as the entire content of the fckeditor is completely lost upon hitting the submit button. See my above post for more details. I've not heard anyone comment on a fix for this problem. Thanks, DKC.
CKEditor 3.0 in the works, I can guess (and prefer) that the new version hit the stands, instead of a 2.54 fork to fix small hotkey bugs in Chrome...
thewaywest wrote:FCKcrew:
Wondering if there is a target date on the hotkey issue mentioned above? I have a few apps that rely heavily on FCKeditor, and want to move the users to Chrome, but can't until this usability issue is resolved. Not whining or bullying, as I know of course you will deliver this. If there is some sense of timing, it would help me determine how to proceed.
Re: FCK in Google Chrome
earlier version didn't work
Re: FCK in Google Chrome
http://127.0.0.1/www.lib/fckeditor/edit ... wblocks.js
Re: FCK in Google Chrome and Safari too
The problem disappears if you press the "Source" button prior to clicking on the FCKeditor's "Submit" button; that seems to refresh the actual fckeditor content to include what you have just typed in.
I tried Frederic's solution of adding a try/catch to fckshowblocks.js, but without any success. Maybe I placed it in the wrong area. Thoughts? Help!
Below is my addition of try/catch, which did not solve the problem...
if ( FCKBrowserInfo.IsIE )
{
try
{
FCK.EditorDocument.selection.createRange().select() ;
}
catch ( e )
{}
}
else
{
try
{
var focus = FCK.EditorWindow.getSelection().focusNode ;
if ( focus.nodeType != 1 )
focus = focus.parentNode ;
FCKDomTools.ScrollIntoView( focus, false ) ;
}
catch ( e )
{}
}
FCK.Events.FireEvent( 'OnSelectionChange' ) ;
Thanks,
DKC
Re: FCK in Google Chrome
I noticed some strange behavior of FCKeditor (2.6.3) with Chrome.
If there are selection when I click B (bold) button, the selected text changes to bold in both browser (FF3 and Chrome).
But if I write in the editor, and I click bold, and I continue writing, the text style changes to bold in FireFox 3 but it remains normal in Chrome.
It is applies to all formatting functions (font type, color, text styles, etc.)
regards,
zsolt
FCK 2.5.X and Google Chrome (do not want 2.6.X)
We are currently upgrading to 2.5.X to avoid the new 2.6.X, really-hard-to-customize style sheets that are replacing all popups. We want 2.5.X mostly because of Safari Support. Now that Chrome is out there, we need FCK to work for that too.
Does chrome work with VERSION 2.5.X
Bump: FCK Hotkeys in Google Chrome - status?
Wondering if there is a target date on the hotkey issue mentioned above? I have a few apps that rely heavily on FCKeditor, and want to move the users to Chrome, but can't until this usability issue is resolved. Not whining or bullying, as I know of course you will deliver this. If there is some sense of timing, it would help me determine how to proceed.
Thanks in advance!
Re: FCK in Google Chrome
https://bugs.webkit.org/show_bug.cgi?id=15256
Re: FCK in Google Chrome
Re: Bump: FCK Hotkeys in Google Chrome - status?
CKEditor 3.0 in the works, I can guess (and prefer) that the new version hit the stands, instead of a 2.54 fork to fix small hotkey bugs in Chrome...
Re: FCK in Google Chrome