Oops, I mixed up the actual results and expected results. I meant this: Actual Results: Syntax errors. Expected Results: Code runs fine.
I believe what you are seeing is compatibility mode, only the features that could break content have been disabled. To maintain compatibility, no new keywords can be added.
Thanks for the report! This is actually due to bug 445873, which is fixed in Firefox 3.1 but will never make it to 3.0, which is what sephr is using. (This actually used to be a Ubiquity bug, so it's quite well-known.) Because Firefox 3.5 is coming out pretty soon, we're just going to have to say that Jetpacks which use let/yield won't work on FF 3.0, but they will on 3.5; eventually this annoyance will become irrelevant. If it's likely that folks will continue to use 3.0 well after 3.5 is launched, though, we could add an "apology" that detects when a parsing error occurs due to a let/yield statement and tells the end-user that the Jetpack only works on 3.5? We should probably file a separate bug for that if so.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 445873
You need to log in before you can comment on or make changes to this bug.