<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Function.toString.call(class Foo {}) doesn't say "class""
href="https://bugs.webkit.org/show_bug.cgi?id=149743#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Function.toString.call(class Foo {}) doesn't say "class""
href="https://bugs.webkit.org/show_bug.cgi?id=149743">bug 149743</a>
from <span class="vcard"><a class="email" href="mailto:ljharb@gmail.com" title="Jordan Harband <ljharb@gmail.com>"> <span class="fn">Jordan Harband</span></a>
</span></b>
<pre>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).
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>