Re: TinyMCE Integration

If this will reduce the number of times I see a "Please remove PRE tags" consideration, then I am all for it!

On the other hand, does this mean that I will need to enable JavaScript to use it?

If the answer is yes, is there any thought toward running TinyMCE in it's own JavaScript-enabled sand-box, separate from the rest of the Monastery? Or encapsulating the call so that JavaScript is only turned on for the duration of time I am using TinyMCE? I guess I am just getting crotchetty in my old age; all this New-fangled Ajax-y mark-up make me twitchy.

(Now there's a thought -- am I turning into a Luddite Geek? "If it was good enough for Sir Tim back in ought-nineteen, then it's good enough for you, you Young Turk!!" Now where did I put my wooden mouse and keyboard? )

----
I Go Back to Sleep, Now.

OGB

Comment on Re: TinyMCE Integration

Replies are listed 'Best First'.
Re^2: TinyMCE Integration by Anonymous Monk on Oct 20, 2009 at 19:04 UTC
What is the reason PRE tags don't behave like CODE tags? I think we should nip this in the bud once and for all	[reply]
Re^3: TinyMCE Integration by planetscape (Chancellor) on Oct 21, 2009 at 11:09 UTC
Please see the note at the bottom of Saturn re: changing "pre" to "code". HTH, planetscape	[reply]
Re^4: TinyMCE Integration (pre) by tye (Sage) on Oct 21, 2009 at 15:09 UTC
How about updating the default CSS so that PRE blocks automatically get horizontal scrollbars if needed (on the more common browsers)? - tye	[reply]
Re^5: TinyMCE Integration (pre) by Anonymous Monk on Oct 22, 2009 at 11:34 UTC
Re^4: TinyMCE Integration by Anonymous Monk on Oct 21, 2009 at 12:06 UTC
Oh, it might break old nodes, in that case, maybe a silent substitution ( s/PRE/CODE/ ) on first preview might be in order.	[reply]