Tracking bug for build and release of SeaMonkey 2.53.7 Final
Categories
(SeaMonkey :: Release Engineering, task)
Tracking
(Not tracked)
People
(Reporter: frg, Assigned: frg)
References
Details
(Whiteboard: SM2.53.7)
Attachments
(2 files)
(deleted),
patch
|
frg
:
review+
frg
:
approval-comm-release+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
frg
:
review+
frg
:
approval-comm-release+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1686851 +++
This is a tracking bug for Build and Release of the SeaMonkey 2.53.7 final.
Assignee | ||
Comment 1•4 years ago
|
||
comm-release 2.53.7 version change r/a=me
Assignee | ||
Comment 2•4 years ago
|
||
mozilla-release 2.53.7 version change r/a=me
Comment 3•4 years ago
|
||
Snce the backport of bug #1390106, part3, the obsoleting "for each" javascript statement no more work.
The reason is the backport changes default version from JSVERSION_LATEST to JSVERSION_DEFAULT (with a value of zero), at it leads to the check always fail.
Since the code for "for each" still remains there, and it seems there are such extensions still used by SM users, it could be better to preserve the "for each" support, at least for a while. It could be done by either (partially) reverting that backport, or fix the check to no more use versions at all.
This one fixes the issue:
--- mozilla/js/src/frontend/Parser.h.orig 2020-08-10 14:30:34.000000000 +0300
+++ mozilla/js/src/frontend/Parser.h 2021-04-02 01:18:40.009761383 +0300
@@ -247,7 +247,7 @@ class ParserBase : public StrictModeGett
#if !JS_HAS_FOR_EACH_IN
return false;
#else
- return options().forEachStatementOption && versionNumber() >= JSVERSION_1_6;
+ return options().forEachStatementOption;
#endif
}
Assignee | ||
Comment 4•4 years ago
|
||
See you in 2.53.7.1 and 2.53.8b1
Description
•