[Webkit-unassigned] [Bug 183523] New: ClassExprNode evaluation of computed property names differs observably from spec and other implementations
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Mar 9 13:09:01 PST 2018
https://bugs.webkit.org/show_bug.cgi?id=183523
Bug ID: 183523
Summary: ClassExprNode evaluation of computed property names
differs observably from spec and other implementations
Product: WebKit
Version: Safari Technology Preview
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: JavaScriptCore
Assignee: webkit-unassigned at lists.webkit.org
Reporter: caitp at igalia.com
https://jsfiddle.net/kposmd21/ is an example reproduction.
WebKit produces:
```
name(2)
name(1)
name(3)
name1 called
name2 called
name3 called
```
while Chrome and FireFox produce:
```
name(1)
name(2)
name(3)
name1 called
name2 called
name3 called
```
----
The spec indicates that Chrome and FF's behaviour is correct here.
This becomes even more potentially weird with the introduction of class fields, in https://bugs.webkit.org/show_bug.cgi?id=174212 --- class elements should be evaluated in order, regardless of whether or not they are methods or class fields, and regardless of whether or not they are static or belong on the instance.
--
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/20180309/6068998c/attachment.html>
More information about the webkit-unassigned
mailing list