CKEditor 3.2 released!
This is an extremely important release for us. It takes the accessibility support in CKEditor to the highest levels. Now CKEditor implements and delivers an interface totally based on WAI-ARIA.
Accessibility, Taken Seriously
Since CKEditor 3.0, we've been always focused on delivering the best accessibility solutions in our editor. In fact, we have some good support for it since then, but we didn't stop our research over this important need.
In general, accessibility on the web has always been limited to satisfying specific recommendations and checklists, especially the WCAG and Section 508 requirements (which are fully satisfied by CKEditor, btw). But this approach has always been limited when talking about rich Internet applications, like CKEditor. Because of that, the W3C designed WAI-ARIA, which instead proposes standard ways to implement accessibility on modern applications. From the W3C web site:
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.
Today's accessibility tools, which include browsers and ATs (screen readers), are happy to have a standard into which base accessibility efforts. Other than that, WAI-ARIA started to be a requirement on software for government, military and enterprise corporations. All this together is making the market moving towards this new standard, which by the way is still a "working draft".
With CKEditor 3.2, we have now a unique WAI-ARIA based editing solution. But again, it's WAI-ARIA based, and this means that, to fully take advantage of it, you must use tools that well support this standard. Because of this, our recommendation today, and the supported platform for accessibility, is Firefox 3.5 and JAWS 11 (maybe other ATs can provide good support also). Other browsers have still quite poor support for WAI-ARIA, with exception to IE8, even if not perfect yet. And of course, the ATs themselves have their own limitations.
The nice thing is that WAI-ARIA has been designed with backwards compatibility in mind. This means that we're still able to provide the level of accessibility we're used to have with CKEditor 3.1 with non Firefox 3.5 browsers. Some of them, like IE6 have even shown enhancements with it.
Enjoy CKEditor 3.2! It's totally accessible... more than ever!
Update:
A few important issues (#5243, #5246 and #5250) have been detected right after the release of CKEditor 3.2. Today, 26 February (24 hours later), we've loaded new distribution files in our server. If you're one of the few users of the 3.2 revision 5191 (see About dialog), be sure to download CKEditor again.
Changelog
Check out the What's New? page for the full list of changes.
Download
License
CKEditor is available in Open Source and Commercial licenses. Full details can be found at our license page.
Reporting Issues
Please use the CKEditor development web site to report issues and suggestions through tickets.
Support
Community support is available through our forums. Visit the support page for additional options.
Other Products
Browse for images and files in CKEditor, with thumbnails, easy to use and intuitive context menu.
Commercial License
For many companies and products, Open Source licenses are not an option. This is why the Closed Distribution License (CDL) has been introduced.
Read more
Proud to Be
Comments
MediaWiki + CKEditor
To use ckeditor with mediawiki:
download and unpack the source ckeditor package
place it in the extensions directory of mediawiki
add the following lines to the end of mediawiki LocalSettings.php:
require_once("$IP/extensions/ckeditor/ckeditor.php");
$wgHooks['EditPage::showEditForm:initial'][] = 'showEditForm';
function showEditForm($form){
global $wgOut;
$wgOut->addScriptFile( '/extensions/ckeditor/ckeditor.js' );
$script =
"<script type=\"text/javascript\">
window.onload = function()
{
CKEDITOR.replace( 'wpTextbox1' );
};
if ( window.removeEventListener )
window.removeEventListener( 'load', mwSetupToolbar, false ) ;
else if ( window.detachEvent )
window.detachEvent( 'onload', mwSetupToolbar ) ;
</script>";
$wgOut->addHTML($script);
return true;
}
IE8 editor does not display (version 3.6.1)
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Win64; x64; Trident/4.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; Tablet PC 2.0; .NET4.0C)
Timestamp: Fri, 29 Jul 2011 15:25:02 UTC
Message: Expected identifier, string or number
Line: 278
Char: 8
Code: 0
Bug reporting
Hi,
could you please use our Development site to report this issue, as described here? It will allow our developers to inverstigate it. Thanks!
Hi,
I am new to world of freelancing but, I am not clear about the use of CK editor.
Next Phase After downloadind CKEDITOR
Hello,
I'm new to programming and just downloaded CKEDITOR to a websites folder on my computer. However, I have no idea how to actually intergrate it to Visual Studio and so am left in limbo. How do I actually intergrate it so that I may start using it soon?
Thank you
I personally love your editor
I personally love your editor tool. I was looking for something that I could use to create my own blog entries and semi-CMS for my personal site so that I didn't have to constantly update from home.
CKEditor will allow me to update my personal blog from anywhere now without having to use a cumbersome package like WordPress.
Excellent!
CKEditor 3.2 with ASP.NET
Hi,
Is CK Editor supports ASP.NET? Is there any ASP.NET User control available for this?
IE8 Problems
Hello CK!
I'm here inthe eternal search of a solution about this problem. CKEditor 3.2 have many troubles with IE8. The weird thing is that in the source site there are some that appears as solved. The following bugs get in this browser
Please let us know when CKEditor will be fully compatible with IE8, it's kind of nightmare this browser but is still used by the people
Thank you in advance
IE
The problem about editing contents inside an element with certain styles is solved for the next version, but I haven't seen any report about your second bug so it can't be fixed without a testcase.
IE
Mmm i've tried to reproduce the bug in the demo here in the page but it has no effect. It seems that I lost something in my code... Thank you for answering, i'll wait the next version. The tool is great
IE 8 Problems
Code to reproduce error:
<div style="position: relative; text-align: left; padding-bottom: 20px; padding-left: 20px; width: 350px; padding-right: 20px; float: left; overflow: hidden; padding-top: 20px">
test</div>
CKEditor 3.2 with ASP
I am using FCKEditor and I am evaluating CKEditor. I have a site with ASP/VBScript. In the downloaded .zip file there is no sub-folder in _sample about ASP integration.
Are you still supporting this (ASP)?
If yes then could you provide me a guide on how to do this? There is a page with ASP but inside it talks about .asp files that do not exist in the downloaded .zip installation file.
web
I very like CKEditor ,I hope you can give me about asp sourse !
I would like to receive your e-mail
asp wrapper
Hopefully an asp wrapper will be available in the next release. That's one of the tasks that I've pending to do.
design
Thanks for your editor guys. It's really the best among wysiwyg javascript editors. Only one but.
Design is so awful. Guys, this icons.. it's impossible, it's like windows 95.. just horrible. Please, do something with it. So many people use your editor, there're should be plenty of good designers among them. I don't believe that they can't create good icons for your editor..
Let's wait for the Skins repository
Still this year - hopefully sooner than later - we'll be launching our skins and plugins repository. We hope to have new skins there, which will include different sets of icons to satisfy everybody.
Mediawiki+CKEditor
Is there any word on how the Mediawiki intergration is going? There is a project, correct, to integrate the new editor into Mediawiki, right?
With the new rewrite, I'm not sure that I could successfully do the integration.
Thanks.
FCK, Please Respond
What are your plans to provide MediaWiki integration?
3.1.1 vs 3.2
Hey FCK,
Can you explain the reason for releasing both 3.1.1 and 3.2 today? Is upgrading to 3.2 more involved than 3.1.1?
-Brandon
3.2 = 3.1.1 + (New Features or "Intense" Fixes)
Hi Brandon. That's simply a new release standards we're using now.
Micro releases (3.1.1) are supposed to be bug fixing only releases. They should not contain important new features not even fixes that involve large code changes. So, upgrading from a closer previous release should be safer.
Minor releases instead bring more important code changes and additions. Because of this some developers consider minor releases more risky and prefer waiting a bit, or even perform a more extensive testing before using them.
So, we just want to give you the option. I hope this is useful.
Post new comment