Hi Leon, Guillaume Lerouge wrote: I guess this is not well explained in the documentation. Leon, can you improve it to make it more explicit? First you have to get a reference to the WYSIWYG editor instance. Currently we don't save such a reference when we create the editor to edit the page content. You have two options: 1) edit the wysiwyg_createEditor velocity macro from macros.vm and replace: new WysiwygEditor($jsVarName); with something like window["${fieldId}_editor"] = new WysiwygEditor($jsVarName); Of course, you can name the reference as you wish. 2) use prototype to catch the "xwiki:wysiwyg:created" custom event which should have a property called "instance" that points to the newly created WYSIWYG editor. Prototype gurus should be able to provide more help here. Once you have a reference to the WYSIWYG editor you can interact with it in two ways: i) access the editor in Java (GWT) code by writing a simple native getter like: native WysiwygEditor getEditor() /*-{ return editorJSReference.@com.xpn.xwiki.wysiwyg.client.editor.WysiwygEditorApi::editor; }-*/; NOTE: This forces your application to depend on the WYSIWYG code which means your compile time will increase and the resulting JavaScript code will include the WYSIWYG code. This way the editor JavaScript code will be duplicated. If you want to go this way then you can change the background color of the selected text with this: getEditor().getRichTextEditor().getTextArea().getCommandManager().execute(Command.BACK_COLOR,"yellow"); ii) use the editor JavaScript API and don't depend at all on WYSIWYG Java code. This is not possible right now but I can extend the native JavaScript API so that you can write something like: native void setBackgroudColor(String color) /*-{ editorJSReference.execute('backcolor', color); }-*/; Let me know if you needs this. Hope this helps, Marius