Skip to content

Incorrect interaction with html dialog #369

Description

@andresdsep

TanStack Devtools version

v0.9.9

Framework/Library version

React 19.2.3

Describe the bug and the steps to reproduce it

Devtools does not interact well with Html's dialog element.

A dialog anywhere in the DOM will take precedence in the element stack, regardless of z-index. This means that when a dialog is open, both the trigger and panel of the devtools will become inaccessible.

Image

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

Render a <dialog open>Something</dialog> in a page with devtools and devtools can no longer be interacted with.

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

No, because I do not know how

Terms & Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Activity

  1. github-actions commented on Mar 5, 2026

    @github-actions
    Contributor

    Thanks for filing this issue! The bug description is clear — <dialog> elements creating a top layer that blocks interaction with the devtools panel makes sense.

    However, the Minimal, Reproducible Example field requires a link to a runnable sandbox (e.g. CodeSandbox, StackBlitz), not a text description. Could you provide one? You can fork one of the official examples and add a <dialog open> to demonstrate the problem.

    A working reproduction will help the maintainers investigate and fix this much faster. Thanks!

  2. harry-whorlow commented on Mar 19, 2026

    @harry-whorlow
    Collaborator

    Hi @andresdsep, do you have any suggestions on how we should fix this? if we exposed an zIndex prop allowing you to modify the zIndex, would that solve it?

  3. andresdsep commented on Mar 19, 2026

    @andresdsep
    Author

    As I mentioned, dialog supercedes z-index, so that wouldn't help. In my view, the only way to work with dialog would be for devtools to render a dialog itself.

    Perhaps it could do so on an "opt-in" basis. So an optional prop on TanStackDevtools like renderAsDialog, so a consumer isn't forced into this newer API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions