Skip to content

Fix organs panel indentation, dead hover box, and nest colon lesion under colon - #260

Merged
aperson30 merged 1 commit into
BodyMaps:mainfrom
aperson30:fix/organ-panel-indent-colon-group
Sep 25, 2026
Merged

aperson30 merged 1 commit into
BodyMaps:mainfrom
aperson30:fix/organ-panel-indent-colon-group

Conversation

@aperson30

Copy link
Copy Markdown
Collaborator

Summary

  • Rows after the Pancreas subgroup in the Organs panel were indented deeper than the Pancreas header, so colon, duodenum, etc. looked like children of Pancreas. Sibling rows and subgroup headers now share one indent; a subgroup's own children sit one level deeper.
  • The empty box that appeared on hover beside each organ did nothing: the spacer next to each row reused the chevron class and inherited its hover background. Replaced with a plain non-interactive spacer (also in Custom Classes).
  • colon_lesion is now nested under a Colon subgroup, following the existing Pancreas and Kidneys pattern (header toggles colon, lesion sits below it).

Test plan

  • npx tsc -b clean
  • npx vitest run 331/331 pass
  • Eyeball the Organs panel in the viewer: Digestive System alignment, Colon group with lesion below, no hover box

…under colon

Rows after the Pancreas subgroup were indented deeper than the Pancreas
header itself, so they read as children of Pancreas. Sibling rows and
subgroup headers now share the same indent, and a subgroup's own children
sit one level deeper.

The blank spacer beside each organ row reused the chevron class, so it
picked up the chevron's hover background and showed an empty box that did
nothing. It is now a plain non-interactive spacer.

colon_lesion is now nested under a Colon subgroup (same pattern as
Pancreas and Kidneys) instead of sitting flat beside colon.
@aperson30
aperson30 merged commit c31ca84 into BodyMaps:main Sep 25, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant