Closed
Bug 1195211
Opened 10 years ago
Closed 9 years ago
Geolocation API doesnt work on the Stingray TV
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-b2g:2.5+, b2g-v2.5 fixed, b2g-master fixed)
RESOLVED
FIXED
| blocking-b2g | 2.5+ |
People
(Reporter: pauljt, Assigned: yifan)
References
Details
(Whiteboard: [ft:conndevices][partner-blocker][partner-cherry-pick])
Attachments
(2 files)
|
580.00 KB,
image/png
|
Details | |
|
46 bytes,
text/x-github-pull-request
|
jj.evelyn
:
review+
jocheng
:
approval-gaia-v2.5+
|
Details | Review |
Geolocation doesnt seem to work on the TV. THere is no prompt shown and access to the API fails.
STR: navigate to http://html5demos.com/geo
Expected: geolocation prompt then access to the API
Actual: No access to the API. In the browser app, an error message is shown. In other apps no error is shown.
Comment 1•10 years ago
|
||
What are you referring to when you mention 'tv'? Apple AirPlay Mirroring? What is your setup and configuration?
Flags: needinfo?(ptheriault)
| Reporter | ||
Comment 2•10 years ago
|
||
Sorry I messed up filing here, wrong product and I didnt bloc the bug i meant to block. Sorry for distraction.
Blocks: TV_FxOS2.5
Flags: needinfo?(ptheriault)
Product: Firefox for iOS → Firefox OS
Summary: Geolocation API doesnt work on the TV → Geolocation API doesnt work on the Stingray TV
Comment 3•10 years ago
|
||
I don't think Stingray TV has geolocation sensor, but maybe it can leverage the same geolocation technology we have on Firefox Desktop.
Comment 5•10 years ago
|
||
Discussed with kanru on IRC, we have a fallback network location service in gecko already. However, for b2g we didn't turn on the fallback service by default. The first thing we need to fix is setting pref |geo.provider.use_mls| to true for Stingray TV [1] since it doesn't have geolocation sensor on platform.
[1] https://dxr.mozilla.org/mozilla-central/source/b2g/app/b2g.js#202
Comment 6•10 years ago
|
||
Clear ni first since there are some findings in comment 5.
Flags: needinfo?(alchen)
Comment 7•10 years ago
|
||
Hi Kusaba-san, could you follow comment #5 to enable network location service on stingray TV?
Flags: needinfo?(938.daisuke)
(In reply to Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz) from comment #7)
> Hi Kusaba-san, could you follow comment #5 to enable network location
> service on stingray TV?
This report said that geolocation access is not available on WebPage on WebBrowser of TV(stingray).
Just WebBrowser of TV(stingray) lacks "geolocation" permission in its manifest and after add it, geolocation is available as attached.
So will correct stingray browser app's manifest.
Flags: needinfo?(938.daisuke)
Comment 9•10 years ago
|
||
Great! I double checked the source code and confirmed the logic of using NetworkGeolocationProvider as a fallback. Good to know there is an easy fix for this issue. Feel free to provide the scheduled OTA date and close this bug.
Updated•10 years ago
|
Whiteboard: [ft:conndevices][partner-blocker]
Comment 10•10 years ago
|
||
Bug 1220066 opened for disabling this. We currently do not have Settings on TV.
Evelyn, any alternative before we have Settings on TV ready?
Flags: needinfo?(ehung)
Comment 11•10 years ago
|
||
One more question would be
"How do we use cursor on TV for permission confirmation?"
Comment 12•9 years ago
|
||
(In reply to Josh Cheng [:josh] from comment #11)
> One more question would be
> "How do we use cursor on TV for permission confirmation?"
Permission prompt UI has been TV optimized in bug 1217765.
Let's add permission to browser app and let QA verify it on TV. For settings problem, we have no alternative solution and System will remember the first answer from the user. It's a bug but I feel it shouldn't be a blocker to prevent us supporting this API.
Assign to yifan to add geolocation permission for browser app.
Assignee: nobody → yliao
Flags: needinfo?(ehung)
Whiteboard: [ft:conndevices][partner-blocker] → [ft:conndevices][partner-blocker][partner-cherry-pick]
Comment 13•9 years ago
|
||
| Assignee | ||
Comment 15•9 years ago
|
||
Comment on attachment 8705047 [details] [review]
[gaia] begeeben:1195211_geolocation_api > mozilla-b2g:master
Thanks!
Attachment #8705047 -
Flags: review?(ehung)
Comment 16•9 years ago
|
||
Comment on attachment 8705047 [details] [review]
[gaia] begeeben:1195211_geolocation_api > mozilla-b2g:master
Thanks!!!
Attachment #8705047 -
Flags: review?(ehung) → review+
Comment 17•9 years ago
|
||
merged into master:
https://github.com/mozilla-b2g/gaia/commit/2fd4e124028226668fe50228801df424632a29ce
Please request a? for uplift. Thanks.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 18•9 years ago
|
||
Comment on attachment 8705047 [details] [review]
[gaia] begeeben:1195211_geolocation_api > mozilla-b2g:master
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
[User impact] if declined: Geolocation API will fail to provide the position to requests on the TV broser
[Testing completed]: https://treeherder.mozilla.org/#/jobs?repo=gaia&revision=75b757ed4341bee0e2f905c50c5a4f8a965f1502
[Risk to taking this patch] (and alternatives if risky): none
[String changes made]: none
Attachment #8705047 -
Flags: approval-gaia-v2.5?
Updated•9 years ago
|
status-b2g-v2.5:
--- → affected
status-b2g-master:
--- → fixed
Comment 19•9 years ago
|
||
Comment on attachment 8705047 [details] [review]
[gaia] begeeben:1195211_geolocation_api > mozilla-b2g:master
Approve for 2.5
Attachment #8705047 -
Flags: approval-gaia-v2.5? → approval-gaia-v2.5+
Comment 20•9 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•