Greg Blass
Jul 27, 2017 · 1 min read

Yeah, I’ve been using fastclick.js.

My issue was that when I saw the (useless) tap delay was gone, I rejoiced since I would be able to remove the dependency from my codebase, clean up my code, lighten my assets and reduce my dependencies. I checked it into git, deployed…only to see that it was still there in fullscreen mode.

When I asked about it in the developer forums, I was ignored. I tweeted to people on Apple’s team (I think the right/relevant ones?), but again, ignored.

When I submitted a bug report, I simply got an email that it was a duplicate.

‘Engineering has determined that your bug report (25679073) is a duplicate of another issue (25573509) and will be closed.’

That was it. It’s the principal of the matter really. It’s simply frustrating to see them not only neglect safari full-screen mode — but also be silent about it when people speak up.

“We don’t care about you, lowly web developer. You don’t pay us anything. Go back to your non-app store place.”

I guess this article was the the result of the culmination of all of my experiences.

    Greg Blass

    Written by

    Software Engineer and Web/App Developer. DreamIt Philly Alum. Lover of Ruby on Rails, React/React Native, Progressive Web Apps, Live Music, Craft Beer and Jessi