[Webkit-unassigned] [Bug 211597] New: Window/body/frameset onerror event handler should stringify to include all its parameters

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=211597

            Bug ID: 211597
           Summary: Window/body/frameset onerror event handler should
                    stringify to include all its parameters
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Bindings
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: d at domenic.me
                CC: cdumez at apple.com

A recent change to the ECMAScript spec forced the HTML spec to be explicit about what the source text of a compiled event handler is. That is, what is the value of things like div.onclick.toString() or document.body.onerror.toString(). The resulting HTML pull request is at https://github.com/whatwg/html/pull/5514.

It turns out that browsers mostly do the sensible thing here, and the resulting source text matches the list of arguments to the event handler in question. The exception is in Safari, which per the results of https://github.com/web-platform-tests/wpt/pull/23467 will output `function onerror(event) {\nfoo\n}` instead of `function onerror(event, source, lineno, colno, error) {\nfoo\n}` for window.onerror, body.onerror, and frameset.onerror, despite those functions taking 5 arguments.

So concretely, the goal is to pass the tests at https://github.com/web-platform-tests/wpt/pull/23467 by changing the stringification of onerror in those three cases. (But *not* changing it for cases like someDiv.onerror.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200507/b268dbcd/attachment.htm>