New issue
Advanced search Search tips

Issue 733481 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Should we be able to use conditional interface?

Project Member Reported by peria@chromium.org, Jun 15 2017

Issue description

With https://chromium.googlesource.com/chromium/src.git/+/0ac2b97eb15689ba196f7f88b184b3a17f13d30d , we got an inconsistent situation.
-----
interface Window {
   attribute DOMMatrixConstructor WebKitCSSMatrix;
}

[RuntimeEnabled=GeometryInterfaces]
interface DOMMatrix : ... {}
-----

In this case, we can use V8DOMMatrix feature via WebKitCSSMatrix even if we do not enable the feature GeometryInterfaces.

How should we do for it?
 
First, I think that it's a reasonable situation that we don't want to expose window.DOMMatrix, but we do want to expose window.WebKitCSSMatrix.  In general, it's reasonable that we'd like to expose only WebKitFoo without exposing Foo itself.

Having said that, the syntax used in the report (#0) seems not so good.  There would be room to improve it.  Also, it's good to have consistency check in the bindings generator.

Blocking: 734296
Blocking: -734296
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 22 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

Comment 5 by peria@chromium.org, Jun 25 2018

Status: Available (was: Untriaged)
Status: Assigned (was: Available)
Status: WontFix (was: Assigned)

Sign in to add a comment