ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly
jamesr
FrameRequestCallback interface should be designated as Callback=FunctionOnly
- State:
- CLOSED
- Product:
- Request Animation Frame
- Raised by:
- Jatinder Mann
- Opened on:
- 2011-06-01
- Description:
- Unless explicitly specified with a Callback=FunctionOnly statement in the IDL, we will be allowing objects to be registered as callbacks, like so:
E.g.
var obj = new Object();
obj.handleEvent = function (event) { alert (‘hello, world!’); }
window.requestAnimationFrame(obj);
Registering objects as callbacks is somewhat uncommon and may not be what we want. The Geolocation PositionCallback function, http://dev.w3.org/geo/api/spec-source.html, also explicitly calls out that the callback be a function only.
The change would look like so:
[Callback=FunctionOnly, NoInterfaceObject]
interface FrameRequestCallback {
void sample(in DOMTimeStamp time);
};
- Related Actions Items:
- No related actions
- Related emails:
- [minutes] 20110706 Web Performance WG Teleconference #40 (from jmann@microsoft.com on 2011-07-06)
- [minutes] 20110629 Web Performance WG Teleconference #39 (from jmann@microsoft.com on 2011-06-30)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from cam@mcc.id.au on 2011-06-28)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from slightlyoff@google.com on 2011-06-28)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from cam@mcc.id.au on 2011-06-27)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from bzbarsky@MIT.EDU on 2011-06-08)
- RE: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from Savil.Srivastava@microsoft.com on 2011-06-08)
- RE: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from pettay@mappi.helsinki.fi on 2011-06-02)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from bzbarsky@MIT.EDU on 2011-06-02)
- Re: [minutes] 20110601 Web Performance WG Teleconference #35 (from getify@gmail.com on 2011-06-02)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from cam@mcc.id.au on 2011-06-02)
- [minutes] 20110601 Web Performance WG Teleconference #35 (from jmann@microsoft.com on 2011-06-02)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from cam@mcc.id.au on 2011-06-02)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from cam@mcc.id.au on 2011-06-02)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from Olli.Pettay@helsinki.fi on 2011-06-02)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from cam@mcc.id.au on 2011-06-02)
- RE: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from Savil.Srivastava@microsoft.com on 2011-06-01)
- RE: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from Savil.Srivastava@microsoft.com on 2011-06-01)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from bzbarsky@MIT.EDU on 2011-06-01)
- Re: ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from bzbarsky@MIT.EDU on 2011-06-01)
- ISSUE-7: FrameRequestCallback interface should be designated as Callback=FunctionOnly [Request Animation Frame] (from sysbot+tracker@w3.org on 2011-06-01)
Related notes:
We resolved to leave this text unchanged.
James Robinson, 6 Jul 2011, 21:29:59Display change log