feat: render safe raw HTML in the editor - #493
Merged
Merged
Conversation
Azganoth
force-pushed
the
feature/safe-raw-html
branch
from
September 22, 2026 00:10
1097d02 to
f8913a9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Related Issue
Closes #62
Verification
pnpm exec vitest run src/features/editor/utils/safeHtml.test.ts src/features/editor/tests/sourceProjectionHtml.test.ts src/features/editor/tests/htmlSafety.test.tsx src/features/editor/tests/editorPresentation.test.tsverifies the render predicate, security fallback, exact source-position mapping, projection behavior, and presentation rules.pnpm check:frontendverifies formatting, TypeScript, lint, the production build, and the complete frontend test suite with coverage.Not verified: the desktop E2E suite was not run locally; CI will exercise the updated WebView scenario.
Notes
The source-located parse constructs the validated DOM through element and text-node primitives instead of adopting a browser-parsed template. This differs mechanically from the spike prototype while retaining its security boundary: no HTML string is reparsed into the document and rejected trees are never partially sanitized. Retained source locations provide exact rendered-click mapping back to authored offsets.