Repository navigation
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Related reports: #12 covers general HTML support, and I have previously contributed to it and to discussion #949. This report adds specific 1.12.1 reproduction evidence for widget and notification surfaces and links a prepared implementation.
Affected app version
1.12.1 (version code 24). The original official APK was tested on an emulator; it was re-signed with a disposable test key to allow same-key comparisons with the patched APK. The original APK SHA-256 was dae815ce83285facf9fd8648b8c4f039700d95126325db124521eba479b270ba.
Affected Android/Custom ROM version
Android 15, ARM64 emulator.
Affected device model
Android SDK built for arm64 (emulator). The model of the physical device used for the original Outlook observation was not recorded.
How did you install the app?
GitHub releases: official 1.12.1 APK, re-signed for the disposable emulator test.
Which calendar service or provider do you use, if any?
The original report involved an Outlook/Microsoft Exchange event. The reproducible emulator fixtures use synthetic offline event data and do not connect to a calendar service.
Which sync adapter app do you use for calendar synchronization, if any?
Not applicable to the offline emulator fixture. The sync adapter used for the original Outlook observation was not recorded.
Steps to reproduce the bug
-
Use Fossify Calendar 1.12.1 and create or load an event whose description contains HTML, for example:
<html><body><p>Hello <b>world</b></p><p>Second line</p></body></html>
-
Open the event and inspect its description.
-
When the event description is configured to appear in the event-list widget and in a reminder, inspect those surfaces as well.
The original APK was tested using synthetic events on Android 15. The widget comparison renders Calendar's actual RemoteViews in a test container; the notification comparison captures an actual notification posted by Calendar in the Android notification shade. The test invokes the relevant app code directly; it does not claim a fully manual launcher-widget or scheduled-reminder reproduction.
An Outlook/Exchange-synchronized description observed separately contained a complete HTML document with Microsoft Exchange metadata and a PlainText section. That observation predates the emulator fixture; its app version, device model and sync-adapter route were not recorded. A live Outlook server round trip remains unverified.
Expected behavior
HTML descriptions should be readable in event details, the widget and reminder notifications. Paragraphs, line breaks and links should remain meaningful where the surface permits them. Ordinary plain-text descriptions should keep their existing behavior.
The original synchronized HTML, including surrounding whitespace, should be preserved when editing another event field. A way to inspect or explicitly edit the source would allow the original content to be changed intentionally.
Actual behavior
On the original 1.12.1 APK, HTML markup appears as literal text in the event editor. The original widget RemoteViews and posted reminder notification likewise contain raw tags in the synthetic fixture, making the actual description harder to read. Calendar event lists are another relevant description surface and should be considered when fixing the same underlying rendering problem.
Screenshots/Screen recordings
These matched Android 15 emulator captures use the same synthetic event and the official Calendar 1.12.1 APK before and after a separate Morphe APK patch. The after images do not show the native contributor-fork implementation.
| Surface | Original 1.12.1 | With Penguin patch |
|---|---|---|
| Widget RemoteViews rendered in a test container | Before | After |
| Notification shade | Before | After |
Capture provenance, APK hashes and test details.
The following separate editor comparison shows the native contributor-fork implementation, using a synthetic Exchange-style event:
| Before | Native implementation |
|---|---|
![]() |
![]() |
Additional information
- Related existing report: HTML support #12 (general HTML support). Related discussions: #949 and #465. The Outlook-specific HTML in Outlook calendars not being rendered #975 was marked as a duplicate of HTML support #12. My earlier issue HTML descriptions appear as raw markup in event details, widgets and reminders #1364 was automatically closed because it did not use the required issue template. That issue contains DavidBevi’s request for the contribution to be considered. This report adds a reproducible 1.12.1 fixture and concrete widget and notification evidence to the same underlying HTML rendering problem.
- Prepared native source implementation in my contributor fork: pengusto/Calendar#1. It proposes a native description preview, readable summaries and explicit source editing, while preserving unchanged source. It is not an upstream PR. The fork PR documents its own build and tests; they are separate from the APK-patch captures above. It would need a current review before any upstream submission.
- The native fork PR reports a passing build, Android Lint and Detekt, plus 25 Android instrumentation tests on Android 15 ARM64. Themes, 200% font-scale description readability and loaded-activity rotation were inspected; immediate startup/configuration races remain unverified. These tests concern the source implementation, not the APK patch.
- Independent workaround: Penguin Patches v1.6.4, patch Readable Calendar descriptions, for the official 1.12.0 and 1.12.1 APKs. The patch was tested with Morphe Manager on an Android 15 emulator. It is not an official Fossify release or a substitute for the proposed native fix.
- The original 1.12.1 APK and the Manager-exported patched APK were checked using offline synthetic event data. The patched APK passed 34 HTML/editor/widget/notification checks; the original passed 29 baseline checks. The checks include source preservation on title-only save and explicit source edits. No physical-device test or end-to-end Outlook/CalDAV synchronization test is claimed.
- I would welcome maintainer feedback on whether the prepared approach is suitable and whether the new cross-surface evidence and prepared implementation can be considered here alongside HTML support #12. I have not submitted an upstream PR while the relevant issue lacks the required
help wantedlabel.


Activity
fossifybot commentedon Nov 4, 2026
Please open a new issue using the appropriate issue form and keep its required sections and labels intact. If your GitHub client does not support issue forms, please use a web browser.