Remove libraries from benchmarks as comparison to css-modules baseline is what
matters. This makes benchmark builds faster and will reduce how often people
open PRs asking for their library to be included.
Close#2210
* Improves React Native compatibility by making StyleSheet.create the identify function.
* Improves React 18 support by inserting styles on eval.
* Supports use with multiple windows (i.e., iframes) and shadow roots.
* Supports nested LTR/RTL layouts.
* Supports 3rd party compilers and extraction to static CSS.
* Fixes static and dynamic short/longform deduplication.
* Reduces browser support: Safari 10.1+, Chromium Edge, no IE, no legacy Android browsers.
* Removes automatic vendor-prefixing of inline styles (for better perf).
* Removes focus-visible polyfill as modern browsers no longer show focus rings for mouse interactions.
Close#2208Fix#2138Fix#2196Fix#2007Fix#1517
Less specific shorthand style properties are being applied instead of the more
specific styles if there is another element also with one of the more specific
styles. This is due to the common styles being pulled out as class names for
de-duplication.
Ref #2007Close#2010
Safari requires use of `white-space:nowrap` if not using the multi-line
technique. This patch uses the multi-lines styles to truncate single-lines.
Fix#2111Close#2113
Only set the click handler if it is needed. This was previously always set,
which caused screen readers to announce the element as "clickable".
Close#2061
This patch removes the keyboard `onClick` shim from `unstable_createElement`
and adds it to the `PressResponder`.
Previously, the logic in `createElement` was calling `onClick` during
`onKeyDown`. This could result in React state update warnings if the host
element was no longer in the DOM during `keyup`.
Fix#2051
Elements other than 'a' support the 'href' attribute, so the element type
should not be inferred from 'href'. Longer term no host element type inference
should be performed by 'createElement'.
Fix#1958
This role is not meant to be in the tab flow unless the element type demands
it. Users will now have to manage `onClick` and `onKeyDown` callbacks to apply
the desired interaction behavior.
Fix#1968
The TextInput element no longer uses the 'number' input type, so this reset is
no longer necessary. Furthermore, the reset potentially impacts non-framework
components.
Fix#1949
The host node ref is not a dependency of the focus handling. Previously, the
focus callback was not called if the element was auto-focused, because React
DOM calls `onFocus` while the object ref is `null`.
Fix#2045
