3 ms·
1. Not minor, foundational: UI element appearing before code to handle it, is ready for action. I'm seeing this regularly with smartphone on slow mobile connec
by RetroTechie 3y ago
1. Not minor, foundational: UI element appearing before code to handle it, is ready for action.
I'm seeing this regularly with smartphone on slow mobile connection. Eg. cookie dialogue appears, but tapping options doesn't respond, because scripts handling those actions are still being loaded.
Load or setup a handler first, then present UI element to trigger it.
2. Some webpage element sliding in from the top of the screen. And hiding. And back in. And hiding again, ad infinite.
Super annoying. If it's considered 'necessary', keep it visible. If not, let it go offscreen with the rest of a page when reader scrolls down. If designer meamt it to appear when user scrolls up: fine, but put some threshold (hysteresis) into it. But either way: pop in, pop out, pop in, pop out: aaargh. Just... don't.
3. "Subscribe to newsletter! Enter email / no thx" popup. I can find a "subscribe" link by myself, if present & desired, thank you very much!