The same thing might also be true for new js keywords.
This has been fixed upstream.
We need a new bug about updating our Orion code from upstream.
We should aim to have more of their upstream features. Also, we should look into using stable releases - their next stable release (milestone 0.3), which is scheduled for late October.
I have filed bug 692807 about updating our Orion code from upstream.
I am now going through the Orion/Source Editor/Scratchpad bug reports we have to triage them and compare against the latest upstream Orion code I have locally. (patience please with the bugzilla spam :) )
Confirmed. This is fixed upstream.
This is now fixed. Bug 692807 landed.
This is VERIFIED on Build identifier: Mozilla/5.0 (X11; Linux i686; rv:10.0a1) Gecko/20111107 Firefox/10.0a1
(In reply to Alex Lakatos from comment #7)
> This is VERIFIED on Build identifier: Mozilla/5.0 (X11; Linux i686;
> rv:10.0a1) Gecko/20111107 Firefox/10.0a1
> Also, checked all keywords from
> they are highlighted. Am I missing some keywords that should be highlighted?
Hopefully not. Thank you for your testing!