TinyMCE Forum / TinyMCE 3.2.2 Released

spocke · 2009-03-05 14:30:41

It's been 4 months since our last release of TinyMCE. But that doesn't mean that we haven't been busy improving the editor.

This release includes a new CSS selector engine called Sizzle the same one jQuery uses. We have also improved the build process to use Apache Ant and some custom Ant tasks. Swapped the custom built unit testing framework with QUnit.

We have improved the integration of the CSS selector engine in many ways. The DOMUtils methods like getParent now supports full CSS expressions so you can use dom.getParents(node, 'div[attr=value],p.class') for example.

Some logic was moved out to plugins such as the tab_focus option is now a separate plugin called tabfocus. We have plans of moving out more things from the core to plugins over time.

Another important change is that as of this version the document.domain value will have to be setup manually by the user. Since there could be conflicting scripts doing the same thing and there where other reasons for us to change this behavior. So this will affect users loading the editor cross subdomain we will add some details regarding this in the wiki.

The core API has now also a full fledged DOM Range implementation for IE. In plain English this means that we have a common ground now for all browsers to build TinyMCE upon. Not having a DOM Range implementation in IE was has produced lots of IE specific workarounds over the years and we can now rewrite and fix these kinds of issues more easily.

We fixed a lot of browser specific bugs for new browsers like IE 8 and Safari 4. But it's important to understand that Safari 4 is still released as Beta so it contains bugs and issues and shouldn't be treated as stable yet. It's called "beta" for a reason. However we are impressed with the JS/DOM performance in this new browser version.

Once again we like to thank everyone who contributed patched and bug reports for this release.

Damien · 2009-03-05 15:07:45

Given the core architecture change of using Sizzle for the selector engine, shouldn't this have been given a larger version number bump, e.g. 3.3?

spocke · 2009-03-05 15:34:11

We didn't introduce that many external features. It's mostly internal engine things that's been changed. But maybe it should have had a different version number.

Damien · 2009-03-05 15:43:16

It's still involved rewrites to the core engine, presumably several month's of work, I think it really should have been v3.3 or even v4 to indicate the major internal change.

Felix Riesterer · 2009-03-05 16:23:57

Be the version number what it is - GREAT WORK ONCE AGAIN!!!

I just love this software... can't help it.

spocke · 2009-03-05 16:30:46

@Damien: Yes, I guess but I don't want to run out of version numbers after a while you then tend to need to find odd new names like X or 2009 instead of version numbers. But 3.3 would have been a better name. But now when it's released it's hard to change it. To late.

@Felix: Thanks man, and thanks for helping out in the forum.

Damien · 2009-03-05 16:47:23

You could always just change a comment and then release a Brand New Version ;-)

tan · 2009-03-05 18:20:14

Congratulation on the new release guys!
Great Work!

I am looking forward use the new API and see Sizzle integration in action.

Yes, as you said Spocke, Safari 4 is in beta so we all have to wait, but the modal dialog does not work in OS X/Safari4b on the demonstration page.

spocke · 2009-03-05 19:44:18

Make sure you clear your cache. Works fine in my Safari 4 on PC at least.

happy_noodle_boy · 2009-03-05 20:44:35

Thanks for the new release. Really like the Sizzle inclusion.

Pity you missed these 2 bugs:

https://sourceforge.net/tracker/?func=d … tid=635682
https://sourceforge.net/tracker/?func=d … tid=635682

spocke · 2009-03-05 21:05:31

Yeah, this release was long overdue to adding more to the list before the release was not possible. I will checkout this bugs for the next version though.

happy_noodle_boy · 2009-03-05 21:09:59

Thanks, of course I'm very appreciative of the updates and don't mean to sound otherwise.

It would seem that the code/samp bug is a browser issue with the 'FormatBlock' command and not a TinyMCE bug.

spocke · 2009-03-05 21:32:23

Yes, I have plans of replacing the FormatBlock with my own logic. I will do this more and more I'm just fed up with all the browser issues with the built in commands.

Sword · 2009-03-05 23:21:00

thank you, its nice to get new TinyMCE 3.2.2 release

tan · 2009-03-06 00:01:44

Yeah! I always forget about that

spocke wrote:
Make sure you clear your cache. Works fine in my Safari 4 on PC at least.

thorn · 2009-03-06 00:02:23

spocke wrote:
@Damien: Yes, I guess but I don't want to run out of version numbers after a while you then tend to need to find odd new names like X or 2009 instead of version numbers.

Offtopic: among these odd names we can find X3 (Corel Draw, ABBYY Lingvo) which if treat it as the Russian letters passes into the popular slang acronym with 'f@ck knows' meaning. :-)

benkrembs · 2009-03-06 04:15:06

Hmm.. what happened to the source for tiny_mce_popup.js? The version of that file in the dev distribution is minified.

I only ask because I had to make some tweaks to get Tiny working with the Dojo Toolkit -- and it's hard to reapply the fixes to that file when it's minified

4midori · 2009-03-06 07:27:52

Hi Spocke,

I looked at the changelog, and didn't see the acronym tag bug listed, that is, when adding more than one acronym, the first acronym tag used gets repeated for all acronym tags.

Was this fixed in 3.2.2?

Thanks,

Ben

spocke · 2009-03-06 10:21:30

@benkrembs: The source for it is available in the dev package under classes/Popup.js. Is there are incompatibilities with Dojo please report them at SF.
@4midori: That bug is now resolved. I guess I missed adding it to the changelog.

danielpott · 2009-03-06 11:29:13

Hi Spocke,

I can't get TinyMCE 3.2.2 to "ask" me anymore if it should be used.
"ask = true"
doesn't work here anymore?
Anyone else seen this?

Best Regards
Daniel

spocke · 2009-03-06 11:54:18

Hah, was there really someone using that feature. We removed it since I've never seen a implementation where it was used. How ever we recommend using a load on demand approach instead:
http://tinymce.moxiecode.com/examples/example_12.php

This gives the user the ability to change he's mind if he wants the rich mode on/off. This is how most systems use an optional wysiwyg mode. But if there are many demands to reintroduce this feature we will probably do it but hopefully not. It has produced some strange bugs over the years.

danielpott · 2009-03-06 11:57:23

Hi Spocke,

we are using a Mediawiki with TinyMCE and if I want to change some System settings in Mediawiki I have to edit them without TinyMCE so I switch ask to true for a few seconds, change the settings and turn ask to false again.
Any chance to get it back? I don't need a permanent on demand approach just once in a while?

Thanks

Best Regards
Daniel

strzelecki · 2009-03-06 18:22:12

Is there a list of files that have changed from the last version available? Would save having to copy over everything an re-implementing customisation. Perhaps this could be appended to the changelog in the future?

Great work though!

j2jensen · 2009-03-06 19:00:20

danielpott wrote:
we are using a Mediawiki with TinyMCE and if I want to change some System settings in Mediawiki I have to edit them without TinyMCE so I switch ask to true for a few seconds, change the settings and turn ask to false again.

Daniel,

It's fairly easy to disable TinyMCE using FireBug. You just remove the "mceEditor" span from the DOM, and make the textarea visible again. Changing a feature site-wide for a few seconds doesn't seem to be a very elegant way to go about it.

spocke · 2009-03-07 14:32:09

@danielpott: Yes, I think there is better ways around this. Check the examples on this site on how to add/remove the editor on the fly.

#1 2009-03-05 14:30:41

TinyMCE 3.2.2 Released

#2 2009-03-05 15:07:45

Re: TinyMCE 3.2.2 Released

#3 2009-03-05 15:34:11

Re: TinyMCE 3.2.2 Released

#4 2009-03-05 15:43:16

Re: TinyMCE 3.2.2 Released

#5 2009-03-05 16:23:57

Re: TinyMCE 3.2.2 Released

#6 2009-03-05 16:30:46

Re: TinyMCE 3.2.2 Released

#7 2009-03-05 16:47:23

Re: TinyMCE 3.2.2 Released

#8 2009-03-05 18:20:14

Re: TinyMCE 3.2.2 Released

#9 2009-03-05 19:44:18

Re: TinyMCE 3.2.2 Released

#10 2009-03-05 20:44:35

Re: TinyMCE 3.2.2 Released

#11 2009-03-05 21:05:31

Re: TinyMCE 3.2.2 Released

#12 2009-03-05 21:09:59

Re: TinyMCE 3.2.2 Released

#13 2009-03-05 21:32:23

Re: TinyMCE 3.2.2 Released

#14 2009-03-05 23:21:00

Re: TinyMCE 3.2.2 Released

#15 2009-03-06 00:01:44

Re: TinyMCE 3.2.2 Released

spocke wrote:

#16 2009-03-06 00:02:23

Re: TinyMCE 3.2.2 Released

spocke wrote:

#17 2009-03-06 04:15:06

Re: TinyMCE 3.2.2 Released

#18 2009-03-06 07:27:52

Re: TinyMCE 3.2.2 Released

#19 2009-03-06 10:21:30

Re: TinyMCE 3.2.2 Released

#20 2009-03-06 11:29:13

Re: TinyMCE 3.2.2 Released

#21 2009-03-06 11:54:18

Re: TinyMCE 3.2.2 Released

#22 2009-03-06 11:57:23

Re: TinyMCE 3.2.2 Released

#23 2009-03-06 18:22:12

Re: TinyMCE 3.2.2 Released

#24 2009-03-06 19:00:20

Re: TinyMCE 3.2.2 Released

danielpott wrote:

#25 2009-03-07 14:32:09

Re: TinyMCE 3.2.2 Released

Board footer