View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002080 | Composr | core | public | 2015-11-18 02:11 | 2021-03-15 16:54 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002080: Hide geolocation features on non-SSL for some browsers | ||||
| Description | Google has deprecated geolocation outside SSL. Very long discussion: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/2LXKVWYkOus%5B151-175%5D It's not turned off yet, may not be for years, but it will be at some point. We need to be able to do {$BROWSER_MATCHES,geolocation_available} which would check to see if we can do it, before enabling UI for it. It would look at the browser and look to see if it is SSL. We need to document this somewhere also. | ||||
| Additional Information | No action yet, until Google really does something. Still actively being discussed. | ||||
| Tags | Type: Standards compliance | ||||
| Time estimation (hours) | 5 | ||||
| Sponsorship open | |||||
|
|
Removed way back now in the two main browser engines... Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1072859 Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=561641 So if we implement this we don't need to use BROWSER_MATCHES at all, we just assume only https can do geolocation. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-08 12:17 | Chris Graham | Tag Attached: Type: Standards compliance | |
| 2021-03-15 16:54 | Chris Graham | Note Added: 0007007 |
