-
Notifications
You must be signed in to change notification settings - Fork 771
fxShow is setting display:inline; in IE11 and Edge #310
Comments
The Will re-open issue if problem persists.
|
It's still If you don't have access to Windows for testing, Microsoft provides virtual machine images. |
Material2 builds the CSS: .mat-menu-item {
display: block;
position: relative;
line-height: 48px;
height: 48px;
padding: 0 16px;
background: 0 0;
color: rgba(0,0,0,.87);
font-family: Roboto,"Helvetica Neue",sans-serif;
font-size: 16px;
-webkit-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
user-select: none;
cursor: pointer;
outline: 0;
border: none;
-webkit-tap-highlight-color: rgba(0, 0, 0, 0);
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
text-align: left;
text-decoration: none;
} I am confused regarding why this same code - when used in an IE11 browser - will calculate 'inline'. |
I just added IDs to the non- |
Are you using the latest build from var immediateValue = _angular_platformBrowser.ɵgetDOM().getStyle(element, 'display');
value = immediateValue || _angular_platformBrowser.ɵgetDOM().getComputedStyle(element).getPropertyValue('display');
|
The Show/Hide directives would query the `display` style during construction. For elements constructed during `*ngFor`, calls to getComputedStyle() would incorrectly return “”. Query for styles in CSS stylesheets or inline styles would fail. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
The Show/Hide directives would query the `display` style during construction. For elements constructed during `*ngFor`, calls to getComputedStyle() would incorrectly return “”. Query for styles in CSS stylesheets or inline styles would fail. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
The Show/Hide directives would query the `display` style during construction. For elements constructed during `*ngFor`, calls to getComputedStyle() would incorrectly return “”. Query for styles in CSS stylesheets or inline styles would fail. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
Previously, the Show/Hide directives would query the `display` style during directive instantiation. For elements instantiated during `*ngFor`, constructor calls to getComputedStyle() will incorrectly return “” due to failures in queries for styles in CSS stylesheets or inline styles. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
Previously, the Show/Hide directives would query the `display` style during directive instantiation. For elements instantiated during `*ngFor`, constructor calls to getComputedStyle() will incorrectly return “” due to failures in queries for styles in CSS stylesheets or inline styles. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
Previously, the Show/Hide directives would query the `display` style during directive instantiation. For elements instantiated during `*ngFor`, constructor calls to getComputedStyle() will incorrectly return “” due to failures in queries for styles in CSS stylesheets or inline styles. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
Previously, the Show/Hide directives would query the `display` style during directive instantiation. For elements instantiated during `*ngFor`, constructor calls to getComputedStyle() will incorrectly return “” due to failures in queries for styles in CSS stylesheets or inline styles. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
Previously, the Show/Hide directives would query the `display` style during directive instantiation. For elements instantiated during `*ngFor`, constructor calls to getComputedStyle() will incorrectly return “” due to failures in queries for styles in CSS stylesheets or inline styles. Deferring these types of queries to the ngOnInit() lifecycle event, enables valid response to queries for both inline styles and stylesheets. Fixes #310.
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. |
https://plnkr.co/edit/lF0h5ttXwFiOLrjIgKDr?p=preview
Discovered when using fxShow with md-menu-items. In the above plunkr, the last 4 items in the menu have
fxShow
on them. In IE11 and Edge,display:inline
is applied to them, which ruins the layout.The text was updated successfully, but these errors were encountered: