{"action":"created","issue":{"url":"https://api.github.com/repos/mui-org/material-ui/issues/12568","repository_url":"https://api.github.com/repos/mui-org/material-ui","labels_url":"https://api.github.com/repos/mui-org/material-ui/issues/12568/labels{/name}","comments_url":"https://api.github.com/repos/mui-org/material-ui/issues/12568/comments","events_url":"https://api.github.com/repos/mui-org/material-ui/issues/12568/events","html_url":"https://github.com/mui-org/material-ui/issues/12568","id":351689497,"node_id":"MDU6SXNzdWUzNTE2ODk0OTc=","number":12568,"title":"Opening second panel scrolls all content off screen ","user":{"login":"salientknight","id":40220684,"node_id":"MDQ6VXNlcjQwMjIwNjg0","avatar_url":"https://avatars3.githubusercontent.com/u/40220684?v=4","gravatar_id":"","url":"https://api.github.com/users/salientknight","html_url":"https://github.com/salientknight","followers_url":"https://api.github.com/users/salientknight/followers","following_url":"https://api.github.com/users/salientknight/following{/other_user}","gists_url":"https://api.github.com/users/salientknight/gists{/gist_id}","starred_url":"https://api.github.com/users/salientknight/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/salientknight/subscriptions","organizations_url":"https://api.github.com/users/salientknight/orgs","repos_url":"https://api.github.com/users/salientknight/repos","events_url":"https://api.github.com/users/salientknight/events{/privacy}","received_events_url":"https://api.github.com/users/salientknight/received_events","type":"User","site_admin":false},"labels":[{"id":770115883,"node_id":"MDU6TGFiZWw3NzAxMTU4ODM=","url":"https://api.github.com/repos/mui-org/material-ui/labels/component:%20ExpansionPanel","name":"component: ExpansionPanel","color":"ffffff","default":false},{"id":720656387,"node_id":"MDU6TGFiZWw3MjA2NTYzODc=","url":"https://api.github.com/repos/mui-org/material-ui/labels/waiting%20for%20user%20information","name":"waiting for user information","color":"e99695","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-08-17T18:08:50Z","updated_at":"2018-08-18T10:03:39Z","closed_at":"2018-08-18T10:03:39Z","author_association":"NONE","body":"<!--- Provide a general summary of the issue in the Title above -->\r\nI have 7 panels with a lot of content in each -- on page load all panels open properly. Once I open a second pane, however, the content scrolls up and off screen -- leaving me below the entire set of panels -- with the second panel open.  \r\n<!--\r\n    Thank you very much for contributing to Material-UI by creating an issue! ❤️\r\n    To avoid duplicate issues we ask you to check off the following list.\r\n-->\r\n\r\n<!-- Checked checkbox should look like this: [x] -->\r\n- [ X] This is a v1.x issue. <!-- (v0.x is no longer maintained) -->\r\n- [ X] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.\r\n\r\n## Expected Behavior\r\n  screne focus should be on top of newly opened pannel\r\n\r\n## Current Behavior\r\n  \r\n focus is not at top of newly opened panel - and is quite far down the page\r\n\r\n## Steps to Reproduce\r\nhttps://codesandbox.io/s/lxkw18mk2q\r\n\r\nI've done my best to explain what's wrong in this sample page. \r\nIt seems like when a panel is opened then a panel below it is open, it opens the new panel before closing the first panel, so when the first panel is closed, everything scrolls up by the hight of the panel that was opened first -- leaving focus far below the top of the newly opened panel.  If the panel opened first is below the new panel being open, the behavior works as expected.\r\n\r\nLink:\r\n\r\n1.https://codesandbox.io/s/lxkw18mk2q\r\n2.\r\n3.\r\n4.\r\n\r\n## Context\r\n  Trying to accomplish a single page with 7 panels of content each in turn hidden with the other is open  -- this is the last issues left to be addressed\r\n\r\n## Your Environment\r\nThe problem was easily reproduced in codesanebox.io \r\n\r\n| Tech         | Version |\r\n|--------------|---------|\r\n| Material-UI  | v1.5.0  |\r\n| React        |  v16.4.2       |\r\n| browser      |    any     |\r\n| etc.         |     windows/mac    |\r\n"},"comment":{"url":"https://api.github.com/repos/mui-org/material-ui/issues/comments/414046866","html_url":"https://github.com/mui-org/material-ui/issues/12568#issuecomment-414046866","issue_url":"https://api.github.com/repos/mui-org/material-ui/issues/12568","id":414046866,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNDA0Njg2Ng==","user":{"login":"oliviertassinari","id":3165635,"node_id":"MDQ6VXNlcjMxNjU2MzU=","avatar_url":"https://avatars2.githubusercontent.com/u/3165635?v=4","gravatar_id":"","url":"https://api.github.com/users/oliviertassinari","html_url":"https://github.com/oliviertassinari","followers_url":"https://api.github.com/users/oliviertassinari/followers","following_url":"https://api.github.com/users/oliviertassinari/following{/other_user}","gists_url":"https://api.github.com/users/oliviertassinari/gists{/gist_id}","starred_url":"https://api.github.com/users/oliviertassinari/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oliviertassinari/subscriptions","organizations_url":"https://api.github.com/users/oliviertassinari/orgs","repos_url":"https://api.github.com/users/oliviertassinari/repos","events_url":"https://api.github.com/users/oliviertassinari/events{/privacy}","received_events_url":"https://api.github.com/users/oliviertassinari/received_events","type":"User","site_admin":false},"created_at":"2018-08-18T10:03:39Z","updated_at":"2018-08-18T10:03:39Z","author_association":"MEMBER","body":"> The problem isn's that the accordion behavior is broken is that's the close behavior doesn't seem to be happening in the proper sequence. If the first open container closed first, the content of the second container should stay on the screen.\r\n\r\n@salientknight I see your point. It's exactly what I was looking for.\r\nSo instead of opening and closing two different panels at the **same time**. We can do one after the other. It's something the current API allows you to do. Close the panel, wait for the transition to complete, open the next panel. The current transition logic is optimized for small to medium content, what most people should be using the component for. "}}
{"actor":{"display_login":"oliviertassinari"}}