mobile-web-fixes
Skill1 starsChanged 7 days agoMITView on GitHub
Apply the mobile web fixes below when reviewing or fixing touch interactions, viewport sizing, safe areas, or phone-specific rendering issues.
The file
Files
Mobile web fixes
| Problem | Solution |
| Hover state stuck after tap | Wrap in @media (hover: hover) and (pointer: fine) |
| Grey/blue flash on tap | Kill -webkit-tap-highlight-color |
| Layout has wrong height | 100dvh (app) or 100svh (hero) |
| Page zooms into input | Input's font size should be 16px at the minimum |
| Tap feels laggy | Feedback on pointer-down + touch-action: manipulation |
| Pull-to-refresh hijacks scroll | overscroll-behavior: none on html, body |
| Content stops at the notch | viewport-fit=cover + env(safe-area-inset-*) |
| Long-press selects button text | Add user-select: none |
| Carousel scrolls vertically | touch-action: pan-y on the gesture surface |
| Status bar colour doesn't match | theme-color per colour scheme |
| Right in Chrome, wrong on phone | Test on real hardware! |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.