Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Callbacks functions don't have a handleEvent operation #24

Closed
foolip opened this issue Feb 14, 2019 · 0 comments · Fixed by #39
Closed

Callbacks functions don't have a handleEvent operation #24

foolip opened this issue Feb 14, 2019 · 0 comments · Fixed by #39

Comments

@foolip
Copy link
Member

foolip commented Feb 14, 2019

http://w3c.github.io/geolocation-api/#dom-navigatorgeolocation-getcurrentposition says:

If the attempt is successful, the successCallback MUST be invoked (i.e. the handleEvent operation MUST be called on the callback object) with a new NavigatorGeolocationPosition object, reflecting the current location of the device.

However, the type definition of the callback is:

callback PositionCallback = void (NavigatorGeolocationPosition position);

This is a https://heycam.github.io/webidl/#idl-callback-functions. The spec wording has it confused with https://heycam.github.io/webidl/#dfn-callback-interface and in particular https://dom.spec.whatwg.org/#callbackdef-eventlistener.

https://heycam.github.io/webidl/#invoke-a-callback-function is the way to invoke callback functions, and https://dom.spec.whatwg.org/#notify-mutation-observers has an example of the phrasing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant