New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
m3.barebackrt.com - mobile site is not usable #4120
Comments
I can reproduce this issue on Firefox mobile 53, android 5.1.1 Z3C. The request notification pops up success, I get error message once but can't reproduce again. It always shows in progress but no Maybe someone can help to test on different location and network. |
Update: I get "3-Position acquisition timed out" on Firefox mobile 53. |
Seems fixed in Firefox 51 and later version by https://bugzilla.mozilla.org/show_bug.cgi?id=1283563 |
It's failing with the same "3-Position acquisition timed out" message for me on my phones in today's Firefox nightly (it does so just on the login screen without having to actually log in). It tries for quite a while before failing, but works instantly in Chrome. I don't see any useful debug output in the web console, so switching to needsdiagnosis. |
This fails for me as well in Firefox 52, works instantly in Chrome. |
Thanks, I've filed Firefox bug 1336245 in the interests of getting some insight here. |
So in the bug opened by thomas, it says: try {
var geoLocOpts = {
enableHighAccuracy: true,
timeout: 10000,
maximumAge: 30
};
geoDone = true; the site is requesting high accurary for geoloc and because Firefox is using gps where Chrome benefits of their own data, Firefox is not able to reply on time. I'm moving this to needscontact to recommend the site to drop the high accuracy request. |
In fact let me change that, I'm closing as duplicate of bugzilla. |
Close as duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1336245 |
URL: https://m3.barebackrt.com/?gese&key=1496682830
Browser / Version: Firefox Mobile 52.0
Operating System: Android 6.0.1
Problem type: Mobile site is not usable
Steps to Reproduce
Expected Behavior: find location
Actual Behavior: can't find location
From webcompat.com with ❤️
The text was updated successfully, but these errors were encountered: