4 ms·
Interesting -- but doesn't all that work to remove the 300ms delay mean make the site totally broken on any browser that doesn't generate touchstart/touchend/to
by aquark 14y ago
Interesting -- but doesn't all that work to remove the 300ms delay mean make the site totally broken on any browser that doesn't generate touchstart/touchend/touchmove events?
I guess you could code around this by catching the click event and deciding if you have already handled it, but that is beginning to feel like a lot of fragile and browser specific code that certainly isn't application specific.
I tried to access your mobile site from my phone but it wants me to sign in with either Facebook or Twitter before showing anything, so that was a non-starter.
- djb_hackernews 14y agoFair point, but, I think people need to realize it's ok to only support certain browsers. Every project doesn't need to support every browser from the start. There are of course trade offs, but they mention they are targeting Safari on iOS, and this is ok.
- deleted 14y ago[deleted]
- pygy_ 14y ago> I tried to access your mobile site from my phone but it wants me to sign in with either Facebook or Twitter before showing anything, so that was a non-starter. I created dummy accounts to that end. See https://twitter.com/loganloginski https://twitter.com/loganloginski