inwardWysiwyg / outwardWysiwyg

[guest]

There are config functions for transforming the HTML on its way into and out of the WYSIWYG editor (config.inwardHtml and config.outwardHtml). It would be nice if there were also functions for just the WYSIWYG editor, where outwardWysiwyg would be called anytime you go to the edit-markup mode (and of course vice versa). inwardWysiwyg would also be called after inwardHtml, and outwardWysiwyg would be called before outwardHtml

[douglas]

I agree. We've been bandying this about here because it could make some things easier... I plan to look at this for the next Xinha release...

[ray]

I actually don't understand this. Could someone explain this a little more?

[guest]

Well, one example use case is iframes, which themselves aren't really editable inside the editor. It might be nice to do a transformation like /<(/?iframe.*?)>/[$1]/g which would turn the iframe tags into text. But in source mode there's no reason to have this transformation applied, it would be preferable to show the actual markup.

[douglas]

Ahh, I misunderstood the request. I thought you were asking for something similar to inwardHTML/outwardHTML but where you had access to the DOM nodes instead of the text.

[ray]

guest: This is exactly what's inward/outwardHTML does

doug: Interesting idea, even if it's not what guest was asking for :)

[guest]

Ah... if that's the case, then you can mark this ticket invalid.

[ejucovy]

Closing this ticket as invalid, because as ray said this is what inward/outwardHTML are for.