Repository navigation
feat(observatory): show radar marker details on focus and hover - #908
Merged
Merged
Conversation
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.
Problem and behavior
Radar marker details were available through a native
titlepopup, which did not give keyboard focus the same persistent, inspectable view as pointer hover. A static localized tooltip now shows the current product name, process count and risk on hover or focus. It updates when telemetry changes and dismisses on Escape, blur, pointer exit, removal and page changes.Focus and hover are tracked independently: when a pointer leaves a different marker, the focused marker’s details return unless Escape explicitly dismissed them. The tooltip sits behind marker hit targets, so a long name cannot block a neighboring marker. Marker risk positions, 44px targets, zoom, selection, host grouping and shared-file lines remain intact. No data-dependent motion is added.
Verification
frontend:check, completefrontend:test, scoped lint/format and browser checks passed. A follow-up fixture-only commit repaired seven hosted TypeScript fixture errors; roottypecheck:svelte, roottypecheck, two focused tooltip tests, and scoped lint/format passed locally, with independent GPT-6.1 Sol GO.memory-bank/architecture.md; that declaration was updated from 88 to 89,counts:checknow passes 69/69 declarations, and independent GPT-6.1 Sol review gave GO. Rebase preserved the exact reviewed patch ID; final re-review GO.This advances issue #24 but does not resolve its appearance-transition/design conflict or establish native Electron qualification. Five hosted exact-head CI contexts are required before merge.