-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: Update detour list page and table styles for mobile #2774
Conversation
assets/css/utilities/_hideable.scss
Outdated
@@ -11,7 +11,7 @@ | |||
} | |||
|
|||
.u-hide-for-mobile { | |||
@media screen and (max-width: map-get($breakpoints, "max-mobile-landscape-tablet-portrait-width")) { | |||
@include media-breakpoint-down(md) { |
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.
@mbta/skate-developers want to surface this change. It's not a huge change, but this changes the "hide for mobile" breakpoint from 800px to 768px.
I did this because media-breakpoint-...
uses bootstrap's breakpoints, and I wanted to bias towards bootstrap's breakpoints rather than our own _skate_ui
ones, especially since we want to stop "caring about what's in _skate_ui", per this Slack Convo.
If you'd all prefer, I can split it out into a separate PR. Or ditch this and find a different way to keep our breakpoints consistent!
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.
Btw I found the variable we need to update if we do want to make bootstrap use our breakpoints as a temporary measure https://github.com/twbs/bootstrap/blob/main/scss/_variables.scss#L483-L492
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.
@firestack Amazing, thank you!
What do you think of this?
And at this point, should the _variable_overrides
change and this one be split to a separate PR, do you think?
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.
And at this point, should the
_variable_overrides
change and this one be split to a separate PR, do you think?
I'm good either way 👍🏻
What do you think of this?
Looks good, I don't think you need !default
? Did you try it without that? AFAIK bootstrap has that in their config so that we can override it easily.
Maybe it also should document why these values are set like this, because right now we're doing this to be compatible with the old breakpoints "system", but I don't know what design will want to do with breakpoints in the future.
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 think I do want to split this out into two PR's.
Coverage of commit
|
76c6374
to
b4ba629
Compare
Coverage of commit
|
Coverage of commit
|
Coverage of commit
|
Coverage of commit
|
7fca2cf
to
8efa5ed
Compare
Coverage of commit
|
Coverage of commit
|
Coverage of commit
|
8efa5ed
to
b30b0d0
Compare
Coverage of commit
|
Desktop
Tablet Portrait
Mobile
Asana Ticket: https://app.asana.com/0/1205385723132845/1208226797938041/f
Depends on: