[docs-infra] Avoid redundant header in print#4832
Open
oliviertassinari wants to merge 1 commit into
Open
Conversation
commit: |
Bundle size
PerformanceTotal duration: 1,049.93 ms -42.23 ms(-3.9%) | Renders: 50 (+0) | Paint: 1,595.79 ms -67.99 ms(-4.1%) No significant changes — details Check out the code infra dashboard for more information about this PR. |
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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 problem
This improves a bit the print UX. Currently, the header shows on each print page.
https://base-ui.com/react/components/checkbox
This is redundant information; to do it "right" we only need the header once on the first page. For example, websites optimized for print don't have this.
Why
The print mode still has use cases in 2026:
So we want our components to have some level of support for print.
So we need the docs-infra environment to allow us to test the print mode of the different components without getting too much in the way.
How much level of support we need is unclear, but here is a quick wins 😁