New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 716007 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 701457


Participants' hotlists:
Hotlist-Bindings-IDLCompiler


Sign in to add a comment

Allow partial interfaces to be implemented as different classes in different modules

Project Member Reported by zakerinasab@chromium.org, Apr 27 2017

Issue description

To fix  crbug.com/701457 , we need multiple partial interfaces of WindowOrWorkerGlobalScope implemented as different classes in different modules. The binding relations are similar to this:

* In Window.idl:
Window implements WindowOrWorkerGlobalScope;

* In WorkerGlobalScope.idl:
WorkerGlobalScope implements WindowOrWorkerGlobalScope

* In modules/module1/WindowOrWorkerGlobalScopeModule1.idl:
[ImplementedAs=Module1
] partial interface WindowOrWorkerGlobalScope {
...};

* In modules/module2/WindowOrWorkerGlobalScopeModule2.idl:
[ImplementedAs=Module2
] partial interface WindowOrWorkerGlobalScope {
...};

etc. This seems to be an edge case which is not supported by the current binding engine.
 

Comment 1 Deleted

Comment 2 Deleted

Cc: -junov@chromium.org
Cc: bashi@chromium.org
Owner: peria@chromium.org
Assigning to peria@ to make sure his new code generator takes care of this usage.
Labels: Hotlist-Bindings-IDLCompiler

Sign in to add a comment