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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add paper background support to side navigation #4881
Conversation
Demo starting at https://vanilla-framework-4881.demos.haus |
@@ -539,7 +539,7 @@ | |||
.p-side-navigation--raw-html { | |||
@include vf-side-navigation-raw-html-theme-light; | |||
|
|||
&.is-light { | |||
&.is-dark { |
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.
Drive-by: fixed a broken class name when switching from light theme to dark theme in raw HTML variant.
@@ -12,7 +12,7 @@ function generateMetrics(file, metricsArray) { | |||
{ | |||
name: 'Stylesheet size', | |||
benchmark: 150000, | |||
threshold: 380000, | |||
threshold: 430000, |
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.
Adding more themes to side navigation increases the size of CSS noticeably.
It's OK, because in the end this additional CSS is quite repetitive and will GZIP nicely, so doesn't affect performance too much.
But we need to increase our allowed thresholds so that the tests pass.
@bartaz Looks like the second one (with icons) has a transparent background on mobile |
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.
LGTM 馃憤
Done
As part one building block of new documentation layout this PR updates side navigation component by adding new paper background colour support to the light theme.
QA
Check if PR is ready for release
If this PR contains Vanilla SCSS code changes, it should contain the following changes to make sure it's ready for the release:
Feature 馃巵
,Breaking Change 馃挘
,Bug 馃悰
,Documentation 馃摑
,Maintenance 馃敤
.package.json
should be updated relative to the most recent release, following semver convention: