New issue
Advanced search Search tips

Issue 600726 link

Starred by 4 users

Issue metadata

Status: Assigned
Merged: issue 546006
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

RuntimeEnabled is a no-op on enums

Project Member Reported by jbroman@chromium.org, Apr 5 2016

Issue description

Setting the RuntimeEnabled extended attribute on an enum definition seems to be legal with our bindings generator, but doesn't actually seem to do anything (presumably because the actual logic is done in dictionary members, properties and methods that take the enum).

Both approaches (making the enum RuntimeEnabled and not) now exist in Blink. It would be nice if we picked one or the other (e.g. by making specifying RuntimeEnabled on an enum an error).
 
(To be clear: both exist, but not marking enums as RuntimeEnabled is considerably more common.)
Cc: bashi@chromium.org

Comment 3 by joh...@chromium.org, Apr 18 2016

Mergedinto: 546006
Status: Duplicate (was: Untriaged)

Comment 4 by joh...@chromium.org, Apr 18 2016

Cc: dtapu...@chromium.org
Status: Untriaged (was: Duplicate)
Oops, this isn't actually a duplicate. cc'ing dtapuska who implemented this for dictionaries in  issue 441569 .
To be clear, I would argue this is an aspect of how RuntimeEnabled is treated on enums, rather than how it is treated on dictionaries.

Comment 6 by peria@chromium.org, Aug 25 2016

Owner: bashi@chromium.org
Status: Assigned (was: Untriaged)

Sign in to add a comment