fbug - Project Hosting on Google Code

Today 3 min ago r4994 (remove // from //if in tracing guards that should not have b...) committed by johnjbarton.com - remove // from //if in tracing guards that should not have been committed remove // from //if in tracing guards that should not have been committed 25 min ago r4993 (Layout: Make the BoundingClientRect numbers make more sense) committed by sroussey - Layout: Make the BoundingClientRect numbers make more sense Layout: Make the BoundingClientRect numbers make more sense 25 min ago r4992 (Missing return in rushShowContext (related to 4991)) committed by odvarko - Missing return in rushShowContext (related to 4991) Missing return in rushShowContext (related to 4991) 39 min ago r4991 (move the check for current tab URI to just before the showCo...) committed by johnjbarton.com - move the check for current tab URI to just before the showContext call, so we don't showContext on a tab that is not current move the check for current tab URI to just before the showContext call, so we don't showContext on a tab that is not current 53 min ago issue 2523 (Right click menu displays over 40 options in Seamonkey 2.0 u...) commented on by sroussey - I had a week where I saw this a lot on Firefox. Some error of my own had the side effect, though I don't have any idea as to the cause and effect. And haven't seen it since. Can the original poster please tell us what other extensions are installed? I've tried Firebug 1.5 in Seamonkey 2 with no issues. I had a week where I saw this a lot on Firefox. Some error of my own had the side effect, though I don't have any idea as to the cause and effect. And haven't seen it since. Can the original poster please tell us what other extensions are installed? I've tried Firebug 1.5 in Seamonkey 2 with no issues. 64 min ago issue 2523 (Right click menu displays over 40 options in Seamonkey 2.0 u...) changed by johnjbar...@johnjbarton.com - We need someone from Seamonkey to help here. We're happy to help but we don't use Seamonkey and we don't know anything about it. Look for a Seamonkey newsgroup or bug list and try that. You or others are welcome to post on this bug for information. A screen shot would help since I have no idea if the 40 items are Firebugs or not. Status: OtherComponent Owner: johnjbar...@johnjbarton.com Cc: johnjbar...@johnjbarton.com We need someone from Seamonkey to help here. We're happy to help but we don't use Seamonkey and we don't know anything about it. Look for a Seamonkey newsgroup or bug list and try that. You or others are welcome to post on this bug for information. A screen shot would help since I have no idea if the 40 items are Firebugs or not. Status: OtherComponent Owner: johnjbar...@johnjbarton.com Cc: johnjbar...@johnjbarton.com 69 min ago issue 2524 (Firebug doesn't start) Status changed by johnjbar...@johnjbarton.com - Your firefox is broken, not a Firebug bug. You can try a new Firefox profile, or a new Firefox install. http://getfirebug.com/wiki/index.php/FAQ Kinda looks like you have a build with out jsd, not a good thing. Status: NeedInfo Your firefox is broken, not a Firebug bug. You can try a new Firefox profile, or a new Firefox install. http://getfirebug.com/wiki/index.php/FAQ Kinda looks like you have a build with out jsd, not a good thing. Status: NeedInfo 71 min ago issue 2525 (Inspect is not usable during script debugging) changed by johnjbar...@johnjbarton.com - Yes, this is a new 'feature'. The events from the page are disabled to ensure that the debugger is showing correct data. But then as inspect uses pages events it is broken. I think I will just thaw the page during inspect for now. Status: Triaged Cc: johnjbar...@johnjbarton.com Labels: Type-Defect debugger 1.5 blocks1.5 Yes, this is a new 'feature'. The events from the page are disabled to ensure that the debugger is showing correct data. But then as inspect uses pages events it is broken. I think I will just thaw the page during inspect for now. Status: Triaged Cc: johnjbar...@johnjbarton.com Labels: Type-Defect debugger 1.5 blocks1.5 100 min ago r4990 (Call rushShowContext from the timeout event so that the time...) committed by johnjbarton.com - Call rushShowContext from the timeout event so that the timeout event flag is cleared. Call rushShowContext from the timeout event so that the timeout event flag is cleared. 111 min ago r4989 (Do not display line endings (breaks clipboard copy)) committed by odvarko - Do not display line endings (breaks clipboard copy) Do not display line endings (breaks clipboard copy) 2 hours ago issue 2483 (Inspect highlights and SVG content) commented on by sabine.michael.ratcliffe - I guess I meant line by line rather than pixel by pixel and SVG can do this. One problem is that the larger the screen the worse the performance of canvas ... SVG does not have this problem but canvas is better on small to medium sized screens. Maybe I could get an SVG version together at some point ... I am sure that each have advantages over the other. I should revisit the canvas inspector again anyway because a few of the Fx bugs that were preventing this implementation have been fixed. I guess I meant line by line rather than pixel by pixel and SVG can do this. One problem is that the larger the screen the worse the performance of canvas ... SVG does not have this problem but canvas is better on small to medium sized screens. Maybe I could get an SVG version together at some point ... I am sure that each have advantages over the other. I should revisit the canvas inspector again anyway because a few of the Fx bugs that were preventing this implementation have been fixed. 2 hours ago issue 2483 (Inspect highlights and SVG content) commented on by sroussey - Well, canvas isn't that new so I wouldn't be too worried about bugs for this use case. But it is new, which means the feature is probably better staffed on the Mozilla side while it advances. And more likely to get things fixed if there is a problem because of that. That is just an assumption on my part, of course. I'm not sure what you mean about drawing pixel by pixel as image maps are rects, polys, and circles... I figured (more assumptions) that SVG would have have better optimization paths in the codebase. If you know that the object is a rectangular outline and not just a bunch of pixels, you could optimize that. And it has been around long enough that those optimizations could have happened. Depends on how they composite layers I guess. And rather than erasing and redrawing, you could just change the x/y/height/width. Anyhow, the only advantage I was thinking of was speed. And if canvas is faster overlaid on a page, then that is the end of that. :) It would be nice then, if SVG could render to a canvas to get an outline for this particular issue. Well, canvas isn't that new so I wouldn't be too worried about bugs for this use case. But it is new, which means the feature is probably better staffed on the Mozilla side while it advances. And more likely to get things fixed if there is a problem because of that. That is just an assumption on my part, of course. I'm not sure what you mean about drawing pixel by pixel as image maps are rects, polys, and circles... I figured (more assumptions) that SVG would have have better optimization paths in the codebase. If you know that the object is a rectangular outline and not just a bunch of pixels, you could optimize that. And it has been around long enough that those optimizations could have happened. Depends on how they composite layers I guess. And rather than erasing and redrawing, you could just change the x/y/height/width. Anyhow, the only advantage I was thinking of was speed. And if canvas is faster overlaid on a page, then that is the end of that. :) It would be nice then, if SVG could render to a canvas to get an outline for this particular issue. 2 hours ago issue 2313 (lost post parameters ) changed by odvarko - I believe this is fixed in latest Firebug 1.5 Please let us know if you still see the problem. Thanks for the report! Honza Status: ProbablyWorks Owner: odvarko Cc: −odvarko I believe this is fixed in latest Firebug 1.5 Please let us know if you still see the problem. Thanks for the report! Honza Status: ProbablyWorks Owner: odvarko Cc: −odvarko 2 hours ago r4988 (Test case for 'Console is not defined' problem, see http://g...) committed by johnjbarton.com - Test case for 'Console is not defined' problem, see http://groups.google.com/group/firebug/browse_thread/thread/498e1efaa9645072?hl=en Test case for 'Console is not defined' problem, see http://groups.google.com/group/firebug/browse_thread/thread/498e1efaa9645072?hl=en 2 hours ago issue 786 (Firebug 1.2.0b3 script execution time limit hit in net.js) Owner changed by odvarko - Please try also Firebug 1.5 http://getfirebug.com/releases/firebug/1.5X/ A lots of bugs have been fixed in this version. Honza Owner: odvarko Please try also Firebug 1.5 http://getfirebug.com/releases/firebug/1.5X/ A lots of bugs have been fixed in this version. Honza Owner: odvarko 3 hours ago issue 2525 (Inspect is not usable during script debugging) commented on by sabine.michael.ratcliffe - I have noticed this recently ... also, often the Firefox scrollbar will not scroll when breakpoints are triggered. I think this is actually a debugger issue. I have noticed this recently ... also, often the Firefox scrollbar will not scroll when breakpoints are triggered. I think this is actually a debugger issue. 3 hours ago issue 2517 ('next' property of objects do not show up in console.log()) commented on by sroussey - I see this in Firebug 1.5 also. I see this in Firebug 1.5 also. 3 hours ago r4987 (Locale update vi-VN (contribution by loveleeyoungae)) committed by odvarko - Locale update vi-VN (contribution by loveleeyoungae) Locale update vi-VN (contribution by loveleeyoungae) 3 hours ago issue 2491 ("Break On Errors" acts more like "Break On Next Error") commented on by odvarko - According to the discussion we had yesterday, I have disabled the drop down option menu and make the "Break on Next Error" persistent by default (so, the user has to deactivate it manually). Now, we can wait and see whether the options are actually necessary for other panels or not. Patch committed at R4986. Honza According to the discussion we had yesterday, I have disabled the drop down option menu and make the "Break on Next Error" persistent by default (so, the user has to deactivate it manually). Now, we can wait and see whether the options are actually necessary for other panels or not. Patch committed at R4986. Honza 3 hours ago r4986 (Disable BON options and make "Break On Next Error" persisten...) committed by odvarko - Disable BON options and make "Break On Next Error" persistent by default. Disable BON options and make "Break On Next Error" persistent by default. 3 hours ago issue 1123 (Errors in script panel show wrong line when in an iframe) changed by sabine.michael.ratcliffe - Thanks for your feedback Status: Verified Owner: sabine.michael.ratcliffe Labels: −needTestcase Thanks for your feedback Status: Verified Owner: sabine.michael.ratcliffe Labels: −needTestcase 3 hours ago issue 838 (HTML specialchars not shown correctly) commented on by sroussey - There is a new option "text as source". This takes the nodes nodes and makes them act more as source code and shows the basic entities. Give it a try. There are a lot of entities, even some for basic quote marks. We need to find the smallest set that makes sense. There is a new option "text as source". This takes the nodes nodes and makes them act more as source code and shows the basic entities. Give it a try. There are a lot of entities, even some for basic quote marks. We need to find the smallest set that makes sense. 4 hours ago issue 1123 (Errors in script panel show wrong line when in an iframe) commented on by Prefon...@hotmail.com - Sorry, I do not have a test case, and I have not seen this issue happen for some time, so I am ok if you close it now. Sorry, I do not have a test case, and I have not seen this issue happen for some time, so I am ok if you close it now. 4 hours ago issue 2525 (Inspect is not usable during script debugging) reported by Prefon...@hotmail.com - What steps will reproduce the problem? 1. Open attached html file in Firefox 2. Add breakpoint to 'var a = 1;' line. 3. Click 'doTest()' button 4. When it breaks, try to use the inspector. What is the expected result? What do you see instead? I expect to have full use of the inspector. Instead, the inspector outline will show but it won't move as I try to inspect different elements. Which version of Firebug? (more specific than latest please): 1.5b4 Which version of Firefox? 3.5 On what operating system? XP What steps will reproduce the problem? 1. Open attached html file in Firefox 2. Add breakpoint to 'var a = 1;' line. 3. Click 'doTest()' button 4. When it breaks, try to use the inspector. What is the expected result? What do you see instead? I expect to have full use of the inspector. Instead, the inspector outline will show but it won't move as I try to inspect different elements. Which version of Firebug? (more specific than latest please): 1.5b4 Which version of Firefox? 3.5 On what operating system? XP 4 hours ago issue 2517 ('next' property of objects do not show up in console.log()) commented on by lopez.roger - I have clicked the object, as noted under the code sample in the issue. When clicking into the object, only the 'previous' property is displayed. You can see here: http://skitch.com/zroger/ne9yc/issue-2517-fbug-next-property-of-objects-do-not-show-up-in-console.log-project-hosting-on-google-code Also, try console.dir() which should show the whole object in the console. It also doesn't the 'next' property. I have clicked the object, as noted under the code sample in the issue. When clicking into the object, only the 'previous' property is displayed. You can see here: http://skitch.com/zroger/ne9yc/issue-2517-fbug-next-property-of-objects-do-not-show-up-in-console.log-project-hosting-on-google-code Also, try console.dir() which should show the whole object in the console. It also doesn't the 'next' property. 4 hours ago r4985 (Localization strings.) committed by odvarko - Localization strings. Localization strings. 4 hours ago issue 1338 (Increment CSS values at least significant digit) commented on by faridhas...@hotmail.com - Hi, i would like this enhancement so i created a test case to help. Hope its ok. It has 3 paragraphs with classes noDP, oneDP, and twoDP, with the sizes set to 1em, 1.2em, and 1.25em respectivly. Hi, i would like this enhancement so i created a test case to help. Hope its ok. It has 3 paragraphs with classes noDP, oneDP, and twoDP, with the sizes set to 1em, 1.2em, and 1.25em respectivly. 5 hours ago issue 2067 (Open in a new Window fails with tab switching once Firebug i...) Status changed by odvarko - Thanks for the update! Honza Status: Verified Thanks for the update! Honza Status: Verified 5 hours ago r4984 (Fix for test net/1275) committed by odvarko - Fix for test net/1275 Fix for test net/1275 5 hours ago issue 838 (HTML specialchars not shown correctly) commented on by scott.vivian - The issue I mentioned in comment #8 above seems fixed now. However in the DOM tree I still see the characters themselves, not the entities like < - same as issue #1138 . This actually looks pretty weird for my example of displaying HTML code, not sure if there is a neat solution apart from simply displaying the entities as the entity code. Maybe using a slightly different background color? The issue I mentioned in comment #8 above seems fixed now. However in the DOM tree I still see the characters themselves, not the entities like < - same as issue #1138 . This actually looks pretty weird for my example of displaying HTML code, not sure if there is a neat solution apart from simply displaying the entities as the entity code. Maybe using a slightly different background color? 5 hours ago issue 1138 (nbsp elements rendered in the DOM as spaces) commented on by scott.vivian - I'm not sure whether this is fixed or not. What is meant to be the exact behaviour? On the above test case, when I inpect the paragraph, the entities are not shown in the DOM tree (HTML tab). I just see plain text. If I double click to edit an element, I see the entities fine. I've just seen the option "Show White Space" which does show the entities for spaces in the DOM tree. However, entities for other characters, say — or « are still shown as their actual characters, not entities. I'm not sure whether this is fixed or not. What is meant to be the exact behaviour? On the above test case, when I inpect the paragraph, the entities are not shown in the DOM tree (HTML tab). I just see plain text. If I double click to edit an element, I see the entities fine. I've just seen the option "Show White Space" which does show the entities for spaces in the DOM tree. However, entities for other characters, say — or « are still shown as their actual characters, not entities. 5 hours ago issue 2499 (Show HTTP protocol version on the Net tab) commented on by alexkon - Thank you, Honza! Thank you, Honza! 5 hours ago issue 2067 (Open in a new Window fails with tab switching once Firebug i...) commented on by scott.vivian - Yes, this is fixed now. BTW my previous comment, "then it should keep popping up every time" was supposed to read "then it should NOT keep popping up every time". I'm sure you realized that, otherwise I would be totally contradicting myself ;) Yes, this is fixed now. BTW my previous comment, "then it should keep popping up every time" was supposed to read "then it should NOT keep popping up every time". I'm sure you realized that, otherwise I would be totally contradicting myself ;) 6 hours ago issue 2499 (Show HTTP protocol version on the Net tab) changed by odvarko - Patch committed at R4983 This patch is also related to already required feature that allows to see raw text of request and response headers. This feature can be also used to see the HTTP protocol version. Just expand a network request (within the Net panel) and select Headers tab. There is a new action "view source". You need: Firebug 1.5 and Firefox 3.6 http://getfirebug.com/releases/firebug/1.5X/ Honza Status: Commit Owner: odvarko Cc: −odvarko Patch committed at R4983 This patch is also related to already required feature that allows to see raw text of request and response headers. This feature can be also used to see the HTTP protocol version. Just expand a network request (within the Net panel) and select Headers tab. There is a new action "view source". You need: Firebug 1.5 and Firefox 3.6 http://getfirebug.com/releases/firebug/1.5X/ Honza Status: Commit Owner: odvarko Cc: −odvarko 6 hours ago r4983 (Issue 2499: Show HTTP protocol version on the Net tab) committed by odvarko - Issue 2499: Show HTTP protocol version on the Net tab Issue 2499: Show HTTP protocol version on the Net tab 6 hours ago issue 1926 (Delay bug when loading page with Net enabled.) changed by odvarko - Owner: odvarko Cc: −odvarko Owner: odvarko Cc: −odvarko 7 hours ago r4982 (Refactoring FirebugChrome --> FirebugUI, forced FBL exposure...) committed by pedrosimonetti - Refactoring FirebugChrome --> FirebugUI, forced FBL exposure in IE when in development mode, updated build files. Refactoring FirebugChrome --> FirebugUI, forced FBL exposure in IE when in development mode, updated build files. 8 hours ago issue 2524 (Firebug doesn't start) reported by amit.prakash.ambasta - Please, if you don't have a test case or the time to write detailed instructions on how to reproduce your problem, then post to the newsgroup, http://groups.google.com/group/firebug. We can only fix bugs that we can reproduce exactly the way you see the problem. What steps will reproduce the problem? 1. Install firebug, Restart firefox 2.Browse to website 3.Click on firebug icon What is the expected result? What do you see instead? Expected: Firebug should open in lower context area Result: Nothing Happens. Firefox version : 3.6-b3 Firebug version: 1.4.5 Errors from jsconsole Error: jsdIScript is undefined Source File: file:///home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehe witt.com/components/firebug-service.js Line: 49 Failed to load XPCOM component: /home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehewitt.c om/components/firebug-service.js Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://browser/content/browser.js :: delayedStartup :: line 1146" data: no] Which version of Firebug? (more specific than latest please): Which version of Firefox? On what operating system? To be able to fix a bug we need a test case and detailed steps to reproduce the problem. Please attach a small test case or public URL for one. No matter how trivial you think a test case may be to create, we almost never work on bugs without one. Please, if you don't have a test case or the time to write detailed instructions on how to reproduce your problem, then post to the newsgroup, http://groups.google.com/group/firebug. We can only fix bugs that we can reproduce exactly the way you see the problem. What steps will reproduce the problem? 1. Install firebug, Restart firefox 2.Browse to website 3.Click on firebug icon What is the expected result? What do you see instead? Expected: Firebug should open in lower context area Result: Nothing Happens. Firefox version : 3.6-b3 Firebug version: 1.4.5 Errors from jsconsole Error: jsdIScript is undefined Source File: file:///home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehe witt.com/components/firebug-service.js Line: 49 Failed to load XPCOM component: /home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehewitt.c om/components/firebug-service.js Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://browser/content/browser.js :: delayedStartup :: line 1146" data: no] Which version of Firebug? (more specific than latest please): Which version of Firefox? On what operating system? To be able to fix a bug we need a test case and detailed steps to reproduce the problem. Please attach a small test case or public URL for one. No matter how trivial you think a test case may be to create, we almost never work on bugs without one. 8 hours ago r4981 (Refactoring FirebugChrome --> FirebugUI.) committed by pedrosimonetti - Refactoring FirebugChrome --> FirebugUI. Refactoring FirebugChrome --> FirebugUI. 8 hours ago r4980 (Making domplate runnable without using global variables (dom...) committed by pedrosimonetti - Making domplate runnable without using global variables (domplate and DomplateTag). Making domplate runnable without using global variables (domplate and DomplateTag). 9 hours ago r4979 (Fixing variables leaking to global namespace.) committed by pedrosimonetti - Fixing variables leaking to global namespace. Fixing variables leaking to global namespace. 9 hours ago r4978 (Refactoring lib initialize.) committed by pedrosimonetti - Refactoring lib initialize. Refactoring lib initialize. 9 hours ago issue 2483 (Inspect highlights and SVG content) changed by sabine.michael.ratcliffe - 1. Canvas is easier to work with: SVG var rect = document.createElementNS(SVG_NS, "rect"); rect.setAttribute("x", "5"); rect.setAttribute("y", "5"); rect.setAttribute("width", "20"); rect.setAttribute("height", "20"); rect.setAttribute("fill", "red"); parent.appendChild(rect); Canvas ctx.fillStyle = "red"; ctx.fillRect(5, 5, 20, 20); 2. We sometimes need to draw shapes pixel by pixel for example to highlight shapes in image maps (these could be any regular or irregular shape). 3. Canvas is much more efficient than SVG from a performance perspective. To be honest I would say that canvas being new made me less likely to use it because it was a little buggy ... especially when I first tried implementing this. Weighing the two against each other, the ease of working with canvas plus the better performance make it ideal for the inspector in my opinion. Would there be any advantages of using SVG over canvas? Owner: sabine.michael.ratcliffe Cc: sroussey 1. Canvas is easier to work with: SVG var rect = document.createElementNS(SVG_NS, "rect"); rect.setAttribute("x", "5"); rect.setAttribute("y", "5"); rect.setAttribute("width", "20"); rect.setAttribute("height", "20"); rect.setAttribute("fill", "red"); parent.appendChild(rect); Canvas ctx.fillStyle = "red"; ctx.fillRect(5, 5, 20, 20); 2. We sometimes need to draw shapes pixel by pixel for example to highlight shapes in image maps (these could be any regular or irregular shape). 3. Canvas is much more efficient than SVG from a performance perspective. To be honest I would say that canvas being new made me less likely to use it because it was a little buggy ... especially when I first tried implementing this. Weighing the two against each other, the ease of working with canvas plus the better performance make it ideal for the inspector in my opinion. Would there be any advantages of using SVG over canvas? Owner: sabine.michael.ratcliffe Cc: sroussey 9 hours ago issue 1925 (Incredible lag when using 1.4.0b3 under Firefox 3.5) Status changed by sabine.michael.ratcliffe - Thanks for your feedback Status: Verified Thanks for your feedback Status: Verified 9 hours ago issue 1902 (Firebug causes problems while NTLM authentication against pr...) commented on by google....@moderlak.de - Hi there, I had altercating with the same issue and I found the main point of that bug. The implemenation of NTLM is correct as it is: Three requests are needed for the handshake - see http://www.innovation.ch/personal/ronald/ntlm.html#handshake The only thing were Firebug goes wrong is (and that's the bug), that he puts in the first both requests the body from the answer of the last response. But the browser received bodydata only in the last response. This can be verified with wireshark. And this is the reason why I and surely the other peoples here were get confused. Hi there, I had altercating with the same issue and I found the main point of that bug. The implemenation of NTLM is correct as it is: Three requests are needed for the handshake - see http://www.innovation.ch/personal/ronald/ntlm.html#handshake The only thing were Firebug goes wrong is (and that's the bug), that he puts in the first both requests the body from the answer of the last response. But the browser received bodydata only in the last response. This can be verified with wireshark. And this is the reason why I and surely the other peoples here were get confused. 10 hours ago r4977 (CSS Formatter: Selector Text Formatting) committed by kpdecker - CSS Formatter: Selector Text Formatting CSS Formatter: Selector Text Formatting 10 hours ago r4976 (Formatter base logic.) committed by kpdecker - Formatter base logic. Formatter base logic. 10 hours ago r4975 (License) committed by kpdecker - License License 10 hours ago issue 2496 (build.xml jsdoc fix for 1.5) Status changed by odvarko - Thanks for the update! Honza Status: Verified Thanks for the update! Honza Status: Verified 11 hours ago issue 2510 (Console and watch returns undefined for falsy values when de...) Status changed by kpdecker - Status: Verified Status: Verified

issue 2524 (Firebug doesn't start) reported by amit.prakash.ambasta - Please, if you don't have a test case or the time to write detailed instructions on how to reproduce your problem, then post to the newsgroup, http://groups.google.com/group/firebug. We can only fix bugs that we can reproduce exactly the way you see the problem. What steps will reproduce the problem? 1. Install firebug, Restart firefox 2.Browse to website 3.Click on firebug icon What is the expected result? What do you see instead? Expected: Firebug should open in lower context area Result: Nothing Happens. Firefox version : 3.6-b3 Firebug version: 1.4.5 Errors from jsconsole Error: jsdIScript is undefined Source File: file:///home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehe witt.com/components/firebug-service.js Line: 49 Failed to load XPCOM component: /home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehewitt.c om/components/firebug-service.js Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://browser/content/browser.js :: delayedStartup :: line 1146" data: no] Which version of Firebug? (more specific than latest please): Which version of Firefox? On what operating system? To be able to fix a bug we need a test case and detailed steps to reproduce the problem. Please attach a small test case or public URL for one. No matter how trivial you think a test case may be to create, we almost never work on bugs without one.

Please, if you don't have a test case or the time to write detailed instructions on how to reproduce your problem, then post to the newsgroup, http://groups.google.com/group/firebug. We can only fix bugs that we can reproduce exactly the way you see the problem. What steps will reproduce the problem? 1. Install firebug, Restart firefox 2.Browse to website 3.Click on firebug icon What is the expected result? What do you see instead? Expected: Firebug should open in lower context area Result: Nothing Happens. Firefox version : 3.6-b3 Firebug version: 1.4.5 Errors from jsconsole Error: jsdIScript is undefined Source File: file:///home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehe witt.com/components/firebug-service.js Line: 49 Failed to load XPCOM component: /home/amitprakash/.mozilla/firefox/15g7wngx.default/extensions/firebug@software.joehewitt.c om/components/firebug-service.js Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://browser/content/browser.js :: delayedStartup :: line 1146" data: no] Which version of Firebug? (more specific than latest please): Which version of Firefox? On what operating system? To be able to fix a bug we need a test case and detailed steps to reproduce the problem. Please attach a small test case or public URL for one. No matter how trivial you think a test case may be to create, we almost never work on bugs without one.

Today