---
title: "Code view"
slug: "code-view"
description: "Master Code view in the Advanced WYSIWYG editor to edit HTML, fix unsupported tags, and enhance your articles with custom elements and styles."
updated: 2026-06-02T13:21:14Z
published: 2026-06-02T13:21:14Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Code view

**Code view** lets you inspect and edit the underlying HTML of an article directly in the Advanced WYSIWYG editor, giving you control over markup the visual editor cannot expose.

![](https://cdn.document360.io/6a41a4ec-dfe1-4f2d-9818-4fc3e2c85382/Images/Documentation/code%20view.png)

---

## When can you use Code view

- Inject custom HTML elements the visual toolbar doesn't support
- Apply inline styles to specific elements
- Embed FontAwesome or other icon snippets
- Fix unsupported tag errors flagged by the editor
- Add symbols or icons into table cells
- Search within HTML using `Ctrl + F`

---

## Automatic HTML formatting

The editor automatically standardizes indentation and spacing each time you open Code view. This only runs on entry — not on save or publish — and does not affect custom HTML or script blocks.

## Searching in Code view

Use the built-in search to locate specific HTML elements or text within the code.

| Action | Shortcut |
| --- | --- |
| Open search | `Ctrl + F` |
| Next result | `Enter` |
| Previous result | `Shift + Enter` |
| Auto-indent / format code | `Shift + Tab` |

---

## Saving changes

Changes in Code view are not saved automatically. Press `Ctrl + S` before switching back to the visual editor or navigating away.

 NOTE

Unsaved changes in Code view will be lost if you navigate away without clicking **Save**.

---

## Unsupported HTML tags and attributes

The editor flags unsupported HTML tags and attributes instead of removing them, so you can review and correct them.

#### When does this happen?

- When switching an article from the WYSIWYG editor to the Advanced WYSIWYG editor — unsupported content is flagged automatically
- When you add unsupported tags or attributes directly in Code view — the editor flags them on parsing

#### What the editor does

- Detects unsupported tags (e.g., `<marquee>`, `<blink>`) and attributes (e.g., `onmouseover`, `style="text-decoration:blink"`)
- Marks flagged elements with tooltips and block highlights without disrupting surrounding content
- Blocks visual editing of flagged elements until resolved in Code view

 NOTE

Flagged elements can be modified, removed, or corrected directly in Code view.

## Supported tag categories

**Text formatting**

- Abbreviations (`<abbr>`)
- Blockquote (`<blockquote>`)
- Headings (`<h1>`–`<h6>`)
- Paragraph (`<p>`)
- Subscript / Superscript (`<sub>`, `<sup>`)
- Inline code (`<code>`)

**Structure & media**

- Images (`<img>`)
- Links (`<a>`)
- Tables (`<table>`, `<tr>`, `<td>`)
- Lists (`<ul>`, `<ol>`, `<li>`)
- Dividers (`<hr>`)
- Spans and divs with supported attributes

---

## Best practices

- Use Code view only when the visual editor cannot accomplish the task. Direct HTML editing increases the risk of introducing unsupported tags or broken markup.
- Stick to supported tags when writing or pasting HTML. Unsupported tags trigger flags and block visual editing of that section until corrected.
- Use `Shift + Tab` to reformat code after making edits, keeping markup readable and easier to debug.
- Save frequently using `Ctrl + S`, especially before switching modes. There is no auto-save and no recovery for unsaved changes.
- Resolve flagged elements promptly. Leaving them unresolved prevents visual editing of the affected block and can cause unexpected rendering issues on publish.**