-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add narrow/regular/wide viewport range utilities #1995
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
624a729
Add viewport range utilities
vdepizzol fdc5fab
Add comment about wide viewport range size
vdepizzol f6266a7
Stylelint auto-fixes
actions-user 0c5fc7e
Create proud-donkeys-happen.md
langermank 6df8aeb
Add support for `.show-whenRegular.hide-whenWide`
vdepizzol 54d0101
Merge branch 'viewport-range-utilities' of https://github.com/primer/…
vdepizzol 6314d8d
Merge branch 'main' into viewport-range-utilities
vdepizzol File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
"@primer/css": patch | ||
--- | ||
|
||
Add narrow/regular/wide viewport range utilities |
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something I'm wondering... should this be limited to
so that these utilities only kick in when between the
$width-md
and$width-xl
breakpoint and not from$width-md
upwards.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@simurai That's in fact how we're considering our viewport ranges to go. Take a look at https://github.com/github/primer/issues/580#issuecomment-1076890831 to see the media queries we're proposing. You can also see a visual of these breakpoint/viewport considerations here in this Figma frame. (only available for hubbers) 😁
The idea is for
Narrow
to wrap all "mobile"-friendly design patterns, andRegular
all the "desktop"-friendly ones, including wider scenarios. TheWide
viewport range in that case is a subset ofRegular
, applied on top of it.✌️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@simurai your comment made me thing of a scenario I haven't considered: when some area needs visibility on
Regular
but not onWide
scenarios.I think we can support it like this:
I've played with CSS specificities (in a way that doesn't try to reinvent the wheel in regards to the use of
!important
in our Primer CSS utilities) in this prototype, and have updated the PR accordingly.Thank you! 🙇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see.
Narrow
is a range (0 - 768), butRegular
andWide
behave more like "breakpoints" (from ... to infinity).Ok, yeah.. that is probably safer and you don't have to remember to add both
Regular
andWide
. 👍