All from FCKeditor

This is one of the most important phases in the editor development: "testing". A well done test period ensures that upgrading current installations of FCKeditor will just provide enhancements to your software, and not unexpected results.

So please, participate. As more testers we have as more tested new versions will be, and this reverts to advantage to you, FCKeditor community.

How to test?

Tests can be done online, by following the link provided at the end of the page. You can also download the installation package and test it in your local environment.

What to test?

Each version is an evolution of the previous one. So, the most important thing to check is that the new version is not introducing new bugs not present in the latest public version.

Important things to test are:

• Interface behavior: editing area, toolbar components, context menu, dialog windows, etc...
• Code generation: looking at the source view for wrong code.
• File Browser: can be launched from the Image, Link and Flash dialogs.
• All samples: be sure that every sample is working correctly. All test cases (_testcases directory) must also work well.
• The "What's New?" file is a good reference of things to be tested.
• Whenever possible, test it on real cases.

Testing on real cases

The best way to be sure FCKeditor will be ok when upgrading, is by testing it on your current applications. In this way, things that may be missing in the samples can be tested and specific problems can be detected.

Where to publish your results

For every new version, we’ll be opening our "Test Results" forum for discussions regarding the tests. Just go to that forum and leave any information you think is useful. Not only negative tests results are good in this phase, but also positive feedback, so we can measure the results.

Please just post information strictly related to testing results. I understand that all you have expectations regarding new versions, but consider each version as an evolution of the previous one. No new development will be done (even to fix know bugs on previous versions), just fixes to new issues.

Testers Mailing List

If you want to receive a message when new tests are opened, please subscribe to our Testers Mailing List. Thanks in advance for your collaboration.

Current test

The testing version corresponds to our SVN "trunk". New developments will not be committed during the testing period, so you can also retrieve the proposed code for this new version from there.

New Features and Improvements:

• The project has been relicensed under the terms of the GPL / LGPL / MPL licenses. This change will remove many licensing compatibility issues with other open source licenses, making the editor even more "open" than before.
• [SF Feature-1329273] [SF Feature-1456005] [SF BUG-1315002] [SF BUG-1350180] [SF BUG-1450689] [SF BUG-1461033] [SF BUG-1510111] [SF BUG-1203560] [SF BUG-1564838] The advance Enter Key Handler is now being introduced. It gives you complete freedom to configure the editor to generate <p>, <div> or <br> when the user uses both the [Enter] and [Shift]+[Enter] keys. The new "EnterMode" and "ShiftEnterMode" settings can be use to control its behavior. It also guarantees that all browsers will generate the same output.
• The new and powerful Keyboard Accelerator System is being introduced. You can now precisely control the commands to execute when some key combinations are activated by the user. It guarantees that all browsers will have the same behavior regarding the shortcuts.
  It also makes it possible to remove buttons from the toolbar and still invoke their features by using the keyboard instead.
  It also blocks all default "CTRL based shortcuts" imposed by the browsers, so if you don't want users to underline text, just remove the CTRL+U combination from the keystrokes table. Take a look at the FCKConfig.Keystrokes setting in the fckconfig.js file.
• The new "ProtectedTags" configuration option is being introduced. It will accept a list of tags (separated by a pipe "|"), which will have no effect during editing, but will still be part of the document DOM. This can be used mainly for non HTML standard, custom tags.
• Dialog box commands can now open resizable dialogs (by setting oCommand.Resizable = true).
• Updated support for AFP. Thanks to Soenke Freitag.
• New language file:
  • Afrikaans (by Willem Petrus Botha).
• [SF PATCH-1456343] New sample file showing how to dynamically exchange a textarea and an instance of FCKeditor. Thanks to Finn Hakansson
• [SF PATCH-1496115] [SF BUG-1588578] [SF BUG-1376534] [SF BUG-1343506] [SF Feature-1211065] [SF Feature-949144] The content of anchors are shown and preserved on creation. *
• [SF Feature-1587175] Local links to an anchor are readjusted if the anchor changes.
• [SF PATCH-1500040] New configuration values to specify the Id and Class for the body element.
• [SF PATCH-1577202] The links created with the popup option now are accessible even if the user has JavaScript disabled.
• [SF PATCH-1443472] [SF BUG-1576488] [SF BUG-1334305] [SF BUG-1578312] The Paste from Word clean up function can be configured with FCKConfig.CleanWordKeepStructure to preserve the markup as much as possible. Thanks Jean-Charles ROGEZ.
• Attention: The default directory in the distribution package is now named "fckeditor" (in lowercase) instead of "FCKeditor".  This change may impact installations on case sensitive OSs, like Linux.
• Attention: All connectors are now pointing by default to the "/userfiles/" folder instead of "/UserFiles/" (case change). Also, the inner folders for each type (file, image, flash and media) are all lower-cased too.
• Attention: The "Universal Keyboard" has been removed from the package. The license of those files was unclear so they can't be included alongside the rest of FCKeditor.
• Attention: The UseBROnCarriageReturn configuration is not anymore valid. The EnterMode setting can now be used to precisely set the enter key behavior.

Fixed Bugs:

• [SF BUG-1444937] [SF BUG-1274364] Shortcut keys are now undoable correctly.
• [SF BUG-1015230] Toolbar buttons now update their state on shortcut keys activation.
• [SF BUG-1485621] It is now possible to precisely control which shortcut keys can be used.
• [SF BUG-1573714] [SF BUG-1593323] Paste was not working in IE if both AutoDetectPasteFromWord and ForcePasteAsPlainText settings were set to "false".
• [SF BUG-1578306] The context menu was wrongly positioned if the editing document was set to render in strict mode. Thanks to Alfonso Martinez.
• [SF BUG-1567060] [SF BUG-1565902] [SF BUG-1440631] IE was getting locked on some specific cases. Fixed.
• [SF BUG-1582859] [SF Patch-1579507] Firefox' spellchecker is now disabled during editing mode. Thanks to Alfonso Martinez.
• Fixed Safari and Opera detection system (for development purposes only).
• Paste from Notepad was including font information in IE. Fixed.
• [SF BUG-1584092] When replacing text area, names with spaces are now accepted.
• Depending on the implementation of toolbar combos (mainly for custom plugins) the editor area was loosing the focus when clicking in the combo label. Fixed.
• [SF BUG-1596937] InsertHtml() was inserting the HTML outside the editor area on some very specific cases.
• [SF BUG-1585548] On very specific, rare and strange cases, the XHTML processor was not working properly in IE. Fixed.
• [SF BUG-1584951] [SF BUG-1380598] [SF BUG-1198139] [SF BUG-1437318] In Firefox, the style selector will not anymore delete the contents when removing styles on specific cases.
• [SF BUG-1515441] [SF BUG-1451071] The "Insert/Edit Link" and "Select All" buttons are now working properly when the editor is running on a IE Modal dialog.
• On some very rare cases, IE was throwing a memory error when hiding the context menus. Fixed.
• [SF BUG-1526154] [SF BUG-1509208] With Firefox, <style> tags defined in the source are now preserved.
• [SF BUG-1535946] The IE dialog system has been changed to better work with custom dialogs.
• [SF BUG-1599520] The table dialog was producing empty tags when leaving some of its fields empty.
• [SF BUG-1599545] HTML entities are now processed on attribute values too.
• [SF BUG-1598517] Meta tags are now protected from execution during editing (avoiding the "redirect" meta to be activated).
• [SF BUG-1415601] Firefox internals: styleWithCSS is used instead of the deprecated useCSS whenever possible.
• All JavaScript Core extension function have been renamed to "PascalCase" (some were in "camelCase"). This may have impact on plugins that use any of those functions.
• [SF BUG-1592311] Operations in the caption of tables are now working correctly in both browsers.
• Small interface fixes to the about box.
• [SF PATCH-1604576] [SF BUG-1604301] Link creation failed in Firefox 3 alpha. Thanks to Arpad Borsos
• [SF BUG-1577247] Unneeded call to captureEvents and releaseEvents.
• [SF BUG-1610790] On some specific situations, the call to form.submit(), in form were FCKeditor has been unloaded by code, was throwing the "Can't execute code from a freed script" error.
• [SF BUG-1613167] If the configuration was missing the FCKConfig.AdditionalNumericEntities entry an error appeared.
• [SF BUG-1590848] [SF BUG-1626360] Cleaning of JavaScript strict warnings in the source code.
• [SF BUG-1559466] The ol/ul list property window always searched first for a UL element.
• [SF BUG-1516008] Class attribute in IE wasn't loaded in the image dialog.
• The "OnAfterSetHTML" event is now fired when being/switching to Source View.
• [SF BUG-1631807] Elements' style properties are now forced to lowercase in IE.
• The extensions "html", "htm" and "asis" have been added to the list of denied extensions on upload.
• Empty inline elements (like span and strong) will not be generated any more.

* This version has been partially sponsored by Medical Media Lab.