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
[ x ] Enhancement
[ ] Bug
[ ] Question
Please specify what version of the library you are using: [ 1.12.0 ]
Can we add support to section backgrounds font color for WebPartTitle ?
Probably need user to optionally add a themeVariant object into the component optionally, and if themeVariant object exist we use themeVariant.semanticColor.bodyText https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/supporting-section-backgrounds
themeVariant
themeVariant.semanticColor.bodyText
The text was updated successfully, but these errors were encountered:
Hi @estruyf - this sounds like a useful enhancement to make. I'd be happy to pick this up as my first contribution to this project, any thoughts?
Sorry, something went wrong.
The PR from @mpowney just got merged, and this change will be available in version 1.14.0.
1.14.0
If you want, you can already test it out via installing the latest beta version. More information about how to install a beta version can be found here: https://sharepoint.github.io/sp-dev-fx-controls-react/beta/
This is now included within the 1.14.0 release
No branches or pull requests
Category
[ x ] Enhancement
[ ] Bug
[ ] Question
Version
Please specify what version of the library you are using: [ 1.12.0 ]
Can we add support to section backgrounds font color for WebPartTitle ?
Probably need user to optionally add a
themeVariant
object into the component optionally, and if themeVariant object exist we usethemeVariant.semanticColor.bodyText
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/supporting-section-backgrounds
The text was updated successfully, but these errors were encountered: