Artifact
Evan Stewart
23d
Head’s up front-end devs: Chrome is doing some weird stuff right now
We encountered a weird edge case this week I wanted to share since your customers might be in a similar boat: some people couldn't click our buttons. 😭 Turns out it's a persistent problem with Chrome’s latest updates. Here's the TL;DR: The problem persists when a user is: - In full-screen vs. a windowed view - Using Google Chrome - On desktop - Appears to be more apparent on Mac They can click all interactions while in a windowed view, but in fullscreen they can't interact with html elements like <button />. Chrome doesn't render any errors, the user simply *can't click* your buttons. The issue is also isolated to buttons rendered on the site (vs. browser-based buttons, like bookmarks) making it appear very much like your app is completely unresponsive. The fix is user-based and simple: the user needs to enable gpu rasterization in their Chrome browser. This can be solved in two steps: - Paste chrome://flags/#enable-gpu-rasterization into the address bar - Toggle to `on` - Restart Chrome It's an extreme edge case but—considering Chrome is the most used browser in the world—one your customers are likely experiencing as well. Hopefully this helps you avoid getting gaslit by Chrome thinking your <button /> element is somehow incorrectly engineered 🫡
2 Comments 4 Likes
Kang Zhang
🥸🥸 imagine a lot of people pulling the hairs on metric drops
Heart
1
Evan Stewart
I was terrified we somehow shipped a straight brick of an update 😅
Heart
1
Comment
4
1
2
App Store
Download Artifact to read and react to more links
App Store Play Store