Global `h1`, `h2` etc styles affect devtools styles
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css, react, typescript
Research direction
Start by reproducing the issue in TanStack Devtools v0.7.6 with global h1, h2, and h3 styles, focusing on the drawer title and its existing plugin-title-container-tanstack-query-0 class. Done means the devtools headings remain readable on the dark background despite consumer heading styles; the reported template error is also noted for investigation.
Written by the indexing model from the issue text.
Description
TanStack Devtools version
v0.7.6
Framework/Library version
React v18.3.1
Describe the bug and the steps to reproduce it
We have some global styles on heading elements (don't ask... legacy 😅)
This makes the different panels unreadable on the dark background
(screenshot doesn't do it justice for how it looks "live" for some reason, but it illustrates the point).
The h3 already has a class plugin-title-container-tanstack-query-0, so in theory you should be able to set some light color to it?
If I disable our rule, it inherits the color of its parent
But that's less specific then an h3 rule apparently.
Note that beyond the title in the drawer, none of our other global resets seems to affect the devtools 👍
Btw, the template has a small error:
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
N/A
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
None
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.
- Dominant language
- TypeScript
- Stars
- 499
- Forks
- 100
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TanStack/devtools
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
All issues in TanStack/devtools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·