Yes, it could be a collision with another extension: Would it be possible to manually verify following tests? dom/3597/issue3597.html dom/2772/issue2772.html dom/breakpoints/breakOnProperty.html dom/breakpoints/breakOnProperty.html dom/1738/main.html script/debuggerKeyword/testPage.html
You need to just right click on a test in the Test console and pick "Open test page" The test page contains detailed description of what to do to execute the test. Thanks! Honza On Jan 12, 10:41 pm, Jorge Alves <jag.al...@gmail.com> wrote: > Ran the test suite and here are my > results:http://getfirebug.com/testresults/?userheaderid=ad7fd2ee957d09c7c1481... > > Got a few more failures maybe because of my extensions? Ghostery is > known to cause problems. > > Both Firebug and FBTest are r8916, btw. > > Thanks for your efforts. :) > > On Jan 12, 4:58 pm, "Honza (Jan Odvarko)" <odva...@gmail.com> wrote: > > > [FAILED] dom/storage/storage.js: DOM Storage > > - Fixed in Firebug (jjb) > > > [FAILED] console/api/count.js: Test for console.count API > > - Seehttps://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: > > > > I have spent some with testing Firebug 1.7 on Firefox 4 (trunk build) > > > and here are some preliminary results: > > > > Firefox 4.0b10per (2011-01-11), built > > > fromhttp://hg.mozilla.org/mozilla-central/rev/4413ed6ba5a5 > > > >http://getfirebug.com/testresults/?userheaderid=1d2bdcae68748c40bbb80... > > > > [FAILED] firebug/openDisableEnableReload.js: Firebug opened disabled > > > on all panels then enabled on all panels > > > [FAILED] firebug/closeOpenOpenSwitchTabsTwice.js: Switch between two > > > tabs, one Firebug, one not > > > [FAILED] console/3408/issue3408.js: Issue 3408: Console panel breaks > > > if Firebug is reactivated. > > > - These are still unstable tests. The problem is clearly in the test. > > > > [FAILED] dom/storage/storage.js: DOM Storage > > > - This one looks like a regression FB bug, I'll investigate more yet. > > > My feeling is that this is not platform bug. > > > > [FAILED] search/scriptPanelSearch.js: Search within the Script panel > > > - This looks like a broken test (fails in Fx3.6 too). Anybody > > > volunteers for fixing? > > > > [FAILED] lib/textSearch.js: Verify FBL.TextSearch > > > - Passes in Fx3.6, needs to be investigated. > > > > [FAILED] console/api/count.js: Test for console.count API. > > > - This one looks like a regression FB bug (manually fails in Fx3.6 > > > too). I'll investigate more. > > > > [FAILED] commandLine/dom.js: Verify command line DOM access. > > > - Looks like a regression FB bug (‘with(_FirebugCommandLine)’ > > > displayed in the console where it shouldn’t be). I'll investigate > > > more. > > > > [FAILED] commandLine/2934/issue2934.js: 1.6a7 console and auto- > > > complete (needs 'window.' prefix) > > > [FAILED] console/completion/3421/issue3421.js: Issue 3421: > > > Autocompletion expression parsing is wrong > > > [FAILED] console/completion/3394/issue3394.js: Issue 3394: TAB Key > > > does not finish > > > an autocomplete keyword in Gnome (Ubuntu) > > > - These auto-completion tests pass with 3.6, could be a Fx4 bug, needs > > > to be investigated. > > > > [FAILED] commandLine/debug.js: Verify command line debug API. > > > - This is reported problem with JSD (fails also in tracemonkey build). > > > I think it's the wrapper problem > > > here:https://bugzilla.mozilla.org/show_bug.cgi?id=624316 > > > > I am going to investigate bugs individually now... > > > > Honza -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com. To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
