-
Notifications
You must be signed in to change notification settings - Fork 28
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
Notification renders double close button #65
Comments
Can you open a PR to remove in the config file? |
Also, looks like this is only an issue when using the FontAwesomeIcon component to render the icons. |
@groundfloorwebb I'm running the demo project and it looks ok without any changes... (using SVG or CSS mode) Can you reproduce it on codepen or similar? |
Well looks like the real issue was i was including a snippet of buefy css leftover from the previous version of our design system. With that code removed the icon is still rendered but has a size of 0px, just like the example code. I feel silly, but the good news is this resolved another strange issue as well. |
First off, great library, keep up the good work!
I'm using @oruga-ui/oruga-next 0.5.6 and @oruga-ui/theme-bulma 0.2.7 in a Vue 3 app with fontawesome. When I open a notification like this
oruga creates a notification with a double close button like this
This issue is theme applies bulma's
delete
class to the close element (creating the circular close button using css) and also generates an icon using the default value of thecloseIcon
prop in the component. I was able to get around this problem by passing an empty string for closeIcon in my config like this:I would recommend making this a part of the theme for a smoother dev experience.
The text was updated successfully, but these errors were encountered: