TheDude
/
ciphermask
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
A Metamask fork with Infura removed and default networks editable
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
11834 Commits
2 Branches
1 Tag
200 MiB
Tag: Branch: Tree: 325215fb5f
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '325215fb5f'
${ noResults }
ciphermask/ui/app/pages/error/index.scss

42 lines
621 B
Raw Normal View History Unescape

Add top-level error page (#7889) Any error caught during a React component render or lifecycle method will now be caught by the top-level error boundary, which shows the user this new error page. The error page will display a simple error message, and will show the details of the error in a collapsible section. The caught error is also reported to Sentry. In development the error will be re-thrown to make it easier to see on the console, but it is not re-thrown in production.
5 years ago
.error-page {
display: flex;
flex-flow: column nowrap;
align-items: center;
font-style: normal;
font-weight: normal;
padding: 35px 10px 10px 10px;
height: 100%;
&__header {
normalize page font styles (#9697)
4 years ago
@include H1;
Add top-level error page (#7889) Any error caught during a React component render or lifecycle method will now be caught by the top-level error boundary, which shows the user this new error page. The error page will display a simple error message, and will show the details of the error in a collapsible section. The caught error is also reported to Sentry. In development the error will be re-thrown to make it easier to see on the console, but it is not re-thrown in production.
5 years ago
display: flex;
justify-content: center;
padding: 10px 0;
text-align: center;
}
&__subheader {
normalize page font styles (#9697)
4 years ago
@include H4;
Add top-level error page (#7889) Any error caught during a React component render or lifecycle method will now be caught by the top-level error boundary, which shows the user this new error page. The error page will display a simple error message, and will show the details of the error in a collapsible section. The caught error is also reported to Sentry. In development the error will be re-thrown to make it easier to see on the console, but it is not re-thrown in production.
5 years ago
padding: 10px 0;
width: 100%;
max-width: 720px;
text-align: center;
}
&__details {
normalize page font styles (#9697)
4 years ago
@include H4;
Add top-level error page (#7889) Any error caught during a React component render or lifecycle method will now be caught by the top-level error boundary, which shows the user this new error page. The error page will display a simple error message, and will show the details of the error in a collapsible section. The caught error is also reported to Sentry. In development the error will be re-thrown to make it easier to see on the console, but it is not re-thrown in production.
5 years ago
overflow-y: auto;
width: 100%;
max-width: 720px;
padding-top: 10px;
}
&__stack {
overflow-x: auto;
background-color: #eee;
}
}