This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14761 - Drop =FunctionOnly from everywhere else than interface Function
Summary: Drop =FunctionOnly from everywhere else than interface Function
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
: 14756 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-10 11:50 UTC by Olli Pettay
Modified: 2011-11-11 00:01 UTC (History)
4 users (show)

See Also:


Attachments

Description Olli Pettay 2011-11-10 11:50:35 UTC

    
Comment 1 Ian 'Hixie' Hickson 2011-11-10 23:57:43 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: By "everywhere" I assume you just mean FunctionStringCallback, part of the new drag-and-drop API.
Comment 2 contributor 2011-11-10 23:58:04 UTC
Checked in as WHATWG revision r6821.
Check-in comment: Allow people to pass an object to the drag-and-drop string callback so that they can store information in the callback object rather than using a closure, since apparently closures are too confusing.
http://html5.org/tools/web-apps-tracker?from=6820&to=6821
Comment 3 Ian 'Hixie' Hickson 2011-11-11 00:01:05 UTC
*** Bug 14756 has been marked as a duplicate of this bug. ***