* position error icon correctly
Add padding right to line with the error to accommodate space for the error icon.
Added in a new selector because it was getting overridden by more specific selectors.
Fixes#4287
* use important instead of selectors
* fix overlapping for smaller screens
* replace width with min-width
* align error icon to center vertically
Use em instead of pixels for padding, increase line height of error icon
* [beta] Reword "action = what happened" advice for useReducer
One learner misinterpreted the original text here as meaning instead that it's important that actions are written in past tense – this updated wording is clearer about what this is meant to convey (I think).
* typo
* [Beta] Fix layout shift from previews
* Arbitrary values
* Fix borked style
* Remove custom styles and start again
* Recreate existing layout
* Try to make it work
* Fix TS
Co-authored-by: Dan Lebowitz <dan.lebo@me.com>
* small fixes to stopwatch codesandbox
noticed that the explanation for the first stopwatch codesandbox mentions "update the time every 10 milliseconds" so updated the codesandbox to reflect that
also there's a small nuanced bug in the second stopwatch codesandbox where each call to `handleStart()` sets a new interval without checking if there's already one ongoing.
Ie: If the user accidentally double clicks the start button, they set two intervals for updating `now` every 10ms and then intervalRef only retains the second interval ID. Thus, it's impossible to actually stop the timer because `handleStop()` will only clear the latest set interval while the original one will keep executing.
* Update referencing-values-with-refs.md
* Update referencing-values-with-refs.md
* Update referencing-values-with-refs.md
Co-authored-by: dan <dan.abramov@gmail.com>
Updated the imported `react-router-dom` Component `BrowserRouter` to read as `BrowserRouter as Router` since the code example has it as `Router` instead of `BrowserRouter`
Alternatively, can change the `<Router></Router>` component to be `<BrowserRouter>...</BrowserRouter>`
I propose that "storing information from previous renders" sounds less like a _cool thing_ and also more clearly describes the rare cases this pattern is for.