-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fix(PortalCompatProvider): support custom ID prefixes in themeClassName #28551
fix(PortalCompatProvider): support custom ID prefixes in themeClassName #28551
Conversation
Asset size changes
Baseline commit: beef7217f6b332ce3339e81d5448135d9142c495 (build) |
📊 Bundle size report
🤖 This report was generated against beef7217f6b332ce3339e81d5448135d9142c495 |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 1562100:
|
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 ❤️
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
Previous Behavior
When a custom ID prefix is set via
IdPrefixProvider
, the resulting theme class name is not picked up byPortalCompatProvider
and so v9 CSS variables are not available in v8 portals. This is due the current regex in the component that only picks upfui-FluentProviderXXX
part and not a possible prefix.New Behavior
A regex that is used to pick a class name from a list of class names in
themeClassName
is updated to include a prefix into a caption group if the prefix exists.Related Issue(s)