0 results found

Content Appearance

Configure the appearance of content inside TinyMCe's editable area.

Contribute to this page

body_class

This option enables you to specify a class for the body of each editor instance. This class can then be used to do TinyMCE specific overrides in your content_css. There is also a specific mceForceColors class that can be used to override the text and background colors to be black and white.

Type: String

Example

This will add the same class to all editors that gets created by the init call.

tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  body_class: 'my_class'
});

This will set specific classes on the bodies of specific editors.

tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  body_class: 'elm1=my_class, elm2=my_class'
});

body_id

This option enables you to specify an id for the body of each editor instance. This id can then be used to do TinyMCE specific overrides in your content_css.

Type: String

Example

This will add the same id to all editors that gets created by the init call.

tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  body_id: 'my_id'
});

This will set specific ids on the bodies of specific editors.

tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  body_id: 'elm1=my_id, elm2=my_id2'
});

content_css

It is usually desirable that TinyMCE's editable area has the same styling as the surrounding content. This can be achieved with the content_css option, which enables you to extend external css into the editable area.

The css file used in this setting should be the same css file that controls the look/style of all your pages. So, let's say you include a file myLayout.css in all your pages to control your site's global appearance, then this file must be set as your content_css value. Doing this will ensure the content in the editable area will also have your site's style.

Note: if you specify a relative path, it is resolved in relation to the URL of the (HTML) file that includes TinyMCE, not relative to TinyMCE itself.

Type: String

Absolute path example
// File: http://domain.mine/mysite/index.html

tinyMCE.init({
  selector: 'textarea',  // change this value according to your HTML
  content_css : '/myLayout.css'  // resolved to http://domain.mine/myLayout.css
});
Relative path example
// File: http://domain.mine/mysite/index.html

tinyMCE.init({
  selector: 'textarea',  // change this value according to your HTML
  content_css : 'mycontent.css'  // resolved to http://domain.mine/mysite/mycontent.css
});
Using multiple stylesheets example
tinyMCE.init({
  selector: 'textarea',  // change this value according to your HTML
  content_css : 'mycontent.css,mycontent2.css'  // includes both CSS files in header
});
Using multiple stylesheets as array example
tinyMCE.init({
  selector: 'textarea',  // change this value according to your HTML
  content_css: ['mycontent.css', 'mycontent2.css']  // includes both CSS files in header, ability to have CSS with `,` in URL
});

A note regarding browser caching

Browser caching might cause TinyMCE to not read the contents of a changed CSS file. You'll see "old" colors & styles.

One solution is to manually clear the browser cache when the file for content_css or editor_css has changed. Another solution is to use an old hack which adds a bogus parameter to the URL containing a present time stamp like "myFile.css?bogus=10023561235". Possible solutions could look like this:

tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  content_css: 'path/myfile.css?' + new Date().getTime()
});
tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  content_css: 'path/myscript.php?myParam=myValue&bogus=' + new Date().getTime()
});

content_style

This option allows you to set custom CSS styles as a string that will be injected into the editor's iframe.

These styles are useful for previewing content as it will appear outside the editor. Since these styles are not saved with the content, it is important that they match the styles in the location that the content will appear.

Type: Object

Example
tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  content_style: "div {margin: 10px; border: 5px solid red; padding: 3px}"
});

visual_anchor_class

This option enables you to configure a custom class to be added to anchors with names since these are invisible by default.

Type: String

Example
tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  visual_anchor_class: 'my-custom-class'
});

visual_table_class

This option enables you to configure a custom class to be added to tables that have a border set to 0. This class is used to add dotted borders to tables that would otherwise be invisible for the user.

Type: String

Example
tinymce.init({
  selector: 'textarea',  // change this value according to your HTML
  visual_table_class: 'my-custom-class'
});

visual

This true/false option gives you the ability to turn on/off the visual aid for tables with no borders. If the border of a table is set to 0, then TinyMCE adds a dotted line around the table by default.

Type: Boolean

Default Value: true

Possible Values: true, false

Example
tinymce.init({
  selector: 'textarea',  // change this value according to your HRML
  visual: false
});

Except as otherwise noted, the content of this page is licensed under the Creative Commons BY-NC-SA 3.0 License, and code samples are licensed under the Apache 2.0 License.