The git log is a 404 :p
Love the new pull down to refresh feature!
"The Chrome Team is unquestionably ecstatic"Ohh :D
Please tell me it is possible to disable pull to refresh using a meta tag? This will break the UX of almost all mobile web apps.
@StephenJust run preventDefault(). Chances are it won't break many web apps at all since they already have to deal with Apple's bounceback-scrolling the same way.
I have not missed the ridiculous qualifiers being added in these descriptions... "Excited," "delighted," and this one.
All I get when opening links from external sources is a black screen that also disables chrome!
Selecting almost any option in settings page crashes the browser after the latest update. Hope we will get a text wrap option like Opera soon.
Beauty, hairstyle, fashion and nail art ideas in this site
I've noticed genuine performance improvements with this latest beta on my 2013 Nexus 7. Of course there's still more work to be done but scrolling and pinch zooming is noticeably smoother. Yes, really.Good work, Google. Keep it coming.
@Simon Unfortunately those workarounds are quiet nasty, don't work all the time and have performance issues (as you need to listen to all touchmove events).preventDefault() on touchmove on the body has the side effect of stopping scrolling for all scrollable elements. You then need to apply a work around for elements you want to be scrollable such as adding a 'scrollable' classname and checking for it in the function that calls preventDefault(). This is problematic for a number of reasons. These workarounds can also interfere with libraries such as FastClick.Chrome team, I hope there is an easier workaround for this in Chrome 41?
I've been using the Chrome Beta browser for about 4 years and just recently the black screen issue started happening. I'm currently using version 41.0.2272.45. The browser process must be terminated and the browser reopened to continue browsing.[Galaxy Note II, Android 4.4.2]Great browser!
Post a Comment