This is
1) using real CRA unnecessarily despite being in the browser so is slow to boot
2) shows "error" immediately to me and doesn't load
3) doesn't seem to get updated with newer React releases
We can readd it if it's fixed and doesn't have these problems (which none of the other templates do).
* More docs onFocus and onBlur events
Including more substantial documentation around the `onFocus` and `onBlur` events that aren't so common sense on first look.
* Update content/docs/reference-events.md
Co-authored-by: Darsh Shah <imdarshshah@gmail.com>
* Update reference-events.md
Adding an example of `relatedTarget` to determine orgin of onblur or onfocus events
* Update reference-events.md
* Update content/docs/reference-events.md
Fixing `onBlur` example bug.
Co-authored-by: Darsh Shah <imdarshshah@gmail.com>
* Update reference-events.md
Fixing spacing in `onBlur` `onFocus` examples and tagging them with `javascript`
* Update reference-events.md
* Update reference-events.md
* Update reference-events.md
Co-authored-by: Darsh Shah <imdarshshah@gmail.com>
Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
* remove event pooling and SyntheticEvent#persist from documents
Syntheticevent#event exists in v17, but it does nothing at the version
* add a page for legacy event pooling for _redirects
* add a warning e.persist() is no longer pooled
* Update legacy-event-pooling.md
* docs: update a redirect link for event pooling
* Update legacy-event-pooling.md
* Update legacy-event-pooling.md
* Update reference-events.md
Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
The sections above this describe how to use the arrow function to bind functions to the component instance to avoid explicit binding in the constructor. This example though, uses both the arrow function and explicitly binds the function. I realise the point of this particular example isn't to describe the binding process, but considering the sections that immediately proceed it, I think it'd be good to avoid confusion here.
* Removed deadlink from Event System section and added correct links
* Changed wording of Event System section and removed react-native events link
* Update codebase-overview.md
Co-authored-by: Dowen Robinson <drobinson@ad.accelclaims.com>
Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
* Clarify language in components-and-props.md
This is a nit for a few reasons:
- The point that extracting a component that "is complex enough on its own" means that it's not necessarily reusable.
- Extracting the components listed in the same sentence (e.g. App) are not necessarily reusable.
- This ends the section "Extracting Components" with a reference to extraction instead of re-usability.
- This delimits extracting into a separate component from creating a re-usable component.
* Update components-and-props.md
* Update components-and-props.md
