Rich text fields let you use formatting such as bold text, lists and links. However, they do not behave exactly the same way everywhere in miniExtensions or in Airtable. This guide explains the differences and what to do if your formatting changes.
Rich text in the grid
The grid displays rich text as plain text when you are not editing the cell. Opening the record in its form lets you view and edit the formatted field. Increasing the grid row height does not restore rich-text formatting.
This grid limitation does not apply to every layout: list and gallery fields can display rich-text formatting. If a link or formatting is missing there, compare the same field in the record’s form and contact us with an example rather than assuming it is unsupported.
Italics and formatting controls
The formatting toolbar does not include an italics button. To italicize text, select it in the rich-text editor and press Ctrl+I on Windows or Command+I on Mac.
If a formatting control does not work while you are editing a grid cell, open the record’s form and edit the field there instead. See Inline Editing in the Grid View for the other differences between inline editing and using the form.
Line breaks and blank space
A single line break in Airtable can appear as a space in miniExtensions. To separate two paragraphs, leave a blank line between them in Airtable, that is, use two line breaks instead of one.
Extra empty lines are not a reliable way to control spacing. Use short headings or visible separator text to divide sections, and check how the field looks in miniExtensions. The spacing around bullet points and numbered lists may also look different from Airtable.
If lists or formatting change after editing
When working with indented lists or carefully spaced text, check a sample record after saving in both miniExtensions and Airtable before making the same changes to many records.
If list items lose their indentation, line breaks disappear, extra spacing appears around a list, or an unexpected backslash appears, keep a copy of the original text and contact us with a before-and-after example. Include whether you edited in the grid or in the record’s form. These symptoms need to be checked against the particular content; they do not mean that lists or rich text are unsupported altogether.
If the editor collapses or stops responding
Do not save an incomplete value. Contact us with the extension link, the affected field, your browser version, and the steps that trigger the problem, for example, whether it happens only after closing and reopening a record.
If you do not need formatting, a separate plain long-text field is an alternative. Keep the original rich-text field while you test; do not turn off its formatting just to troubleshoot if you need to preserve it.
Downloading rich text as CSV
A CSV download does not preserve rich-text formatting, and long rich-text values can be shortened. See the CSV download guide for the limitation and plain-text workaround.