fix(source): retain syntax highlighting after pointer hover and focus changes #27
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: KofTwentyTwo/MarkdownViewr.Windows#27
Reference in new issue
Block a user
Owner-reported regression
When the Markdown source first loads, syntax highlighting appears. Moving the mouse over the source pane removes the highlighting, and it does not return. The owner expects highlighting to remain active.
Reproduction
This is an owner report, not a locally reproduced or diagnosed result.
Acceptance
Related: #16, #10, #1. Recorded during paused owner review; implementation and runtime reproduction/acceptance pending.
Substantial AI assistance: Codex (GPT-6).
Pushed signed/DCO implementation
0eb3a0eto draft PR #3. Current local gates: zero-warning Release,582 core tests/100% measured lines,25 adapter tests, formatting and self-contained publish. Current native/published/installed acceptance is now queued in hosted CI; no current runtime or production-signing claim.Native Settings pages/defaults, labeled toolbar, loaded-snapshot footer, disabled-editor explanation and open-source About changes are implemented. Source-hover regression remains unresolved and has an actual native pointer/color acceptance case. Default-file registration/routing is implemented with five passing isolated registry tests; actual installed chooser/Explorer lifecycle remains pending. Do not close affected issues before actual acceptance. Full stable1.0/dev goal remains active.
Exact hosted0eb3a0e / CI38164841448 reproduced this issue: heading text initially has native foreground#75628B and changes to#000000 after actual pointer entry, before focus/selection. Native result72/97 passes with25 failures and no skips; published acceptance times out at600seconds. Logs and runtime artifacts are retained locally.
Ranked hypotheses: native whole-document hover foreground; focus/selection reset; async repaint cancellation. Installed WinUI2.3.9 generic.xaml confirms PointerOver/Focused/Disabled storyboards target ContentElement.Foreground. Signed/DCO0ed608e tests hypothesis1 by removing only those foreground animations while keeping native chrome/accessibility/scroll and semantic ranges. Added a focused hosted pointer/color regression with retained TRX alongside full acceptance. New CI is queued; this is a candidate, not a verified fix. No local desktop input or failed assertions bypassed.
The exact native hover regression now passes on signed commit0ed608e, CI38166230860, in both the focused job and full native run. The retained focused TRX confirms actual source token foreground colors survive pointer hover, focus and selection; the original failure changed the heading color from#75628B to#000000 immediately after pointer movement.
The fix removes only WinUI RichEditBox template foreground assignments targeting ContentElement, preserving native border/focus/scroll behavior and actual native token formatting. Focused evidence is retained locally in artifacts/source-hover-38166230860 and as source-hover-results in CI38166230860.
Full native acceptance is74/97 with23 failures and zero skips; published/installed acceptance remains incomplete. Commit05bf612 expands focused checks and retains exact pane/scroller/glyph evidence without skipping or relaxing assertions. Keep the issue open until current distributed source behavior also passes.
Current native evidence is
8abbd4d/CI38168946288: full93/97 and focused10/12,zero skips. Physical source hover passes both runs; full palette passes, while focused initial Light palette records actual#1F1F1F versus expected#75628B before pointer input. Published also reproduces that initial-color variant. This is not unconditional highlighting acceptance.Signed/DCO
9fdfc2duses WinUI's real native Toggle menu action instead of focus-sensitive mouse fallback; the unchanged physical hover/focus/selection and exact foreground assertions remain. Source reopening/50:50 and focus-scroll alignment remain required. Exact-head CI38170170551 is running; no installed or current-head success claim. All source regressions remain in the required focused gate.Signed/DCO
2fe5853,efe14afanddbda6d4are pushed to PR#3. Exact-head CI38171433458 is running.The current native pipe fix has actual red/green evidence: defer the real server continuation until its same-user client closes; the unfixed next ConnectAsync times out10seconds. Release accepted native connections even after a broken read clears IsConnected. Four cases plus25runs/100tests now pass locally, with zero failures/skips. No deadline/retry/assertion was relaxed.
Prior9fdfc2d focused14/15 passes source reopening, four-file import and heading commands; full native and published are93/97,4failures,zero skips. They reproduce pipe disconnection, initial source color, nested outline and source focus variants. Published now completes inside the original600second bound, but red tests prevent installed outcomes. These full variants are not superseded by focused passes.
Queued post-theme source repaint and numeric test-only focus diagnostics address the remaining source investigation; the tagged probe must be removed after diagnosis. All observed cases remain in the required focused gate. Local Release/format/55 script tests/both analyzer partitions pass. Owner preview55472 stays responsive and untouched. Production signatures, current-head human review and final stable1.0/dev publication remain pending.
Current signed head
04c1da8is pushed. Exact previousdbda6d4still fails the initial Light source palette after verified UIA ThemeLight toggling: expected #75628B, actual #1F1F1F. The queued repaint did not fix it; physical hover passes in that focused run but does not prove all source colors correct. New opt-in probes capture actual native range/foreground colors before/after painting and after the native queue, with no document text or paths. Original actual-color assertions remain. Local zero-warning Release/format/hooks pass; current Windows evidence: https://github.com/KofTwentyTwo/MarkdownViewr.Windows/actions/runs/38172448726. Keep this issue open until distributed behavior is proven and temporary probes are removed.Published04c1da8 evidence confirms the root color race: snapshot1/paint3/six tokens unchanged; native heading #75628B at paint completion20:37:33.320 becomes #1F1F1F after native queue20:37:33.389. The initial hover fixture shows the same reset before pointer input. Classification completed correctly; native property propagation replaces the painted ranges. Signed local5fa6754 now waits for the owned low-priority dispatcher boundary after control brushes change, then formats real native ranges with stale/disposal guards. Zero-warning Release, format and hooks pass. Hosted proof is pending; do not claim resolved. Pushed91877f7 current CI38173447118 is kept intact before the next push. Temporary probes must be removed before release.
Signed
9994edais pushed; exact CI38176727468 is now running native, focused and published/installed acceptance. Previous exact6374611 is terminal: focused19/20, full native97/98 and published97/98, zero skips. Actual sustained colors/physical hover/focus and outline pass both full variants. The remaining source test advances to line490: source middle glyph aligns but the reader heading stays offscreen.The correction uses full native content-client offscreen character points and stops adding the scroll offset twice. Original physical bidirectional assertions, deadlines and bounds are unchanged. Bounded temporary numeric probes compare anchors/targets; they must be removed before release. Local zero-warning Release, formatting and signed/DCO hooks pass. Hosted proof of the correction and installed acceptance remain pending; no stable1.0/dev publication claim.