[Bug 18255] I don't think [TreatNonCallableAsNull] is necessary on this callback, since if a non-Function is passed it will be converted to a string according to the other overload. That DOMString overload also doesn't need [AllowAny] as that is now the default beha

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18255

Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2012-09-28 05:10: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: applied patch
https://github.com/w3c/html/commit/13c2afbc650cca54c0d3ff3eeae29882c7254485
Rationale: adopted resolution by WHATWG

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 28 September 2012 05:10:45 UTC