{"action":"created","issue":{"url":"https://api.github.com/repos/angular/flex-layout/issues/819","repository_url":"https://api.github.com/repos/angular/flex-layout","labels_url":"https://api.github.com/repos/angular/flex-layout/issues/819/labels{/name}","comments_url":"https://api.github.com/repos/angular/flex-layout/issues/819/comments","events_url":"https://api.github.com/repos/angular/flex-layout/issues/819/events","html_url":"https://github.com/angular/flex-layout/issues/819","id":351953169,"node_id":"MDU6SXNzdWUzNTE5NTMxNjk=","number":819,"title":"fxLayout.gt-xs setting inside dialog affects non-dialog layout","user":{"login":"DmitryEfimenko","id":2098175,"node_id":"MDQ6VXNlcjIwOTgxNzU=","avatar_url":"https://avatars0.githubusercontent.com/u/2098175?v=4","gravatar_id":"","url":"https://api.github.com/users/DmitryEfimenko","html_url":"https://github.com/DmitryEfimenko","followers_url":"https://api.github.com/users/DmitryEfimenko/followers","following_url":"https://api.github.com/users/DmitryEfimenko/following{/other_user}","gists_url":"https://api.github.com/users/DmitryEfimenko/gists{/gist_id}","starred_url":"https://api.github.com/users/DmitryEfimenko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DmitryEfimenko/subscriptions","organizations_url":"https://api.github.com/users/DmitryEfimenko/orgs","repos_url":"https://api.github.com/users/DmitryEfimenko/repos","events_url":"https://api.github.com/users/DmitryEfimenko/events{/privacy}","received_events_url":"https://api.github.com/users/DmitryEfimenko/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-08-20T01:06:04Z","updated_at":"2018-10-01T15:57:24Z","closed_at":null,"author_association":"NONE","body":"# Bug Report\r\n\r\n#### What is the expected behavior?\r\nsetting fxLayout should not affect unexpected areas\r\n\r\n#### What is the current behavior?\r\nplease see [demo](https://stackblitz.com/edit/angular-material-flex-layout-bug)\r\n\r\n#### What are the steps to reproduce?\r\n*  [StackBlitz demo](https://stackblitz.com/edit/angular-material-flex-layout-bug)\r\n* Please read steps in the demo\r\n\r\n#### What is the use-case or motivation for changing an existing behavior?\r\nIt should work properly\r\n\r\n#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?\r\nAngular: 6.1.3\r\nMaterial: 6.4.5\r\nOS: Windows\r\nTypeScript: whatever StackBlitz uses\r\nBrowsers: Chrome, Fireefox, Edge\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/angular/flex-layout/issues/comments/425961370","html_url":"https://github.com/angular/flex-layout/issues/819#issuecomment-425961370","issue_url":"https://api.github.com/repos/angular/flex-layout/issues/819","id":425961370,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNTk2MTM3MA==","user":{"login":"DmitryEfimenko","id":2098175,"node_id":"MDQ6VXNlcjIwOTgxNzU=","avatar_url":"https://avatars0.githubusercontent.com/u/2098175?v=4","gravatar_id":"","url":"https://api.github.com/users/DmitryEfimenko","html_url":"https://github.com/DmitryEfimenko","followers_url":"https://api.github.com/users/DmitryEfimenko/followers","following_url":"https://api.github.com/users/DmitryEfimenko/following{/other_user}","gists_url":"https://api.github.com/users/DmitryEfimenko/gists{/gist_id}","starred_url":"https://api.github.com/users/DmitryEfimenko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DmitryEfimenko/subscriptions","organizations_url":"https://api.github.com/users/DmitryEfimenko/orgs","repos_url":"https://api.github.com/users/DmitryEfimenko/repos","events_url":"https://api.github.com/users/DmitryEfimenko/events{/privacy}","received_events_url":"https://api.github.com/users/DmitryEfimenko/received_events","type":"User","site_admin":false},"created_at":"2018-10-01T15:57:24Z","updated_at":"2018-10-01T15:57:24Z","author_association":"NONE","body":"Thanks for the quick reply. So adding `fxShow.gt-sm` for some reason fixed the issue. It will work as a workaround though I would not call it \"it works fine\" :)\r\n\r\nThe workaround is unintuitive and it should work without it. The fact that it does not might be pointing on a bigger issue in the core implementation."}}
{"actor":{"display_login":"DmitryEfimenko"}}