Skip to content

fix(docker): prevent inspector from covering Logs and Exec - #137

Merged
jhd3197 merged 1 commit into
jhd3197:devfrom
JRebertt:fix/docker-inspector-action-layers
Sep 8, 2026
Merged

fix(docker): prevent inspector from covering Logs and Exec#137
jhd3197 merged 1 commit into
jhd3197:devfrom
JRebertt:fix/docker-inspector-action-layers

Conversation

@JRebertt

@JRebertt JRebertt commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Summary

  • close the container inspector in the same state transition that opens Logs or Exec
  • share the transition handlers between row actions and inspector actions
  • prevent the inspector's Docker-specific layer from covering the shared Drawer and Dialog portals

Why

The inspector uses a higher stacking layer than the shared Logs drawer and Exec dialog. Both actions mounted successfully, but Logs was fully hidden and Exec was partially covered. Removing the inspector before mounting the destination surface avoids nested overlays without changing global z-index behavior.

Tests

  • npm test — 163 passed
  • targeted ESLint — no errors
  • npm run build — passed
  • manually verified that Logs and Exec open unobstructed from the container inspector

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.

2 participants