- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Apr 2015 18:06:46 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28583
Bug ID: 28583
Summary: Inherited method name conflicts with consequential
maplike/setlike interfaces should fail
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: WebIDL
Assignee: cam@mcc.id.au
Reporter: kyle@nonpolynomial.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-script-coord@w3.org
Consider the following interface:
interface Foo1 {
maplike<long, long>;
};
interface Foo2 {
void entries();
};
interface Foo3 : Foo2 {
};
Foo3 implements Foo1;
Currently, this interface passes. However, if the maplike were directly on
Foo3, it would fail. The spec should probably make sure this fails, too.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 29 April 2015 18:06:53 UTC