fix(app): disable Markdown tables after Android layout failure #71
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/01a158a9-disable-tables"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Morten’s v0.50.0 Android test found that tables break the view. Disable table parsing across Android and web and remove the custom table layout; pipe-table syntax becomes ordinary selectable paragraph text. Stored Markdown and all other rendering/editing behavior are preserved.
pipe-table source → shared parser (tables disabled) → existing themed paragraphEvidence
task ci:qualitypasses (868 tests, 129 files), app/E2E type checks and focused ESLint pass. All 8 phone/desktop browser checks pass, including fallback on description/activity/conversation, saved-source preservation and existing interactions. Before/after screenshots are attached to the task. Branch #486 and PR #487 are fully green, including docs and both image builds.Merge danger
Door: two-way. Reverting restores table support; no schema or stored Markdown changes.
Blast radius: app.
Rollback and verification
Owner self-review:
0a778c9against57a858b, plus subsequent browser-fixture corrections. Standards: zero findings. Spec: zero findings. Parallel checks confirmed the supported table parser toggle and removal of custom table rules preserve existing shared rendering, source and checkbox behavior. Browser fixtures now match the entire selectable pipe paragraph, check fallback in description/activity/conversation, use distinct per-viewport message labels and read selection atomically to avoid test collisions. Source regression was red before and green after. Actual Android fallback is pending Morten’s patched-APK test under existing release approval. Verify expected release digests/revision and deployed web fallback; rollback via compatible revert release without source/schema changes.