Couldn't reproduce these issues in a clean profile so it's definitely
extensions interfering.
Could you iterate through the extensions (turn off half at a time to narrow
down) and let us know?
-steve--
--
You received this message because you are subscribed to the Google Groups
I just finished doing that in a new profile and firebug was still
working. :/
My main profile has been in use for a long time and lived through a
lot of nightly and local builds, maybe it's time to start a new one.
From what I could tell, the following expression was triggering the
Trace message
I thought I posted something yesterday but it hasn't showed up...
Anyway, Most of these errors are due to not being able to expand
objects through the [+] sign in the DOM tab.
It just changes to [-] but nothing else happens.
Tracing shows this error:
errors.getErrorContext; ERROR wrong parent
I think this problem is related to Firefox 4.0 async jsd support which
we have not completely dealt with. I believe the function is correct
but the UI does not update correctly yet. Because it is async the
time for update can come before or after the test harness checks the
value.
[FAILED] dom/storage/storage.js: DOM Storage
- Fixed in Firebug (jjb)
[FAILED] console/api/count.js: Test for console.count API
- See https://bugzilla.mozilla.org/show_bug.cgi?id=573875
- Fixed in Firebug (workaround, Honza)
Honza
On Jan 12, 2:35 pm, Honza (Jan Odvarko) odva...@gmail.com wrote:
