fix: Update CSS rules for GT tables in dark mode#235
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PR addresses GT tables losing their styling in the docs because global element-level theme rules bleed into the self-contained gt table. For example, in dark mode
p/codetext turned light-gray and amber-on-dark, and in both modes thep { font-family }rule overrode the report title's font (gt wraps the title in a<p>) while leaving the rest of the table on its own font. This adds.gt_table-scopedexemptions that handcolor,background-color, andfont-familyback to gt's own cascade, so gt tables render identically and correctly in light and dark mode.