You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an umbrella issue for remaining Red Box issues. Please let me know if I forgot any.
PR: #1101
Blockers
Clicking arrows currently makes their text select. Are those implemented as buttons? We need to make sure clicking doesn't select text.
We also need to make sure this dialog is accessible. Can you please read accessibility guidelines for dialogs and make sure we follow as much as possible? This might mean specifying some ARIA attributes etc.
Good point, this should also look reasonably well with mobile exultation.
There is an annoying screen jump when switching between source / compiled because compiled includes a line with ^. In a perfect world I would like to see the line with | ^ get hidden, and instead see ^ rendered absolutely below the offending character. Yeah I know this is not fun. 😄
Some design work on the syntax overlay screen to make them more visually cohesive. Not just in palette but in how they feel like. Syntax overlay is a lazy "terminal" output and wasn't really "designed". I'm not sure how to fix this and I don't want to block the PR on this but we need to make a conscious decision here.
Only code should scroll horizontally; not the page
Ensure bootstrap hidden from output
Add "This screen is visible only in development. It will not appear when the app crashes in production. Open your browser’s developer console to further inspect this error."
This is an umbrella issue for remaining Red Box issues. Please let me know if I forgot any.
PR: #1101
Blockers
source <-> compiled
toggle javascript-y and on per-stack-frame basis https://github.com/Timer/create-react-app/issues/10cursor: pointer
all the (clicky) things!Remove whitespace(do in babel-code-frame)"This screen is visible only in development. It will not appear when the app crashes in production. Open your browser’s developer console to further inspect this error."
The text was updated successfully, but these errors were encountered: