Anton Korzunov
Anton Korzunov
Use componentDidUpdate instead of getDerivedStateFromProps to run side-effects? Currently, one could use selector/flow-step with side-effect, and have to _defer_ any state change he could execute inside, leading to 2 problems....
Locky should support LIFO activation order, as focus lock does. Currently - 2 active locky on the page would block everything - document, body, and eachother.
Discovered in Storybook environment, when was not able to reset `resourceContext` between different stories. Expectation: mounting/unmounting Router and especially MemoryRouter are not by previously used components.
RRR has a few goals to have a flat routing, the ability to preload code or data is one of them. But we cannot use this ability "properly" out of...
As I understand resourceContext might be used to fed `getKey`/`getData` with extra props, not reflected in the `query`. However the updates to it are ignored, and context is never updated....
#### original issue https://github.com/facebook/react/issues/16938 #### test which explains everything https://github.com/facebook/react/pull/16945/files#diff-ab371863932cd2e8f0ba14ff2eaab380R687 --- Mostly for your information. The last React version which will work out of the box with the provided examples...
Look like xss is not possible, as long as HTML tags are escaped by React. Only placeholders could be faked, and should be handled only on save/restore operations.
https://developer.mozilla.org/en-US/docs/Web/CSS/scrollbar-gutter as `overflow-hidden` on body will not "hide" scrollbar cc @thearnica
`Remove-scroll` right now completely disables scroll outside of the "lock". In the same time, scroll could occur as a result of a "focus-jump" or be driven programmatically in a different...
This PR improves two moments: - it presorts `cache` file, so there is no need to do it every time, as well sorts package names so the file is more...