-
Notifications
You must be signed in to change notification settings - Fork 35
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
Site header notification border when removing it #3635
Comments
Hello @dhamaris, when you don't have a notification in your site header you shouldn't have its wrapper div as well. |
Hello @planctus, I cannot see the button close on the playground so I cannot reproduce it there: However, when debugging I only see the this.element being deleted (the one with class ecl-notification) Here, this.element is the third div on the following snippet, so the first and second one do not get deleted.
Am I looking at the right spot? Please let me know if there is something I am missing here. |
Hi @dhamaris, i completely misunderstood the issue initially, you are right that we have styles set on the container but we only remove the notification element on close. Concerning the current version, you can try in the dev branch where we enabled the close button in the site header notification: https://v4-dev--europa-component-library.netlify.app/playground/ec/?path=/story/components-site-wide-site-header--standardised&args=show_notification:!true;show_menu:menu&globals=viewport:responsive We will fix this, but the fix will be on top of 4.7.0, please review your implementation of the site header, you can see that the notification element should be above the site name container and not below it. |
Ok @planctus, sorry for not stating the version I was using at the beginning, I am using the 4.6. |
Expected behavior
Hello, site header notification works very well:
The only things is, when removing it, a line remains:
It seems it is the border-top on this css:
I would overwrite it but wanted to ask you if it is necessary, or if the line is intended.
Thanks a lot
The text was updated successfully, but these errors were encountered: