[Webkit-unassigned] [Bug 149743] Function.toString.call(class Foo {}) doesn't say "class"

[bugzilla-daemon at webkit.org]

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

Saam Barati <sbarati at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sbarati at apple.com

--- Comment #4 from Saam Barati <sbarati at apple.com> ---
(In reply to comment #3)
> In that example - when the method is dynamically added - the "method"
> function absolutely wouldn't appear. If you define a function's name later,
> it doesn't affect its string representation.
> 
> While it's fine to wait, this means it's *impossible* to detect when a
> "class" was defined using "class" syntax, and also does not comply with how
> Chrome or Edge does it (although it does comply with how Firefox does it).
Why would you want to detect this?

> Waiting for the spec to define it isn't the worst idea, but Chrome and
> Edge's behavior will almost certainly become the standard - so it'd be nice
> if WebKit/Safari followed suit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151006/37ad10a4/attachment-0001.html>