[Sensors] Fix error type and message used

[Sensors] Fix error type and message used

Before this change Sensor implementation used 'UnknownError' exception type (and the default message) to report errors from mojo proxies.
This led to the weird error messages like: "SensorErrorEvent {error: DOMException: An unknown error occurred within Indexed Database.,".

This patch uses 'NotReadableError' as described in the specification [1] and also simplifies the error handling code.

BUG=692559
[1] https://w3c.github.io/sensors

Review-Url: https://codereview.chromium.org/2699673002
Cr-Commit-Position: refs/heads/master@{#450741}
Committed: https://chromium.googlesource.com/chromium/src/+/064a292ce35b28592529c5bded26f905d65833a9

[Mikhail, 2017-02-15 15:25:45]

The CQ bit was checked by mikhail.pozdnyakov@intel.com to run a CQ dry run

[commit-bot: I haz the power, 2017-02-15 15:26:06]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Mikhail, 2017-02-15 15:27:21]

mikhail.pozdnyakov@intel.com changed reviewers:
+ alexander.shalamov@intel.com, haraken@chromium.org, reillyg@chromium.org

[Mikhail, 2017-02-15 15:27:22]

PTAL

[haraken, 2017-02-15 15:29:32]

LGTM on my side

[commit-bot: I haz the power, 2017-02-15 16:52:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-15 16:52:56]

Dry run: This issue passed the CQ dry run.

[Reilly Grant (use Gerrit), 2017-02-15 16:57:30]

lgtm

[Mikhail, 2017-02-15 17:22:21]

The CQ bit was checked by mikhail.pozdnyakov@intel.com

[commit-bot: I haz the power, 2017-02-15 17:23:17]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-15 17:35:47]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487179341023470, "parent_rev":
"015400e5f61ea871e81cae45fc648df19a50eee1", "commit_rev":
"064a292ce35b28592529c5bded26f905d65833a9"}

[commit-bot: I haz the power, 2017-02-15 17:36:23]

Description was changed from

==========
[Sensors] Fix error type and message used

Before this change Sensor implementation used 'UnknownError' exception type (and
the default message) to report errors from mojo proxies.
This led to the weird error messages like: "SensorErrorEvent {error:
DOMException: An unknown error occurred within Indexed Database.,".

This patch uses 'NotReadableError' as described in the specification [1] and
also simplifies the error handling code.

BUG=692559

[1] https://w3c.github.io/sensors
==========

to

==========
[Sensors] Fix error type and message used

Before this change Sensor implementation used 'UnknownError' exception type (and
the default message) to report errors from mojo proxies.
This led to the weird error messages like: "SensorErrorEvent {error:
DOMException: An unknown error occurred within Indexed Database.,".

This patch uses 'NotReadableError' as described in the specification [1] and
also simplifies the error handling code.

BUG=692559

[1] https://w3c.github.io/sensors

Review-Url: https://codereview.chromium.org/2699673002
Cr-Commit-Position: refs/heads/master@{#450741}
Committed:
https://chromium.googlesource.com/chromium/src/+/064a292ce35b28592529c5bded26...
==========

[commit-bot: I haz the power, 2017-02-15 17:36:25]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/064a292ce35b28592529c5bded26...