id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 2657,"""Real"" inline editing request - similar or using contentEditable (see http://mozile.mozdev.org/)",Ludo,,"Hi, Before you read go to http://mozile.mozdev.org if you are not familiar with it. I would like to use what I would call ""real inline editing"" meaning we could keep the elements on a page without creating iFrames which lose all the CSS (because in CSS there is 'cascading'). A H1 tag lost in an iFrame created on the fly will not inehrit the special cascading CSS rules provided for a specific DOM element (as in div.MainContent > H1). One would assume that this has been discussed but I can't find anything about it. I'm sure it's very much within the capability of FCKeditor but it doesn't seem obvious how to achieve as it doesn't seem to have been scoped for so far. Simply imagine using contentEditable = 'true' (compatible with FF2, IE5.5 and Safari) or another more 'standard friendly' way for any element and being able to use the toolbar to edit the content in the same way as we're currently doing with iFrames. The goal is to be able to edit specific ""editable areas"" of the page based on templates. The same way Dreamweaver templates and asp.net MasterPages work. The best would be to use the current CreateHtml() technique to swap modes on elements based on their class or id and then enable the toolbar on focus... Which is exactly how Mozile work apparently (http://mozile.mozdev.org/). Please tell me it's already possible ;-) Thanks, Ludo",New Feature,closed,Normal,,General,,fixed,,