Promotes .v-tooltip > .v-overlay__content's background and color to !important so the override beats Vuetify's default regardless of CSS chunk order in production builds.
Tightens the file's header comment so the (now-disproven) "source order wins" claim isn't carried forward.
Why
PR #33's 104cac5 introduced the tooltip-readability fix, but on the deployed :latest it still rendered light-on-light. Both selectors (.v-tooltip > .v-overlay__content) are tied at specificity, and the override relied on app.css being imported after vuetify/styles in main.js. Vite's production bundler reorders CSS chunks from node_modules into the final stylesheet unpredictably, so source-order ties aren't reliable. !important on the two contrast properties is the targeted fix; cosmetic border + shadow stay un-important since Vuetify doesn't set them.
Test plan
After :latest rebuilds and compose restarts, hover any v-tooltip (e.g., the "Check all sources" rerun button in Subscriptions → Subscriptions). Background should be slate (#2C313A); text should be parchment (#E8E4D8). DevTools → Computed should show the rule has !important and is the winning declaration.
## Summary
- Promotes `.v-tooltip > .v-overlay__content`'s `background` and `color` to `!important` so the override beats Vuetify's default regardless of CSS chunk order in production builds.
- Tightens the file's header comment so the (now-disproven) "source order wins" claim isn't carried forward.
## Why
PR #33's `104cac5` introduced the tooltip-readability fix, but on the deployed `:latest` it still rendered light-on-light. Both selectors (`.v-tooltip > .v-overlay__content`) are tied at specificity, and the override relied on `app.css` being imported after `vuetify/styles` in `main.js`. Vite's production bundler reorders CSS chunks from `node_modules` into the final stylesheet unpredictably, so source-order ties aren't reliable. `!important` on the two contrast properties is the targeted fix; cosmetic border + shadow stay un-important since Vuetify doesn't set them.
## Test plan
- [ ] After `:latest` rebuilds and compose restarts, hover any v-tooltip (e.g., the "Check all sources" rerun button in Subscriptions → Subscriptions). Background should be slate (#2C313A); text should be parchment (#E8E4D8). DevTools → Computed should show the rule has `!important` and is the winning declaration.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
.v-tooltip > .v-overlay__content'sbackgroundandcolorto!importantso the override beats Vuetify's default regardless of CSS chunk order in production builds.Why
PR #33's
104cac5introduced the tooltip-readability fix, but on the deployed:latestit still rendered light-on-light. Both selectors (.v-tooltip > .v-overlay__content) are tied at specificity, and the override relied onapp.cssbeing imported aftervuetify/stylesinmain.js. Vite's production bundler reorders CSS chunks fromnode_modulesinto the final stylesheet unpredictably, so source-order ties aren't reliable.!importanton the two contrast properties is the targeted fix; cosmetic border + shadow stay un-important since Vuetify doesn't set them.Test plan
:latestrebuilds and compose restarts, hover any v-tooltip (e.g., the "Check all sources" rerun button in Subscriptions → Subscriptions). Background should be slate (#2C313A); text should be parchment (#E8E4D8). DevTools → Computed should show the rule has!importantand is the winning declaration.🤖 Generated with Claude Code