element-call/src/FullScreenView.module.css
David Baker cf309102a2 Make the error boundary work
We had an error boundary at the top level of the app, but it didn't
work because it used ErrorPage which tried to use a bunch of things
like useLocation() and an error prop. Also it wasn't passed in correctly
anyway.

This wires it up correctly to a separate view with a button to send
debug logs, and also moves it down a few layers so it has access to
enough things to be able to send rageshakes.

Related: https://github.com/vector-im/element-call/issues/421
2022-07-20 20:43:11 +01:00

47 lines
681 B
CSS

.page {
position: relative;
display: flex;
flex-direction: column;
overflow: hidden;
min-height: 100%;
}
.header {
padding: 76px 65px;
}
.container {
display: flex;
flex-direction: column;
justify-content: center;
align-items: center;
flex: 1;
}
.content {
display: flex;
flex-direction: column;
justify-content: center;
align-items: center;
max-width: 660px;
padding: 0 65px;
}
.content > * {
margin-top: 0;
margin-bottom: 32px;
}
.content > :last-child {
margin-bottom: 0;
}
/* Make the buttons the same width */
.wideButton {
width: 291px;
}
/* Fixed height to avoid content jumping around*/
.sendLogsSection {
height: 50px;
}