Remove RaisesException from getCurrentPosition and watchPosition

According to Geolocation API specification getCurrentPosition and
watchPosition does not raise exception, and current RaisesException
for them in the Geolocation.idl are meaningless Because it never
affect to generating bindings codes at all. Therefore we do not
need to keep them in that idl.

BUG=368184

Review URL: https://codereview.chromium.org/297353002

git-svn-id: svn://svn.chromium.org/blink/trunk@175133 bbb929c8-8fbe-4397-9dbb-9b2b20218538
parent 56ff8e3f
......@@ -28,13 +28,13 @@
WillBeGarbageCollected,
NoInterfaceObject,
] interface Geolocation {
// FIXME: should be: PositionOptions options (need PositionOptions.idl)
[RaisesException, Custom, PerWorldBindings, LogActivity] void getCurrentPosition(PositionCallback successCallback,
// FIXME: should be: PositionOptions options: need PositionOptions.idl and dictionary http:/crbug.com/321462
[Custom, PerWorldBindings, LogActivity] void getCurrentPosition(PositionCallback successCallback,
optional PositionErrorCallback errorCallback,
optional object options);
// FIXME: should be: PositionOptions options (need PositionOptions.idl)
[RaisesException, Custom, PerWorldBindings, LogActivity] long watchPosition(PositionCallback successCallback,
// FIXME: should be: PositionOptions options: need PositionOptions.idl and dictionary http:/crbug.com/321462
[Custom, PerWorldBindings, LogActivity] long watchPosition(PositionCallback successCallback,
optional PositionErrorCallback errorCallback,
optional object options);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment