Closed
Bug 352748
Opened 18 years ago
Closed 18 years ago
Can't use JS 1.7 let/yield in JS components
Categories
(Core :: XPConnect, defect, P2)
Core
XPConnect
Tracking
()
VERIFIED
FIXED
mozilla1.8.1
People
(Reporter: nanto, Assigned: brendan)
Details
(Keywords: verified1.8.1)
Attachments
(1 file)
1.09 KB,
patch
|
jst
:
review+
jst
:
superreview+
mtschrep
:
approval1.8.1+
|
Details | Diff | Splinter Review |
Confirmed in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060914 Minefield/3.0a1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060914 BonEcho/2.0
It seems that this bug is fixed in ZAP_20050610_BRANCH.
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/js/src/xpconnect/loader/mozJSComponentLoader.cpp&rev=1.105.2.19&root=/cvsroot#460
Reporter | ||
Comment 1•18 years ago
|
||
I checked all the XPIs under http://releases.mozilla.org/pub/mozilla.org/extensions/ and no JS component in them uses let or yield as a variable name. Flashgot 0.5.96 uses yield as a method name but it is treated as an identifier because it appears in an object initialiser. So I think the risk of enabling JS 1.7 in JS components is low, or zero if only using extensions provided in addons.mozilla.org.
Now there is no way to use JS 1.7 let/yield in JS components. Why not make JS 1.7 a new feature of Firefox 2 for extension developers?
Flags: blocking1.8.1?
Assignee | ||
Comment 2•18 years ago
|
||
Sorry, I lost track of this amid all the decompiler fixing. We should fix this in an RC3 if there is an RC3. Patch in a few, could use testing help.
/be
Assignee: dbradley → brendan
Assignee | ||
Comment 3•18 years ago
|
||
Attachment #241394 -
Flags: review?(jst)
Attachment #241394 -
Flags: approval1.8.1?
Comment 4•18 years ago
|
||
Comment on attachment 241394 [details] [diff] [review]
fix from the ZAP_20050610_BRANCH change
r+sr=jst
Attachment #241394 -
Flags: superreview+
Attachment #241394 -
Flags: review?(jst)
Attachment #241394 -
Flags: review+
Assignee | ||
Updated•18 years ago
|
Status: NEW → ASSIGNED
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → mozilla1.8.1
Assignee | ||
Comment 5•18 years ago
|
||
Fixed on the trunk:
Checking in mozJSComponentLoader.cpp;
/cvsroot/mozilla/js/src/xpconnect/loader/mozJSComponentLoader.cpp,v <-- mozJSComponentLoader.cpp
new revision: 1.127; previous revision: 1.126
done
/be
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•18 years ago
|
Severity: normal → major
Priority: -- → P2
Comment 6•18 years ago
|
||
(In reply to comment #2)
> Sorry, I lost track of this amid all the decompiler fixing. We should fix this
> in an RC3 if there is an RC3. Patch in a few, could use testing help.
Without this, is JS 1.7 actually implemented in a useful way in Firefox 2? I guess what I'm asking is, should this *cause* an RC3?
Comment 8•18 years ago
|
||
Comment on attachment 241394 [details] [diff] [review]
fix from the ZAP_20050610_BRANCH change
Approved for RC3.
Attachment #241394 -
Flags: approval1.8.1? → approval1.8.1+
Assignee | ||
Comment 9•18 years ago
|
||
Fixed on the 1.8 branch:
Checking in mozJSComponentLoader.cpp;
/cvsroot/mozilla/js/src/xpconnect/loader/mozJSComponentLoader.cpp,v <-- mozJSComponentLoader.cpp
new revision: 1.109.2.7; previous revision: 1.109.2.6
done
/be
Keywords: fixed1.8.1
Comment 10•18 years ago
|
||
nanto, can you verify that this is fixed on 1.8?
Reporter | ||
Comment 11•18 years ago
|
||
Verified fixed 1.8 2006101103 Windows, 1.9 2006101104 Windows.
Status: RESOLVED → VERIFIED
Keywords: fixed1.8.1 → verified1.8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•