W3C Feature (GeoLocation) Deprecation timelines
Now that W3C have officially deprecated the GeoLocation API
How long do we have before our existing navigator.geolocation code stops working?
Is there some feature/API retirement that we can refer to as an example?
Most importantly who approved this? #GeoLocationIsNotaSensor! Sorry I take that back, MOST importantly who ask for a GeoLocation Sensor?
deprecated w3c-geolocation
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
add a comment |
Now that W3C have officially deprecated the GeoLocation API
How long do we have before our existing navigator.geolocation code stops working?
Is there some feature/API retirement that we can refer to as an example?
Most importantly who approved this? #GeoLocationIsNotaSensor! Sorry I take that back, MOST importantly who ask for a GeoLocation Sensor?
deprecated w3c-geolocation
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
That warning links from Draft 11 to Draft 12 in a new location on w3c.github.io, where only the path changed, fromgeolocation-apitogeolocation-sensor. Where are you reading that this has been deprecated?
– Martijn Pieters♦
Nov 15 '18 at 10:36
If you are worried about the change in API when writing code using the old draft, first of all, this was a draft so is subject to change until final, and second, just test if the oldnavigator.geolocationattribute exists. If not, use the new sensor API to get a current position or use the promised-based read API to receive event callbacks.
– Martijn Pieters♦
Nov 15 '18 at 10:57
add a comment |
Now that W3C have officially deprecated the GeoLocation API
How long do we have before our existing navigator.geolocation code stops working?
Is there some feature/API retirement that we can refer to as an example?
Most importantly who approved this? #GeoLocationIsNotaSensor! Sorry I take that back, MOST importantly who ask for a GeoLocation Sensor?
deprecated w3c-geolocation
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
Now that W3C have officially deprecated the GeoLocation API
How long do we have before our existing navigator.geolocation code stops working?
Is there some feature/API retirement that we can refer to as an example?
Most importantly who approved this? #GeoLocationIsNotaSensor! Sorry I take that back, MOST importantly who ask for a GeoLocation Sensor?
deprecated w3c-geolocation
deprecated w3c-geolocation
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
edited Nov 15 '18 at 10:47
Martijn Pieters♦
724k14125422346
724k14125422346
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
asked Nov 15 '18 at 5:50
McMurphyMcMurphy
4751619
4751619
That warning links from Draft 11 to Draft 12 in a new location on w3c.github.io, where only the path changed, fromgeolocation-apitogeolocation-sensor. Where are you reading that this has been deprecated?
– Martijn Pieters♦
Nov 15 '18 at 10:36
If you are worried about the change in API when writing code using the old draft, first of all, this was a draft so is subject to change until final, and second, just test if the oldnavigator.geolocationattribute exists. If not, use the new sensor API to get a current position or use the promised-based read API to receive event callbacks.
– Martijn Pieters♦
Nov 15 '18 at 10:57
add a comment |
That warning links from Draft 11 to Draft 12 in a new location on w3c.github.io, where only the path changed, fromgeolocation-apitogeolocation-sensor. Where are you reading that this has been deprecated?
– Martijn Pieters♦
Nov 15 '18 at 10:36
If you are worried about the change in API when writing code using the old draft, first of all, this was a draft so is subject to change until final, and second, just test if the oldnavigator.geolocationattribute exists. If not, use the new sensor API to get a current position or use the promised-based read API to receive event callbacks.
– Martijn Pieters♦
Nov 15 '18 at 10:57
That warning links from Draft 11 to Draft 12 in a new location on w3c.github.io, where only the path changed, from
geolocation-api to geolocation-sensor. Where are you reading that this has been deprecated?– Martijn Pieters♦
Nov 15 '18 at 10:36
That warning links from Draft 11 to Draft 12 in a new location on w3c.github.io, where only the path changed, from
geolocation-api to geolocation-sensor. Where are you reading that this has been deprecated?– Martijn Pieters♦
Nov 15 '18 at 10:36
If you are worried about the change in API when writing code using the old draft, first of all, this was a draft so is subject to change until final, and second, just test if the old
navigator.geolocation attribute exists. If not, use the new sensor API to get a current position or use the promised-based read API to receive event callbacks.– Martijn Pieters♦
Nov 15 '18 at 10:57
If you are worried about the change in API when writing code using the old draft, first of all, this was a draft so is subject to change until final, and second, just test if the old
navigator.geolocation attribute exists. If not, use the new sensor API to get a current position or use the promised-based read API to receive event callbacks.– Martijn Pieters♦
Nov 15 '18 at 10:57
add a comment |
1 Answer
1
active
oldest
votes
There is no mention of deprecation whatsoever in the page you linked to.
What this warning box says is that the specification of this API has been moved to an other working group, Geolocation Sensor.
So given they even created an entire working group for this API, I'd bet it's not going to get away of browsers' implementations any time soon, but future can prove me wrong...
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
2
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
add a comment |
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53313193%2fw3c-feature-geolocation-deprecation-timelines%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no mention of deprecation whatsoever in the page you linked to.
What this warning box says is that the specification of this API has been moved to an other working group, Geolocation Sensor.
So given they even created an entire working group for this API, I'd bet it's not going to get away of browsers' implementations any time soon, but future can prove me wrong...
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
2
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
add a comment |
There is no mention of deprecation whatsoever in the page you linked to.
What this warning box says is that the specification of this API has been moved to an other working group, Geolocation Sensor.
So given they even created an entire working group for this API, I'd bet it's not going to get away of browsers' implementations any time soon, but future can prove me wrong...
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
2
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
add a comment |
There is no mention of deprecation whatsoever in the page you linked to.
What this warning box says is that the specification of this API has been moved to an other working group, Geolocation Sensor.
So given they even created an entire working group for this API, I'd bet it's not going to get away of browsers' implementations any time soon, but future can prove me wrong...
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
There is no mention of deprecation whatsoever in the page you linked to.
What this warning box says is that the specification of this API has been moved to an other working group, Geolocation Sensor.
So given they even created an entire working group for this API, I'd bet it's not going to get away of browsers' implementations any time soon, but future can prove me wrong...
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
answered Nov 15 '18 at 8:40
KaiidoKaiido
45.1k467108
45.1k467108
2
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
add a comment |
2
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
2
2
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
Yeah, I was a bit puzzled by this question. The Devices and Sensors Working Group is even a W3C Working Group! If anything the spec has been promoted, not deprecated, since the original document came from a W3C Community Group. (I'm a member of another W3C Community Group, so I'm somewhat familiar with how this works.)
– BoltClock♦
Nov 15 '18 at 8:41
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53313193%2fw3c-feature-geolocation-deprecation-timelines%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
That warning links from Draft 11 to Draft 12 in a new location on w3c.github.io, where only the path changed, from
geolocation-apitogeolocation-sensor. Where are you reading that this has been deprecated?– Martijn Pieters♦
Nov 15 '18 at 10:36
If you are worried about the change in API when writing code using the old draft, first of all, this was a draft so is subject to change until final, and second, just test if the old
navigator.geolocationattribute exists. If not, use the new sensor API to get a current position or use the promised-based read API to receive event callbacks.– Martijn Pieters♦
Nov 15 '18 at 10:57