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

Toasts and Internet Explorer 11 #28341

Closed
ray73864 opened this issue Feb 22, 2019 · 2 comments · Fixed by #30959
Closed

Toasts and Internet Explorer 11 #28341

ray73864 opened this issue Feb 22, 2019 · 2 comments · Fixed by #30959

Comments

@ray73864
Copy link

Having an interesting issue with IE11 and the new Toasts in 4.2.1.
I am using the functionality to centre a toast on the screen (horizontally at least) as found in this page:
https://getbootstrap.com/docs/4.2/components/toasts/#placement

With IE11, the toast that appears is just over 120px wide, where as in Chrome the toast is 348px wide.

OS: Windows 10 1809 & Windows Server 2012 R2
Browser: IE11
JSBin: https://jsbin.com/suyuguzidu/1/edit?html,js

When testing with JSBin, I found if you use the output pane, it shows correctly in IE11, but if you click the little arrow to pop it out into its own tab, it exhibits the problem.

I found if I set a 'style="width: 350px"' on the div with a class of 'toast' it shows correctly, and is an OK work around for now, but it's not ideal, mostly because if I was to change the scss to have a bigger max-width I would then have to manually change any html file with a toast on it.

@patrickhlauke
Copy link
Member

patrickhlauke commented Jun 22, 2019

coming in late, but confirming that on larger window width/viewport, the toast collapses in IE11 (it tries to center every single word). adding a fixed width (rather than max-width) would solve this. @twbs/css-review thoughts?

@ffoodd ffoodd mentioned this issue Jun 3, 2020
@ffoodd ffoodd linked a pull request Jun 3, 2020 that will close this issue
@ffoodd ffoodd added the has-pr label Jun 3, 2020
@XhmikosR
Copy link
Member

Fixed by #30959

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

Successfully merging a pull request may close this issue.

5 participants