Developer tools · HTML WYSIWYG editor
From <font> Tags to CSS: How Web Formatting Moved Out of the Markup
· Background
html css text-cleanup
Recounts how presentational HTML such as font, center and align attributes gave way to CSS, and why that history explains today's inline-style debate in editors.
Presentational HTML in older pages — no date claim is sourced here
Older page fragments often express appearance directly through elements such as font and center or attributes such as bgcolor and align. The workbook attaches a mid-1990s chronology, but no repository source verifies those dates. The implementation can demonstrate only how this editor treats such markup today.
ToolAcre does not allow font or center, and it does not preserve presentation attributes. Ordinary unsupported wrappers are unwrapped, so their visible words may survive while the formatting instruction disappears. That output is a cleaned draft, not a faithful restoration of a legacy page.
font, center and bgcolor: presentation in the tags — describes the elements and attributes browsers added for appearance
When presentation lives in tags and attributes, content and design become difficult to change independently. A color choice repeated across articles must be edited in every fragment, and a centered heading has no inherent structural meaning. Copying those constructs also imports assumptions from an obsolete layout.
Semantic markup names roles such as heading, paragraph, list and quotation. The destination stylesheet can present all occurrences consistently. ToolAcre supports that smaller vocabulary and removes class and style too, leaving the receiving system responsible for its own presentation layer.
CSS separates structure from presentation; standards dates are outside repository evidence
CSS provides selectors and declarations separate from the content tree. That architectural division allows one design change to affect many documents without rewriting each body. This article does not invent a first-recommendation date or standards sequence because such historical claims require external specifications.
The practical rule remains testable: copied fragments from ToolAcre contain no style attributes or class names. The downloaded full document includes ToolAcre’s own wrapper stylesheet, but that CSS is not inserted into the sanitized fragment returned by Copy HTML.
Presentational elements are outside this allowlist, without a living-standard chronology claim
The workbook describes deprecation and removal from a living standard. This module has no standards archive, so the article stops at current policy: presentational elements are unsupported and either unwrapped or removed according to their risk category. It does not make a normative chronology claim.
The removal report is the useful evidence. Paste a font tag around text and observe that the wrapper is rejected while the words remain. Paste a dangerous style container and its body is removed whole, because raw style content can create request and parsing surfaces beyond this editor’s scope.
Inline styles exist elsewhere but this editor removes them
Inline style is a modern syntax mechanism, but ToolAcre declines it completely. Therefore this editor cannot demonstrate a surviving “compromise” style attribute or recommend one of its own output modes. The only self-contained styling appears in the generated preview document around filtered body HTML.
Other contexts, especially email production, may require inline declarations. That requirement calls for a separate pipeline with client testing and CSS policy. Adding arbitrary style here would contradict the current allowlist and expand the sanitizer’s responsibilities without evidence or tests.
Worked example: modernising a 1990s snippet — rewrites font-tag markup as semantic HTML plus a class and compares the two
Modernize `<center><font color="red"><b>Maintenance</b></font></center><p align="left">Tonight</p>` by choosing a real heading and paragraph. ToolAcre unwraps unsupported presentation, maps b to strong, removes align and retains p, but it cannot infer that Maintenance should be h2.
Rewrite the meaning explicitly as `<h2>Maintenance</h2><p>Tonight</p>`, then add approved destination classes or stylesheet rules outside the editor. If importance is intended inside a sentence, strong may be suitable; if bold was merely a font weight, do not retain misleading semantics.
What this does not cover — CSS methodology debates or framework-specific styling
This article does not compare CSS methodologies, frameworks, utility classes or design tokens. It does not claim historical dates for font, CSS or standards transitions. It also does not offer an automated converter that can infer semantic roles from visual legacy markup.
Filtering is not universal XSS prevention. ToolAcre’s hand-written tokenizer is constrained and its preview is separately sandboxed. A server accepting legacy or user-generated HTML needs a maintained parser-based sanitizer, migration tests and a destination-specific allowlist.
Takeaway: know why the rule exists — summarises the history and how inspecting output in ToolAcre's HTML WYSIWYG editor helps keep presentation out of your markup
Know why structure and presentation are separated: meaning should survive redesign, while appearance should be governed consistently. ToolAcre enforces that boundary aggressively by removing both legacy presentation and modern inline or class-based styling from copied fragments.
Use the source view to identify what was lost, then restore semantics manually and style at the destination. This process may not preserve the old look, but it produces content that is easier to review, migrate and adapt without carrying obsolete decisions into every future theme.