Are you adding the style definition directly in the source edit mode? This is not recommended practice and might result in the bahavior you are experiencing.You can define styles that can be selected from a drop down selection box - this is covered (AEM 6) under:Styles (Text)However, it might depend...

Unfortunately custom styles in the RTE are not currently supported for the touch-optimized UI. Please see the documentation at:Plugins and their Features - Touch-optimized UIPredefined Styles and FormatsThey are supported for the classic UI.

I don't know about the roadmap, but at the moment (6.0) Design Mode is only available in the classic UI. See:http://docs.adobe.com/docs/en/aem/6-0/author/page-authoring/author-environment-tools.html#Page%20Modes

OK, sorry for the delay on this, but we have been testing and checking details with the development department this week.The feedback is that:TableThese are available when using the Table component.Heading chooser (paraformat)This works in both classic and touch UI.The documentation has been updated...

Hello againI have tested configuration of the paraformat and although it does work, there are a few key pieces of information missing from the documentation. Unfortunately it will take another few days to get the full details (for the various scenarios) confirmed. I'm also confirming some details ab...

Have you configured the two plugins?http://docs.adobe.com/docs/en/aem/6-0/administer/operations/page-authoring/rich-text-editor.html#Paragraph%20Formatshttp://docs.adobe.com/docs/en/aem/6-0/administer/operations/page-authoring/rich-text-editor.html#Styles%20%28Tables%20and%20Table%20Cells%29I will t...

HelloI've checked this with the developer and paraformat (and styles) are now supported - but only in full-screen mode. See:http://docs.adobe.com/docs/en/aem/6-0/author/page-authoring/editing-content.html?#Edit%20%28Content%29%20Full%20Screen%20Mode%20-%20Touch-optimized%20UIApologies there was a di...

Hello,I have confirmed this with the developer and the recommended method is:Overlay the link dialog.Change the configuration of the path field:In your /apps version of:     /libs/cq/ui/widgets/source/widgets/form/rte/plugins/LinkDialog.jsAs always, you must not make any changes in the /libs branch ...

Thanks for the info - and just to let you know - I've tried on a straight-out-of-the-box installation, but I can't reproduce any of the issues.

Can we ask you to confirm which version of AEM/CQ you are using?Also, just to check - is this happening for every user account?Thanks for the information