Closed
Bug 418204
Opened 18 years ago
Closed 18 years ago
Wrong array behaviour
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: wolfram, Assigned: johnjbarton)
References
()
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_4_11; de-de) AppleWebKit/526+ (KHTML, like Gecko) Version/3.0.4 Safari/523.12.2
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3) Gecko/2008020511 Firefox/3.0b3
http://alex.dojotoolkit.org/?p=651
Reproducible: Always
Steps to Reproduce:
http://alex.dojotoolkit.org/?p=651
| Reporter | ||
Comment 1•18 years ago
|
||
it only occurs in Firefox3 beta3, FF2 it works as expected
Updated•18 years ago
|
Assignee: nobody → general
Component: General → JavaScript Engine
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → Trunk
Updated•18 years ago
|
Keywords: regression
Comment 2•18 years ago
|
||
WFM, latest JS source and in a trunk build that's less than a day old. I also downloaded b3 and ran the buggy code in the JavaScript shell, but I couldn't reproduce there either.
http://www.squarefree.com/shell/shell.html
Are you absolutely sure this is b3 and not b3+? There's been array hacking which conceivably could have temporarily broken this, but I believe most of the regressions have been fixed at this point (with only a threadsafety regression remaining?).
| Reporter | ||
Comment 3•18 years ago
|
||
I have tried it with Firebug and the site you posted and it fails in Firebug but works in the shell you posted, so it looks like a Firebug problem!
I keep investigating. Thanks for the help
| Assignee | ||
Comment 4•18 years ago
|
||
These problems were caused by evalInSandbox, which is no longer used in Firebug as of firebug 1.2a13X.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
| Assignee | ||
Updated•18 years ago
|
Assignee: general → johnjbarton
Status: ASSIGNED → NEW
| Assignee | ||
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•