-
Notifications
You must be signed in to change notification settings - Fork 78
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
Modal css fixes #3429
Modal css fixes #3429
Conversation
* Use css reset for margins * Move css import statement to Overlay component
Passing run #2355 ↗︎Details:
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
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.
This looks great to me, thanks. The only issue here is the use of Inter
which isn't a standard browser font...
Assuming y'all figure out something for that, let's merge this in
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.
Thanks 👍
Closes #3423
Code Changes
Steps to Confirm
Pre-Merge Checklist
CHANGELOG.md
Description Of Changes
Chrome:
Firefox:
Safari:
Note that the borders are straight because we only have the full width version of the banner right now. We haven't implemented break points for the banner yet, but when it gets smaller, the border should start to curve (see this slack convo)
A note on CSS resets:
Apps can normally do something like
We can't do that, or else we might mess up the host app's CSS! we could do
but that's nested CSS so isn't widely supported. the usual conversion of
doesn't quite work because of CSS specificity rules I haven't quite wrapped my head around. It does apply that
margin:0
, but then our subsequent css doesn't overwrite it properly. I opted not to look into this too much, but we may want to consider adding a css reset to our fides demo page so that styling issues like this don't come up again (assuming we develop against the demo page)