Skip to content
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

Closed
webcompat-bot opened this issue Dec 29, 2016 · 9 comments
Closed

m3.barebackrt.com - mobile site is not usable #4120

webcompat-bot opened this issue Dec 29, 2016 · 9 comments

Comments

@webcompat-bot
Copy link

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

  1. Navigate to: https://m3.barebackrt.com/?gese&key=1496682830

Expected Behavior: find location

Actual Behavior: can't find location

Screenshot Description

From webcompat.com with ❤️

@MDTsai
Copy link

MDTsai commented Dec 30, 2016

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
But on Chrome mobile and Firefox desktop in responsive mode, it can get GeoLocation immediately after allow request.

Maybe someone can help to test on different location and network.

@MDTsai
Copy link

MDTsai commented Dec 30, 2016

Update: I get "3-Position acquisition timed out" on Firefox mobile 53.

@MDTsai
Copy link

MDTsai commented Dec 30, 2016

Seems fixed in Firefox 51 and later version by https://bugzilla.mozilla.org/show_bug.cgi?id=1283563

@wisniewskit
Copy link
Member

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.

@adamopenweb
Copy link
Collaborator

This fails for me as well in Firefox 52, works instantly in Chrome.

@wisniewskit
Copy link
Member

wisniewskit commented Feb 2, 2017

Thanks, I've filed Firefox bug 1336245 in the interests of getting some insight here.

@karlcow
Copy link
Member

karlcow commented Nov 30, 2017

So in the bug opened by thomas, it says:
https://bugzilla.mozilla.org/show_bug.cgi?id=1336245

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.

@karlcow
Copy link
Member

karlcow commented Nov 30, 2017

In fact let me change that, I'm closing as duplicate of bugzilla.
I will explain there

@karlcow
Copy link
Member

karlcow commented Nov 30, 2017

Close as duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1336245

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants