Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.

fix(layout): Revert overzealous IE11 flexbox fix. #9412

Merged

Conversation

topherfangio
Copy link
Contributor

A recent change which was supposed to fix an IE11 bug accidentally altered the flex-basis for the flex children of all .layout-column flex containers in all browsers.

Unfortunately, there is no IE11-specific fix.

  • Revert the original change.
  • Update the Layout Troubleshooting page with a new demo.
  • Update the Layout Children docs to mention the new demo.
  • Remove old Chrome-specific demo which was incidentally fixed
    by reverting this change.

Reverts ce0ebbf.

Fixes #9354.

A recent change which was supposed to fix an IE11 bug accidentally
altered the `flex-basis` for the flex children of all `.layout-column`
flex containers in all browsers.

Unfortunately, there is no IE11-specific fix.

 - Revert the original change.
 - Update the Layout Troubleshooting page with a new demo.
 - Update the Layout Children docs to mention the new demo.
 - Remove old Chrome-specific demo which was incidentally fixed
   by reverting this change.

Reverts ce0ebbf.

Fixes angular#9354.
@topherfangio topherfangio added the needs: review This PR is waiting on review from the team label Aug 25, 2016
@topherfangio topherfangio added this to the 1.1.1 milestone Aug 25, 2016
content. This is particularly noticable if you have a non-flex item (say a toolbar), followed by
two flex items in a column layout.
In Internet Explorer 11, when you have a column layout with unspecified height and flex items
inside, the browser can get confused and incorrectly calculate the height of each item (and thus
Copy link
Member

@devversion devversion Aug 25, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not really sure, but should that be and incorrectly calculates?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Random English Silliness

I honestly think either would work here, but how I judge it is this: remove the "get confused and" phrase to see how it sounds:

the browser can incorrectly calculate the height...

verses

the browser can incorrectly calculates the height...

Honestly, seeing as I've never seen it not get confused, it might be more correct to just say

the browser gets confused and incorrectly calculates the height...

Stupid english 😝

Copy link
Member

@devversion devversion Aug 26, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol, thanks for the explanation 😄 Keep whatever you think. You are the native speaker!

Probably some german habit

@devversion
Copy link
Member

That looks very good to me. Especially how everything is explained with an associated demo.

@ThomasBurleson
Copy link
Contributor

@topherfangio - lgtm, nice work here sir!

@ThomasBurleson ThomasBurleson added pr: merge ready This PR is ready for a caretaker to review and removed needs: review This PR is waiting on review from the team labels Aug 26, 2016
@hansl hansl merged commit 660826b into angular:master Aug 31, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pr: merge ready This PR is ready for a caretaker to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Demo in layout tips no longer fixes Chrome issue.
5 participants