Skip to content

Grid column overflows row in IE 10 when flex is enabled #20102

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

Closed
takeradi opened this issue Jun 9, 2016 · 3 comments
Closed

Grid column overflows row in IE 10 when flex is enabled #20102

takeradi opened this issue Jun 9, 2016 · 3 comments

Comments

@takeradi
Copy link

takeradi commented Jun 9, 2016

One of the known issues on http://caniuse.com/#search=flex is that:

In IE10 the default value for flex is 0 0 auto rather than 0 1 auto as defined in the latest spec.

On smaller screens when the col-* elements start to wrap, they default to flex: 0 0 auto instead of flex: 1 0 auto and the column overflows the row since the row is display: flex and the columns have been set not to shrink.

@twbs-lmvtfy
Copy link

Hi @takeradi!

You appear to have posted a live example (https://run.plnkr.co/plunks/spvWj4U7KP6p2mXJ7Dvp/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

  • line 13, column 5: E003: Found one or more .rows that were not children of a grid column or descendants of a .container or .container-fluid
  • W001: <head> is missing UTF-8 charset <meta> tag
  • W002: <head> is missing X-UA-Compatible <meta> tag that disables old IE compatibility modes
  • W003: <head> is missing viewport <meta> tag that enables responsiveness

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!

(Please note that this is a fully automated comment.)

@cvrebert
Copy link
Collaborator

cvrebert commented Jun 9, 2016

Please re-test against latest v4-dev branch. #19109 should have fixed this.

@twbs-closer
Copy link

Hey there!

We're automatically closing this issue since the original poster (or another commenter) hasn't yet responded to the question or request made to them 14 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.

Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

(Please note that this is an automated comment.)

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

No branches or pull requests

4 participants