-
Notifications
You must be signed in to change notification settings - Fork 768
Responsive Flex Layout Chrome Bug #481
Comments
@JaimeStill , I tried to run your repro on edge and the editor can't render your app! The StackBlitz editor works fine on Chrome, but I think that defeats the purpose of your question. Have you been successful with flex-layout on Edge? I'm getting weird layouts, like super thin columns in Edge. |
@largeDachshund , In Edge, opening the repro in full screen preview appropriately shows the app. However, opening the repro from the link above generates the following error for me when instantiating: Fatal error:
Access is denied.
Evaluating https://unpkg.com/core-js@2.4.1/modules/_export.js
Evaluating https://unpkg.com/core-js@2.4.1/modules/es6.reflect.apply.js
Evaluating https://unpkg.com/core-js@2.4.1/es6/reflect.js
Evaluating polyfills.ts
Evaluating main.ts
Loading blitzapp |
@JaimeStill , thanks for the clarification. |
We have a PR pending that should fix the use of |
The fix without using the
We'll look into changing the default behavior, but for now this is the prescribed solution. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Bug
What is the expected behavior?
When moving from row to column layout, controls should stack appropriately
What is the current behavior?
In Chrome, when transitioning from row to column layout with an element that has a nested column layout, all of the elements merge onto the same line.
Examples
Chrome at gt-md

Chrome at lt-lg

Firefox at lt-lg

What are the steps to reproduce?
Repro
All of the relevant markup is in test.component.html
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Tested with the following:
Angular 4.4.4
Material 2 beta 12
flex-layout 2 beta 10
Is there anything else we should know?
While the following causes the mess in Chrome, but works in Firefox and Edge:
The following causes the intended behavior to work in all browsers:
The text was updated successfully, but these errors were encountered: