|Release Date:||March 15, 2012|
* Rewrote the enter key logic to normalize browser behavior.
* Fixed so enter within PRE elements produces a BR and shift+enter breaks/end the PRE. Can be disabled using the br_in_pre option.
* Fixed bug where the selection wouldn't be correct after applying formatting and having the caret at the end of the new format node.
* Fixed bug where the noneditable plugin would process contents on raw input calls for example on undo/redo calls.
* Fixed bug where WebKit could produce an exception when a bookmark was requested when there wasn't a proper selection.
* Fixed bug where WebKit would fail to open the image dialog since it would be returning false for a class name instead of a string.
* Fixed so alignment and indentation works properly when forced_root_blocks is set to false. It will produce a DIV by default.
|Notes Title:||TinyMCE 3.5b2 Released|
|Notes:||Time for another beta release of the 3.5 branch this one fixes a few issues with the last version but also introduces some new features. Since the HTML5 logic added more complexity to how the enter key works in the editor we decided to rewrite that logic from scratch and in the meantime introduce a few new features and options. [New br_in_pre option] This option is enabled by default and changes the behavior on how the enter key is used within a pre tag. Since most pre tags are used for things like code examples like on our Wiki it made more sense to produce a BR on enter by default and only split pre tags when hitting shift+enter. If you don't want this new behavior you can set the br_in_pre to false. [BR vs P] I've seen a lot of requests over the years to have better support for producing BR elements by default in the editor. And I have always tried to explain why paragraphs is better than br:s. But guess what I got some news for you BR fan boys out there this version now fully supports BR elements and things like alignment and indentation work it will auto generate a div if you don't have any block element to align or indent. The force_br_newlines/force_p_newlines where removed since it doesn't make sense to mix the forced_root_block option with that. So just set forced_root_block to false and it will start spitting out those pesky BR elements. :) If you want to split a block element while having forced_root_block set to false you would have to press shift+enter since enter will insert a BR within the block. We might add some option to control this as well in the future. [Changes noneditable plugin] There are still a few issues with this plugin that we need to address over the upcoming weeks. So I guess there will be a few more betas until we release the final of 3.5. Thanks for all bug reports and patches etc.|