You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
When I create a React project using Yeoman, if I use OfficeHelpers.UI.notify to show an error, or for anything, the MessageBar has no background. This occurs even with the out of the box project (with the small change of changing 'range.format.fill.color = 'yellow'' to 'range.format.fill.color = null' so that there is an error to show).
Here's a picture of what happens. As you can see, the OfficeHelpers.UI.notify MessageBar displaying the "RichApi.Error" has no background:
I'm not really sure if this is the right place to post this, as I'm sure it could be a bug with office-generator or office-fabric-ui-react, but since it was the notify function that appeared bugged, I thought it'd be a good idea to start here.
The text was updated successfully, but these errors were encountered:
I am also experiencing the same issue, I've noticed the body font isn't being set to Segoe UI either. The issue appears to be related to the Fabric UI package not getting loaded correctly.
Environment Information
Bug Information:
When I create a React project using Yeoman, if I use OfficeHelpers.UI.notify to show an error, or for anything, the MessageBar has no background. This occurs even with the out of the box project (with the small change of changing 'range.format.fill.color = 'yellow'' to 'range.format.fill.color = null' so that there is an error to show).
Here's a picture of what happens. As you can see, the OfficeHelpers.UI.notify MessageBar displaying the "RichApi.Error" has no background:
I'm not really sure if this is the right place to post this, as I'm sure it could be a bug with office-generator or office-fabric-ui-react, but since it was the notify function that appeared bugged, I thought it'd be a good idea to start here.
The text was updated successfully, but these errors were encountered: