W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2010

Fwd: [Bug 10337] New: add [Supplemental] support

From: Arthur Barstow <art.barstow@nokia.com>
Date: Tue, 10 Aug 2010 07:29:45 -0400
Message-ID: <4C613829.4060903@nokia.com>
To: public-script-coord <public-script-coord@w3.org>
-------- Original Message --------
Subject: 	[Bug 10337] New: add [Supplemental] support
Date: 	Tue, 10 Aug 2010 00:31:31 +0200
From: 	ext bugzilla@jessica.w3.org <bugzilla@jessica.w3.org>
To: 	public-webapps@w3.org <public-webapps@w3.org>



http://www.w3.org/Bugs/Public/show_bug.cgi?id=10337

            Summary: add [Supplemental] support
            Product: WebAppsWG
            Version: unspecified
           Platform: PC
         OS/Version: All
             Status: NEW
           Severity: normal
           Priority: P2
          Component: WebIDL
         AssignedTo: cam@mcc.id.au
         ReportedBy: ian@hixie.ch
          QAContact: member-webapi-cvs@w3.org
                 CC: mike@w3.org, public-webapps@w3.org


For specification process reasons, some interface  definitions don't get
organised the same way as we want from implementations. I've assumed that
[Supplemental] will exist, and used it as follows:

  - Setting [Supplemental, NoInterfaceObject] on an interface X with no
    ancestor and then saying:
      Y implements X;
    ...implies that the members in X are imported into Y as if the
    definition of Y always had X in it.

  - Setting [Supplemental, NoInterfaceObject] on an interface X that
    inherits from Y implies that there are objects called Y that have all
    the members of X and Y with X not appearing on the prototype chain.

  - Setting [Supplemental] on an interface that has the same name as an
    interface definition without [Supplemental].

The distinction between these cases is that I have three different cases
where I need to do this. One is where I have some objects, e.g. Window,
that are made up of APIs defined in other specs, and those APIs are also
used by other interfaces. So I define Window, and then other specs slide
stuff into Window, and slide stuff into other interfaces (like Worker-
related ones). Another is WorkerGlobalScope, which I want to be the name
of the interface implementing the global scope for workers, but there are
two types of workers, and they have slightly different interfaces. And the
third is the deprecated interfaces, where one interface, e.g.
HTMLAnchorElement, is defined in two places.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 10 August 2010 11:30:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:03 UTC