Skip to content
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

Fixed Toast notifications not having background blur. #34968

Closed
wants to merge 1 commit into from
Closed

Fixed Toast notifications not having background blur. #34968

wants to merge 1 commit into from

Conversation

pricop
Copy link

@pricop pricop commented Sep 14, 2021

Hello guys,

I believe the background blur from Toasts was mistakenly removed. The background blur on toasts was available up until bootstrap 4.5.0, in v4.5.1 there were some changes, in which it seems that the background blur got removed.

The Bootstrap Documentation for v4.6.0 also mentions that there's an attempt to blur the background under the Toast but there's no such code to do it: https://getbootstrap.com/docs/4.6/components/toasts/#translucent

I've noticed this now that we've upgraded to the latest stable 4.6.x version and it looks yuck 😅.

Thank you.

Hello guys,

I believe the background blur from Toasts was mistakenly removed. The background blur on toasts was available up until bootstrap 4.5.0, in v4.5.1 there were some changes, in which it seems that the background blur got removed.

The Bootstrap Documentation for v4.6.0 also mentions that there's an attempt to blur the background under the Toast but there's no such code to do it: https://getbootstrap.com/docs/4.6/components/toasts/#translucent

I've noticed this now that we've upgraded to the latest stable 4.6.x version and it looks yuck 😅.

Thank you.
@pricop pricop requested a review from a team as a code owner September 14, 2021 05:27
@pricop
Copy link
Author

pricop commented Sep 14, 2021

Just a quick update. I've found out that @mdo has actually issued a commit with the removal of the background filter: b2ef98f#diff-84a7935decf58a2c246ba26d1a02eb8da154e35a704f32fc998921289c028387

If this is decision is permanent, then perhaps the Documentation for v4.5.1 and higher should be updated to reflect that.

@mdo
Copy link
Member

mdo commented Oct 13, 2021

Yes, the docs should be updated, not the CSS. Care to open a new PR to address that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants