v4: Rip out IE compatibility mode meta tags #21483
Conversation
…ts as we no longer support IE9 and IE8
|
super awesome @mdo sir |
|
|
|
Exactly @Quy .... i didn't notice. cc /@mdo @bardiharborow |
|
I've been wondering this for a while now (and this probably isn't the place to talk about it, I just got reminded of it because of the change adding the note about v3), but v3 status is "no more features, only critical bug fixes and documentation improvements", but every v3 issue and pull request I've seen has been closed. Just how critical are we talking here? Why not merge #21341 which seems like a fairly big problem to some people? And why not merge pull requests like #21065 that just add a documentation improvement? |
|
@Starsam80 I'm labelling all those issues as they get closed. Anything I can come back to when v4 is released, I'll come back to. Otherwise, just talking about mental load and balancing work, life, and OSS, I can only focus on one major code version at a time. Trying to do both was no good for anyone for far too long. 😞 |
|
...and this |
|
@Starsam80 sorry but please support mark & team on this .... dont worry we all will get back to v3 rather sooner than later .... at this time v4 should be the focus ... These coming months, we should work hard for this v4 release first and then think about anything else like v3. |
|
@IamManchanda Thanks, but I appreciate @Starsam80 pushing back on that stuff. I did make some copy changes there and he's right that it's not all that accurate in how we're "maintaining" v3. |
|
Yup won't fix is the not the right choice , even i agree .... @mdo @Starsam80 Would be better to reopen those important issues or something like a temporary lock can also be a better choice for some of these issues but surely not most !! |
|
Or maybe a new label to show that they will be reviewed later. Maybe something like |
|
Yup 👍 @Starsam80 .... but i guess |
|
Why are these tags being removed? IE10 and IE11 still need those to make sure that they are using their respective latest rendering engine, no? |
|
|
||
| For a list of some of the browser bugs that Bootstrap has to grapple with, see our [Wall of browser bugs]({{ site.baseurl }}/browser-bugs/). | ||
|
|
||
| ## Internet Explorer | ||
|
|
||
| Internet Explorer 10+ is supported, however, IE9 down is not. Please be aware that some CSS3 properties and HTML5 elements are not fully supported. | ||
| Internet Explorer 10+ is supported; IE9 down is not. Please be aware that some CSS3 properties and HTML5 elements are not fully supported in IE10, or require prefixed properties for full functionality. Visit [Can I use...](http://caniuse.com/) for details on browser support of CSS3 and HTML5 features. |
There was a problem hiding this comment.
Not sure, but shouldn't it say "IE9 and down is not"?
no. HTML5 doctype has the exact same effect, without needing vendor-specific meta elements |
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
Bootstrap v4 Alpha 6 removes support for IE 8 and 9 and these tags are no longer necessary. See: twbs/bootstrap#21483
|
Sorry for bumping this old PR but the following statement is not entirely correct and I can't let it stand:
This only applies to pages which aren't in the "Intranet" zone, see https://www.leapinggorilla.com/Blog/Read/1016/ie-ate-my-css---disabling-compatability-mode What is true though is that the other reason for setting the meta tag in the past, the UI option to switch a page to compatibility mode is hidden per default (at least in IE11). |
Fixes #21476.
Updates the docs, examples, and JS tests to remove the relevant
<meta>tag. Also updates our docs to remove mention of some irrelevant IE8-9 business. This info will still be there in v3's docs, so we can update it later to link to things as needed.