Fix base react-apps-check: New Tab row lint
Base-red repair. c4b5aee486019 (cx-d0d.80) put onMouseDown on the New Tab field's row (NewTabScreen.tsx:476). The resulting jsx-a11y/no-static-element-interactions warning fails bun run check, so web / react-apps-check is red on every PR that runs it (seen on #20197).
The row's press only moves focus into the field, which stays the control. So this adds a disable comment like the one in MenuRow.tsx, rather than a role that would announce the row as something it isn't.
Testing
bun run check in webviews/ now passes with no warnings. Before this change it failed with 1 warning.
Changelog
none
🤖 Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3.svg)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark.svg)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the failing web / react-apps-check by silencing a lint warning in NewTabScreen.tsx.
Bug Fixes
- Adds a
jsx-a11y/no-static-element-interactionsdisable comment to the New Tab row, matching the pattern inMenuRow.tsx. - The row's press only moves focus into the field (which stays the control), so a disable comment is used rather than a role that would misrepresent the element.
bun run checkinwebviews/now passes with no warnings.