1933920 - pay.rakuten.co.jp - Current location does not get displayed

Status: VERIFIED FIXED

(Web Compatibility :: Site Reports, defect, P2)

Description

[Calin Tanase]

Environment:
Operating system: Android 14
Firefox version: Firefox Mobile 133/135

Steps to reproduce:

1. Go to https://pay.rakuten.co.jp/shop/map/?scid=wi_rpay_map_nav_shop
2. Allow the location when prompted.
3. Observe the behavior.

Expected Behavior:
It shows the current location.

Actual Behavior:
Shows Tokyo as a standard location and displays an error after a few seconds.

Notes:

• Reproduces regardless of the status of ETP
• Reproduces in firefox-nightly, and firefox-release
• Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/144233

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Comment 2

[Sean Feng [:sefeng211]]

The site works as, using navigator.geolocation.watchPosition API to consistently get the current location, consistently stores it to local session storage, and then checks the stored value in session storage.

The issue is, we don't see to update the location correctly.

Running the following code on the site only execute twice in Firefox, but it gets consistently called in Chrome.

navigator.geolocation.watchPosition(function(pos) {
    console.log(pos);
}, function() {console.log("got error")}, {maximumAge: 600000, enableHighAccuracy: true})

Comment 3

[Sean Feng [:sefeng211]]

Filed the platform bug for this, bug 1934115

Comment 4

[Calin Tanase]

Retriaged, the issue is still reproducible with the latest Nightly.

Tested with:

• Browser / Version: Nightly 140.0a1-20250524091254
• Operating System: Google Pixel 5 (Android 14)

Comment 5

[Sean Feng [:sefeng211]]

Kagami, I think we chatted about this in Berlin...do you mind take a look again? Thanks!!

Comment 6

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

I can't reproduce comment #0. I still see the error popup saying「このエリアに当該するお店がございません」, which means there's no stores matching your location, which is natural because this is for Japan and I'm in Germany. It still properly locates me anyway. Is this what you see too, or if not can you explain more?

Comment 7

[Sean Feng [:sefeng211]]

For me, Chrome was able to show my current location (Toronto, Canada) but Firefox stuck at Japan

Comment 8

[Calin Tanase]

Attachment: First load Nightly 140.png

It seems to work after a reload, on first load it shows me central Tokyo. I can reproduce this issue on clean every time.

Note: When you clear the cookies and site data, close the tab and access the website on a new tab. I'm not able to reproduce the issue if I clear the cache/data and reload the page. (or if you want to be on the safer side delete everything from browsing data)

Comment 9

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

Sean, can you check the location permission is not Blocked?

What are the repro steps here? It certainly goes to Japan if I do nothing for like 10 seconds for the prompted permission request (if there's no cache), but the same happens on Chrome.

Edit: Testing on Galaxy S22 Ultra, if this matters.

Comment 10

[Sean Feng [:sefeng211]]

Hey Kagami, here's a recording for Firefox and here's a recording for Chrome.

I cleared the browsing data for both of them, and you can see that Firefox wasn't able to locate me upon the first try.

Comment 11

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

Can you double check the nightly version just in case?

To me it looks like the Android geolocation service is having time to get signal. If you try the same but after doing the same on Google Maps, does it change the result?

Comment 12

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

And if you can connect the debugger, can you try calling navigator.geolocation.watchPosition(console.log, console.error) and see how long it takes to get the first signal?

Comment 13

[Sean Feng [:sefeng211]]

Nightly is 20250524091254

Not sure if I understand the Google Maps part.. https://drive.google.com/file/d/1htr6Dku8YZF6KNqe43QxefXiqxcheniG/view?usp=sharing here's another one I just did.

navigator.geolocation.watchPosition(console.log, console.error) works pretty fast for me, like instant..

Comment 14

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

Hmm, somehow I managed to reproduce it. It's nothing to do with cache clear for me, it happens if I force close the browser and reopen it. Debugger shows the error callback ultimately gets code=1 (which is GeolocationPositionError.PERMISSION_DENIED) after several seconds even though the permission is not denied. And that callback makes the website show 「現在地の取得ができません。」, which says failed to get the location. (They could make the error message better. 🤔)

I wonder the permission request is sometimes not handled and is disposed, leading to unexpected permission deny. Maybe Kato-san has better idea?

Edit: The same doesn't happen on https://browserleaks.com/geo, so maybe still something to do with Rakuten doing two geolocation requests at once.

Comment 15

[Makoto Kato [:m_kato]]

Fenix/ac resolves two GeckoResult as ContentPermission.VALUE_ALLOW correctly. But at first time, Gecko (GeckoView?) throws permission denied... I need to investigate more why.

Comment 16

[Makoto Kato [:m_kato]]

Ah, I tested this issue with geolocation permission of Android is set. Android permission request seems be be disposed... This implementation doesn't use GeckoResult and callback isn't handled, so this permission request doesn't return forever.

Comment 17

[Makoto Kato [:m_kato]]

Also, I guess that this has another issue that is regression by bug 1771229. When Android permission dialog appears, Fenix's window is inactive. Then after permission dialog is closed, window becomes active. But when starting geolocation request, it is still inactive...

Comment 18

[Brian Birtles (:birtles)]

This seems to work for me in Firefox Beta on Android now—it correctly shows my current location on the second load in both Firefox and Chrome. Can we close this?

Comment 19

[railioaie]

The issue is not reproducible anymore using the latest Nightly. Thank you!

Comment 20

[Makoto Kato [:m_kato]]

I also verified.

Comment 21

[Raul Bucata]

Verified as FIXED using RC Build fenix android-arm64-v8a

Tested with:

Browser / Version: Firefox 142.0 Build 2016107994
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)
Operating System: Oppo Find X5 (Android 13) - 1080 x 2400 pixels, 20:9 ratio (~402 ppi density)