Handle prose that looks like code in the Content Editor

Release notes

Problem to solve

The Content Editor removes text that looks like code. It is currently impossible to write <this> (without the backticks) in the editor. It shows up while editing but the act of saving the page removes anything that appears to be wrapped in code brackets.

Proposal

Allow the writing of special characters in the content editor. < followed by a word, then a trailing > should be considered raw text unless it is clearly meant to be inline HTML.

Details

clearly meant to be inline HTML

This is the hard part. What does that mean? Should all HTML need to have an end tag to be parsed as such? Is there a case where shorthand or invalid HTML is actually meant to be written inline? For example <img src="#" /> is valid, but not closed.

We shouldn't require anyone to know that they have to escape special characters, but in the absence of that intent, how do we determine whether the code is part of the raw text rather than inline styling? We could go the other way and require inline styling to be something handled by intentionally triggering an HTML tag.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.