Fix raw HTML in Google Calendar event descriptions - #2193
Open
martin-forge wants to merge 2 commits into
Open
Conversation
Google Calendar descriptions may contain HTML, but TaskNotes uses them as plain text across event details, copied content, generated notes, and folder templates. Normalize them at the Google provider boundary while preserving paragraphs, lists, and link targets. Leave plain-text descriptions unchanged.
martin-forge
changed the title
The module only wires the Google provider boundary; ICS subscriptions read descriptions through their own path and are not normalized here.
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
1 participant
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.
Problem
Google Calendar descriptions may contain HTML. TaskNotes treated the field as plain text, so users could see literal tags in event details, copied text, and generated notes.
Fix and benefit
Normalize descriptions once at the Google provider boundary using the Obsidian HTML sanitizer. Paragraphs, lists, and link destinations stay readable everywhere TaskNotes uses the description, while existing plain text—including angle-bracketed email addresses and placeholders—remains unchanged.
This complements #1882, which fixed TaskNotes-to-Google export; this PR fixes Google-to-TaskNotes input.
Validation