News for hackers. Stuff that matters.
Re:WebKit removes the 350ms click delay for iOS by glesica on Wednesday October 14, 2015 @08:59PM (#10390658)
I didn't downvote you, but I also don't agree with your assumptions. First, I don't think that desktop sites are such a big problem on mobile (though some are, admittedly, unusable). At least with a desktop site I can zoom and figure out a way to get to the content I want (in fact iOS does, or used to, to let you double-tap on the content and it would intelligently zoom to fit). Most mobile sites with which I interact, on the other hand, are terrible. Either the text is too small and the page has disabled zooming, or content overflows and doesn't allow me to pan to see it, or some other terribleness. "Responsive" sites are actually some of the worst to interact with on mobile (for me).

I really don't believe that most developers of "desktop sites" care about mobile or do anything to optimize for it, and therefore wouldn't care about a 350ms delay, or even be aware of it. The people who are going to foul this up, it seems to me, are the "mobile web" developers who try to make their sites act like apps instead of just presenting content in a flexible manner.

Re:WebKit removes the 350ms click delay for iOS by Flow on Thursday October 15, 2015 @02:07AM (#10391608)
This has been my experience too. I surf in landscape mode on an iPhone 5, and far too often there's a fat social-sharing-bar at the bottom, and a fancy site-header-bar at the top, leaving about 1cm of readable and scrollable content. Wtf are they smoking?

A tip: Hold down your finger on the reload circle-arrow to load the desktop version of the page.

Re:WebKit removes the 350ms click delay for iOS by dredmorbius on Thursday October 15, 2015 @03:09AM (#10391774)
Reader mode FTFW.

Fuck fixed headers / footers. Fuck social. And fuck fixed social header/footer bars specifically.

Re:WebKit removes the 350ms click delay for iOS by jedrek on Thursday October 15, 2015 @04:41AM (#10392042)
I hate fixed bars on desktop as well - I still scroll with my keyboard and it chops content off willy nilly.
Re:WebKit removes the 350ms click delay for iOS by dredmorbius on Thursday October 15, 2015 @02:23PM (#10394947)
Yep. I've been creating my own local stylesheets under Stylish, including a default which pretty effectively nukes social elements and fixed headers, with some collateral damage I _may_ fix selectively on specific sites.

If you're naming your primary elements, or ascribing them values of "share" or "social" (wildcard search), they're likely to get nuked.

Re:WebKit removes the 350ms click delay for iOS by evook on Thursday October 15, 2015 @04:30AM (#10392009)
Best answer so far. Print mode is also not bad.
Re:WebKit removes the 350ms click delay for iOS by dredmorbius on Thursday October 15, 2015 @02:24PM (#10394954)
Print mode (offered by websites) so often 1) launches the actual browser print dialog and 2) closes the fucking page when the dialog's closed that I've largely abandoned use of it.

I'll sooner copy/paste text into a vim buffer.

Re:WebKit removes the 350ms click delay for iOS by fanf2 on Thursday October 15, 2015 @08:27PM (#10396833)
Oh man, this makes GitHub usable on my phone! Their mobile site is so shit.
Re:WebKit removes the 350ms click delay for iOS by jakobegger on Thursday October 15, 2015 @03:05AM (#10391762)
Thanks for that tip!
Re:WebKit removes the 350ms click delay for iOS by Tepix on Thursday October 15, 2015 @05:07AM (#10392108)
Install a content blocker...
Re:WebKit removes the 350ms click delay for iOS by PebblesHD on Wednesday October 14, 2015 @10:09PM (#10390902)
And thats a perfectly reasonable complaint to make, my argument is simply that developers of 'desktop sites' should in fact care about mobile browsers as they make up over 50% of page views on most large properties. If they can't make the effort to accomodate a smaller browser to the point where loss of the zoom function breaks their functionality then I feel that this kick might get them to work out these issues.