Only set userSelect:auto on anchor tags (native)

[necolas]

Fix #314

[github-actions]

workflow: benchmarks/size

Comparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better.

Results	Base	Patch	Ratio
react-strict-dom/dist/dom/index.js
· compressed	2,513	2,513	1.00
· minified	8,695	8,695	1.00
react-strict-dom/dist/dom/runtime.js
· compressed	855	855	1.00
· minified	2,435	2,435	1.00
react-strict-dom/dist/native/index.js
· compressed	16,226	16,259	1.00	+
· minified	60,854	60,755	1.00	-

[github-actions]

workflow: benchmarks/perf (native)

Comparison of performance test results, measured in operations per second. Larger is better.

Results	Base	Patch	Ratio
css.create
· small	1,129,366	1,136,227	1.01	+
· small with units	438,689	436,853	1.00	-
· small with variables	671,873	673,174	1.00	+
· several small	323,657	321,264	0.99	-
· large	209,140	206,674	0.99	-
· large with polyfills	149,180	146,523	0.98	-
· complex	102,377	101,433	0.99	-
· unsupported	220,474	222,422	1.01	+
css.createTheme
· simple theme	228,220	227,624	1.00	-
· polyfill theme	213,098	211,756	0.99	-
css.props
· small	245,757	246,198	1.00	+
· small with units	191,828	192,099	1.00	+
· small with variables	106,690	107,315	1.01	+
· small with variables of units	75,678	75,666	1.00	-
· large	104,852	104,345	1.00	-
· large with polyfills	37,359	37,573	1.01	+
· complex	23,406	23,689	1.01	+
· unsupported	147,408	146,998	1.00	-
· simple merge	163,554	164,534	1.01	+
· wide merge	17,722	17,905	1.01	+
· deep merge	17,418	17,578	1.01	+
· themed merge	31,386	31,312	1.00	-

[mdjastrzebski]

I've done some practical checks, and:

• on iOS: neither onPress nor userSelect style triggers keyboard navigation focus. Wrapping Text in Pressable (or simply <View accessible>) allows for focusing the text. However, when nesting that inside Text you get whacky layout.

• on Android: having onPress prop alone is sufficient for Text component to receive keyboard navigation focus (being wrapped in Pressable is also fine)

Therefore, I would recommend on not applying userSelect: auto to a elements, as:

• it's not needed on Android, having onPress prop is enough
• it does not work on iOS anyway
• AFAIU the purpose of userSelect style is to allow for user to copy given text, not to make it focusable by keyboard, that would be tabIndex/focusable props (but these work only on Android anyway)

You can check the experiements repo here: https://github.com/mdjastrzebski/repro-rsd-keyboard-navigation

[necolas]

Updated to remove it entirely

[mdjastrzebski]

✅ Looks Good! Thank you for fixing it.