Intent to Prototype and Ship: toJSON for GeolocationCoordinates and GeolocationPosition

271 views
Skip to first unread message

Reilly Grant

unread,
Apr 16, 2024, 1:36:24 PMApr 16
to blink-dev

Contact emails

rei...@chromium.org


Explainer

None


Specification

https://github.com/w3c/geolocation-api/pull/147 (merged but blocked on a publishing error)


Summary

Add .toJSON() methods to the GeolocationCoordinates and GeolocationPosition interfaces.


These methods will aid in developing automated tests for the Geolocation API and may be useful for debugging as well. If the API were developed today, these WebIDL interfaces would likely be WebIDL dictionaries instead. However, given compatibility constraints, this is the next best option for making these types serializable.



Blink component

Blink>Geolocation


TAG review

None


TAG review status

Not applicable


Risks



Interoperability and Compatibility

None



Gecko: Positive (https://github.com/w3c/geolocation-api/pull/147#issuecomment-2048035042) 👍 from @saschanaz.


WebKit: Positive (https://github.com/w3c/geolocation-api/pull/147#issue-2232542989) Implemented in WebKit.


Web developers: No signals


Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None.



Debuggability

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes


Is this feature fully tested by web-platform-tests?

Yes


Flag name on chrome://flags

None


Finch feature name

None


Non-finch justification

Trivial addition of an accessor method.



Requires code in //chrome?

False


Estimated milestones

Shipping on desktop

126


Shipping on Android

126


Shipping on WebView

126




Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

None.


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5606741606924288


This intent message was generated by Chrome Platform Status.

Reilly Grant | Software Engineer | rei...@chromium.org | Google Chrome

slightlyoff via Chromestatus

unread,
Apr 16, 2024, 2:02:55 PMApr 16
to blin...@chromium.org
LGTM1

Mike Taylor

unread,
Apr 16, 2024, 2:37:41 PMApr 16
to blin...@chromium.org

LGTM2 - seems like a trivial, useful addition.

On 4/16/24 2:02 PM, slightlyoff via Chromestatus wrote:
LGTM1
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0000000000008c8a3f06163a8bf3%40google.com.

Domenic Denicola

unread,
Apr 16, 2024, 8:57:49 PMApr 16
to Mike Taylor, blin...@chromium.org
Reply all
Reply to author
Forward
0 new messages