> On 25 Aug 2016, at 18:36, Vincent Massol <[email protected]> wrote: > > Hi devs, > > Marius has recently introduced the honoring of text editor for xproperty > editing for textarea types. > > This is great but it’s causing a lot of backward compatibility issues. We’ve > fixed several xclass to use “puretext” for code but there are plenty out > there still. > > I’ve just found another one with XWiki.WatchListMessage. > > The issue is that this is a blocker. I was trying to make a change there so I > was editing using the “source” mode of CKEditor. The problem is that when I > saved there were a lot of changes made to the content automatically, breaking > the code, see for example: > https://www.evernote.com/l/AHf4KpfVtfBOK5zqcyf_up1Rty923fZOm-I > > The main issue is that I’m stuck. There’s nothing I can do in my wiki > (without resorting to scripting, using REST, etc). > > I’m proposing that we do the opposite: > * When no editor is specified, use the wiki editor. Apps that want WYSIWYG in > xproperties should say so. > > This is actually more logical to me because the object editor is a technical > editor. > > In any case we need a solution that doesn’t break backward compatiblity. > > Since this change of behavior (honoring the editor for xproperties in the > object editor) was introduced in XWiki 8.2 we need to act fast before it > becomes a problem for our users.
I forgot to mention that initially I was even using the GWT editor as my WYSIWYG editor and in that case I can’t even view the source since that doesn’t exist for GWT and thus those using GWT are even more stuck… Thanks -Vincent > WDYT? > > Thanks > -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
