diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-08-26 01:54:30 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-08-26 01:54:30 +0200 |
| commit | 7f4da24fe9d357f36561da6968bb87d59945c000 (patch) | |
| tree | a0e47a109fd5a9a719967b695a400bb99a5cb237 /packages/meshbay-node/src | |
| parent | ba7677290a2f2963295f1c015cdb90fe86ef63da (diff) | |
| download | meshbay-7f4da24fe9d357f36561da6968bb87d59945c000.tar.gz | |
fix(hub): disable Android's default tap-highlight flash
The :hover/:focus fix in 909505f didn't fully clear the "stuck pressed"
look reported on mobile Chrome: screenshots showed the music player's
"next" button (which carries no state class in the JS at all — not
.active, not .music-player-play) filled with a solid accent-blue
circle after a tap, and the same on "repeat". Neither :hover (already
scoped to `hover: hover`) nor the default focus outline (already
cleared for non-:focus-visible) produces a filled background, so
neither explained it.
Third, separate mechanism: -webkit-tap-highlight-color, Android's own
touch-feedback flash, never disabled anywhere in this stylesheet. Left
at its default, many Android builds tint it from the OS accent colour,
which is why it read as "the app's own blue" rather than an obviously
foreign highlight. Unrelated to real :hover/:focus, so disabling it
carries no keyboard-accessibility tradeoff at all.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013XSohfUQQiaE77qyFLgSv3
Diffstat (limited to 'packages/meshbay-node/src')
0 files changed, 0 insertions, 0 deletions