This release contains mainly bug fixes for the previous beta. We will only fix critical bugs after this rc to get a stable 3.3 version out we will probably release the stable version early next week.
Thanks for helping out with the testing and reporting all bugs and issues you found.
Thank you for TinyMCE 3.3rc1 Release 
I hope you will release stable version early next week 
Huzzah to the Moxie team! Can't wait for 3.3 final to "ship"!
Huzzah to the Moxie team! Can't wait for 3.3 final to "ship"!
Me too! Love the editor (obviously) 
Hello, I am wondering what version your examples page is running. I am seeing some bugs in webkit browsers that don't appear on your examples page - but the examples page doesn't appear to be creating the same javascript elements / calls that mine is.
The examples uses 3.3rc1 the latest version.
Thanks, spocke. I've ugpraded to rc1 in our test environment and all of my Webkit issues went away (which is probably to be expected given your release notes).
TinyMCE is top notch!
Yes, we have been working with WebKit issues a lot lately. Mainly since Chrome is getting more and more users. But still WebKit is a horrible browser when it comes to rich text editing. 
Hi,
nice to see new releases. Very great job.
A minor thing:
Could you fix the force_br_newlines stuff working not only for IE ?
Yes I read a lot about your opinion about br/p tags...and agree, but if there is this option it should work for all browsers, right ?
See line 11441:
if (s.force_br_newlines) {
// Force IE to produce BRs on enter
if (isIE) {
Thanks for answer about or a fix.
Cheers
Lolo
Last edited by Lolo irie (2010-02-26 11:54:25)
It has various quirks we have corrected a few of them in the 3.3 branch so we have done some work on the br line breaks issue.
However the feature works on all browsers use this setup:
force_br_newlines : true,
force_p_newlines : false,
forced_root_block : ''
Hi, thanks for the quick answer, but...
using following code:
force_br_newlines : true,
force_p_newlines : false,
forced_root_block : ''
doesn't work in Firefox like in IE.
Firefox continues to add P Tag instead BR Tags...
Deleting the if(isIE) does the job here...
I just downloaded the jQuery package tinymce_3_3rc1_jquery.zip
Unfortunately it didn't work on Firefox 3.6. I ran it like this:
file:///C:/tinymce_3_3rc1_jquery/tinymce/examples/index.html
but the toolbar did not render so I am only seeing the plain textarea. Is it not supposed to work this way?
It works in Chrome and IE though.
I also downloaded tinymce_3_3rc1.zip and the code worked in Firefox, Chrome and IE.
Is there something wrong with the file(s) in tinymce_3_3rc1_jquery.zip?
@Lolo irie: Works perfectly fine on my FF. It will continue to split existing P elements so will IE but that is a different thing since it must do this. Removing the IE check is not a solution. In fact that logic if faulty it should not force BR if you are within a block element such as a P. Will fix that when we move all the br enter logic out to a plugin.
@klbytec: You need to load it though a real web server. FF has security restrictions on loading scripts out side the current directory. Maybe we need to add a check for this to each example script telling the user to load it using a real web server.
Have loaded version 3.3rc1 which works fine in IE but refuses to give the WYSIWYG editor in Firefox 3.5.8, will need to backtrack the version
Strange does it load correctly on the examples n this site? Could be some odd FF extension.
I have raised a bug on sourceforge relating to the spellchecker in IE8. Whenever you select a word to replace a mis-spelled word the browser completely crashes. This has been introduced since the last release, and is reproducable in the 2nd beta and the current release candidate.
Is there already a release date for the stable version of tinymce?
Need to fix the IE8 crash bug, this is currently the only thing holding the release back.
I think I found a bug.
I used to insert a javascript snippet into the header to make the iframe transparent. This doesn't work with this version for some reason.
Does anyone know another way for making the iframe transparent?
The code snippet I use is:
<script type="text/javascript">
onload = function()
{
var theframes = document.getElementsByTagName(\'iframe\');
for(var i = 0; i < theframes.length; i++)
{
theframes[i].setAttribute("allowTransparency","true");
}
}
</script>
That is some form of implementation issue not a bug.
I have a question:
Have you changed the way styling is done? I can no longer add classes to block elements using the style drop down. So if I had <p>my content</p>, there is no way to make <p class="example1">my content</p> using Tiny's interface, just <p><span class="example1">my content</span></p>.
Yes, we switched it to be more powerful. You can now specify that the class should only be applied to block elements. However it seems that people are missing this old feature so we might re-add it later in 3.3.1 or similar but right now we need to get the 3.3 out of the door and since you can configure it to use block level classes it's not something we need to address right away.
>Lolo irie and Spocke
Hi, I'd like to make an additional comment to Lolo's post.
Just yo let you know, it can be occurred in our environment.
TinyMCE make a <br /> code in NEW SENTENCE when we make a setting in"set force_br_newlines" as Lolo said.
Though we cannot have a <br /> code when we write some sentences in EXISTING DOCUMENT DATA and it have <p> paragraphs, even if we set "set force_br_newlines".
Yama and I tested and it occurred repeatedly.
So I'd rather you check this issue again.
Sincerely,
Nick of Tokyo, Japan
That is good to know. We use Tiny for our CMS and we cannot move forward with Tiny without the support of both block and span classing. If you re-add it later would it be as a plug-in? Maybe a duel drop-down system: one for inline elements and one for block?
We love Tiny. Thanks again for all your hard work.
Sincerely,
Max
Both block/span classing is available now though the style_formats option. Just not a mixed scenario where you some times have the class on spans some times on blocks. This will probably be added to the core of the formatter, will be a bit strange to setup since I guess you would want to specify what elements it should bleed out to etc.
You are not logged in. Please login or register.
