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
The only relevant difference is we load the bootstrap css and make the opacity adjustment where as this example does not and copy/pastes the bootstrap styling it needs, see https://github.com/scttcper/ngx-toastr/blob/master/src/styles.scss. We do have some additional styles we apply to our toasts to give them a custom background color but that's it.
What we've noticed is in chrome when the network throttling is turned on the notifications don't have all of the custom styling applied. They seem to have the default bootstrap but do not have our custom styles applied on them. If you turn network throttling off things work fine. It's almost like they are trying to lazy load the css? Is that what is happening?
The text was updated successfully, but these errors were encountered:
I have a custom bootstrap styled notification that I'm raising with toastr pretty much exactly like the example here https://github.com/scttcper/ngx-toastr/blob/master/src/app/bootstrap.toast.ts
The only relevant difference is we load the bootstrap css and make the opacity adjustment where as this example does not and copy/pastes the bootstrap styling it needs, see https://github.com/scttcper/ngx-toastr/blob/master/src/styles.scss. We do have some additional styles we apply to our toasts to give them a custom background color but that's it.
What we've noticed is in chrome when the network throttling is turned on the notifications don't have all of the custom styling applied. They seem to have the default bootstrap but do not have our custom styles applied on them. If you turn network throttling off things work fine. It's almost like they are trying to lazy load the css? Is that what is happening?
The text was updated successfully, but these errors were encountered: