We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
box-shadow variables have extra commas which make them unusable in box-shadow: $pt-elevation-box-shadow Sass usage
box-shadow: $pt-elevation-box-shadow
$pt-elevation-shadow-0: 0, 0, 0, 1px, rgba(17, 20, 24, 0.15) !default;
they were fine in v4.16.x variables.scss:
$pt-elevation-shadow-0: 0 0 0 1px rgba(17, 20, 24, 0.15) !default;
Caused by #5904, need to look into how we generate CSS variables...
The text was updated successfully, but these errors were encountered:
It seems like the quotes on strings got dropped too.
Before:
$icons16-family: "blueprint-icons-16" !default; $icons20-family: "blueprint-icons-20" !default; $pt-icon-size-standard: 16px !default; $pt-icon-size-large: 20px !default; $pt-font-family: -apple-system, "BlinkMacSystemFont", "Segoe UI", "Roboto", "Oxygen", "Ubuntu", "Cantarell", "Open Sans", "Helvetica Neue", "blueprint-icons-16", sans-serif !default;
After:
$icons16-family: blueprint-icons-16 !default; $icons20-family: blueprint-icons-20 !default; $pt-icon-size-standard: 16px !default; $pt-icon-size-large: 20px !default; $pt-font-family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen, Ubuntu, Cantarell, Open Sans, Helvetica Neue, blueprint-icons-16, sans-serif !default;
Sorry, something went wrong.
Note that these variables are only broken for consumers of the Sass variables, and not internally in Blueprint styles:
adidahiya
Successfully merging a pull request may close this issue.
Environment
Actual behavior
box-shadow variables have extra commas which make them unusable in
box-shadow: $pt-elevation-box-shadow
Sass usageExpected behavior
they were fine in v4.16.x variables.scss:
Possible solution
Caused by #5904, need to look into how we generate CSS variables...
The text was updated successfully, but these errors were encountered: