Re:Firefox Android Build that caused issues is working as in...
by fooey on Tuesday August 25, 2020 @06:18PM
(#24276897)
The biggest thing I've missed is that pull to refresh doesn't work, and it's such a basic tiny little thing it drives me crazy every time it doesn't work.
[ Parent
| on HN ]
Re:Firefox Android Build that caused issues is working as in...
by staktrace on Tuesday August 25, 2020 @08:55PM
(#24277958)
Pull to refresh has been implemented, but still needs some polish before being released. https://github.com/mozilla-mobile/fenix/issues/9766
Re:Firefox Android Build that caused issues is working as in...
by akdor1154 on Tuesday August 25, 2020 @07:29PM
(#24277476)
Maybe someone could write an extension to implement it... Oh.
Re:Firefox Android Build that caused issues is working as in...
by yorwba on Tuesday August 25, 2020 @07:06PM
(#24277307)
I tap in the bottom-right corner to open the menu and then tap the refresh button, which is in the bottom-right corner of the menu. So basically don't need to move my thumb at all. Much more convenient than pull-to-refresh in my opinion.
Re:Firefox Android Build that caused issues is working as in...
by MaxikCZ on Tuesday August 25, 2020 @10:49PM
(#24278578)
I cant understand how 2 taps in precise location are more convenient to some people than one short swipe anywhere on screen, but to each their own I guess
Re:Firefox Android Build that caused issues is working as in...
by yorwba on Wednesday August 26, 2020 @04:48AM
(#24280491)
On my phone, pull-to-refresh doesn't work in Chrome if I only do a short swipe. It seems to reject anything shorter than 3cm or so. And that's only if I'm already at the top of the page.