New issue
Advanced search Search tips

Issue 674576 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Add support for IDL Error type in Blink bindings

Project Member Reported by mikhail....@intel.com, Dec 15 2016

Issue description

At the moment Blink IDL bindings are missing support for 'Error' type (https://heycam.github.io/webidl/#idl-Error)
 
Status: Available (was: Untriaged)
Is there a feature that wishes to use this, but it doesn't exist, or is this request simply for completeness?

Marking as Pri-3 Available unless there are clients that are blocked on, or working around, this feature.
This type is present at https://w3c.github.io/sensors/#the-sensor-error-event-interface which is being implemented in Chromium.
Good to know. I'm slightly unsure how we'll end up implemented this, as it's complicated by isolated worlds.

Specifically, if you give a non-DOMException object, what should the V8 object be when you access it in a different world? Undefined? A proxy/membrane (which we don't implement)? A shallow copy?

Leaving at Pri-3 for now, but probably it becomes Pri-2 if sensor is blocking on it.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 16 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: peria@chromium.org yukishiino@chromium.org
Status: Available (was: Untriaged)
bumping back to available; not clear that much has changed here, but ccing a couple TOK bindings people who may have opinions

Comment 6 by peria@chromium.org, Apr 26 2018

Status: WontFix (was: Available)
IIRC, all used Error types were replaced with DOMException, and we no longer have cases of Error types, and we decided to support only DOMException interface directly.

Sign in to add a comment