fbug - Google Code

Today 12 min ago r3459 (Splitted FBTrace in 2 pieces, the standalone core, and the F...) committed by pedrosimonetti - Splitted FBTrace in 2 pieces, the standalone core, and the Firebug module. Splitted FBTrace in 2 pieces, the standalone core, and the Firebug module. 27 min ago issue 2014 (List of scripts missing from script panel) reported by ben.periton - Firefox: 3.5 Firebug: 1.4.0b7 I've come across an issue with a site I have been working on. This site has 2 modes; live and development. In live firebug works fine, but in development mode it does not. When in the Script panel, clicking the dropdown to display the list of scripts on the page doesnt populate the list - it is empty. From what I can gather, the issue lies with this: <iframe style="border-width: 0pt; position: absolute; visibility: visible; width: 10em; height: 10em; top: -104px; left: -104px;" id="_yuiResizeMonitor" src="data:text/html;charset=utf-8,%3Chtml%3E %3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize %3Dfunction %28%29%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire %28%29%3B%7D%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C %2Fhtml%3E"></iframe> I had a look around the extension, and after a bit of playing this seems to do the trick: [lib.js 2381] props['name'] = decodeURIComponent(props['encodedContent'].substr (0,200)).replace(/\s$/, ""); replace with props['name'] = decodeURIComponent(props['encodedContent']).replace(/ \s$/, ""); The only way I've been able to reproduce this is using the development area of the product I work on, its a bit tricky. The development mode is only available using a username/password which would allow access to private data. I have attached a firefox trace. I will try and get a test case uploaded soon. Firefox: 3.5 Firebug: 1.4.0b7 I've come across an issue with a site I have been working on. This site has 2 modes; live and development. In live firebug works fine, but in development mode it does not. When in the Script panel, clicking the dropdown to display the list of scripts on the page doesnt populate the list - it is empty. From what I can gather, the issue lies with this: <iframe style="border-width: 0pt; position: absolute; visibility: visible; width: 10em; height: 10em; top: -104px; left: -104px;" id="_yuiResizeMonitor" src="data:text/html;charset=utf-8,%3Chtml%3E %3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize %3Dfunction %28%29%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire %28%29%3B%7D%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C %2Fhtml%3E"></iframe> I had a look around the extension, and after a bit of playing this seems to do the trick: [lib.js 2381] props['name'] = decodeURIComponent(props['encodedContent'].substr (0,200)).replace(/\s$/, ""); replace with props['name'] = decodeURIComponent(props['encodedContent']).replace(/ \s$/, ""); The only way I've been able to reproduce this is using the development area of the product I work on, its a bit tricky. The development mode is only available using a username/password which would allow access to private data. I have attached a firefox trace. I will try and get a test case uploaded soon. 49 min ago issue 2011 (Firebug console does not stay open when navigating between t...) changed by johnjbar...@johnjbarton.com - This is working as designed. For more information see: http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-firebug-14/ Status: WontFix Owner: johnjbar...@johnjbarton.com This is working as designed. For more information see: http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-firebug-14/ Status: WontFix Owner: johnjbar...@johnjbarton.com 50 min ago issue 2012 (Close button functionality has changed) changed by johnjbar...@johnjbarton.com - Yes, this is a change in Firebug 1.4, as signaled by the "Off" next to the [X]. The behavior from 1.3 is minimize [_] or pressing the Firebug status bar icon For more information see http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-firebug-14/ Status: WontFix Owner: johnjbar...@johnjbarton.com Yes, this is a change in Firebug 1.4, as signaled by the "Off" next to the [X]. The behavior from 1.3 is minimize [_] or pressing the Firebug status bar icon For more information see http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-firebug-14/ Status: WontFix Owner: johnjbar...@johnjbarton.com 50 min ago issue 2013 (Declaring "var console" results in "Firebug cannot find _fir...) reported by Andrew.p.martinez - What steps will reproduce the problem? 1. Create an HTML page that includes a JS script in the <head> section 2. Inside the included JS file put: if(false){ var console = {} } 3. Run the page 4. Open the Firebug console 5. Click on the command line (errors should occur) Note: Using 'if( false ){ console = {} }' (no var) does not cause the issue. What is the expected result? What do you see instead? Expected: No errors, working console. Seen: Errors (below) and the console does not work. > Firebug cannot find _firebugConsole element true Window <site address> > redeclaration of var console Which version of Firebug? (more specific than latest please): 1.4X.0b7 Which version of Firefox? 3.5 On what operating system? Win XP SP3 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. What steps will reproduce the problem? 1. Create an HTML page that includes a JS script in the <head> section 2. Inside the included JS file put: if(false){ var console = {} } 3. Run the page 4. Open the Firebug console 5. Click on the command line (errors should occur) Note: Using 'if( false ){ console = {} }' (no var) does not cause the issue. What is the expected result? What do you see instead? Expected: No errors, working console. Seen: Errors (below) and the console does not work. > Firebug cannot find _firebugConsole element true Window <site address> > redeclaration of var console Which version of Firebug? (more specific than latest please): 1.4X.0b7 Which version of Firefox? 3.5 On what operating system? Win XP SP3 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. 100 min ago issue 1724 (Firebug no longer keeps the console window scrolled to the b...) changed by robmcampbell - Status: Duplicate Status: Duplicate 100 min ago issue 1697 (Console stops auto-scrolling) commented on by robmcampbell - Issue 1724 has been merged into this issue. Issue 1724 has been merged into this issue. 101 min ago issue 1697 (Console stops auto-scrolling) changed by robmcampbell - Status: Triaged Labels: blocks1.4 Status: Triaged Labels: blocks1.4 104 min ago issue 1307 (XhrRequests are not logged in the console window) changed by robmcampbell - I'm hoping this is fixed. changing status to triaged, but should probably be either commit or fixed. Need more testing. Status: Triaged Labels: blocks1.4 I'm hoping this is fixed. changing status to triaged, but should probably be either commit or fixed. Need more testing. Status: Triaged Labels: blocks1.4 2 hours ago issue 2012 (Close button functionality has changed) reported by jbtibor - What steps will reproduce the problem? 1. Install 1.4.0b7. 2. Open Firebug by clicking on FB icon on status bar. What is the expected result? Red X button should close FB window like it does in other applications and like it used to do in earlier FB. What do you see instead? Close button deactivates FB for the open website. Which version of Firebug? (more specific than latest please): 1.4.0b7 Which version of Firefox? 3.5 On what operating system? Windows XP 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. What steps will reproduce the problem? 1. Install 1.4.0b7. 2. Open Firebug by clicking on FB icon on status bar. What is the expected result? Red X button should close FB window like it does in other applications and like it used to do in earlier FB. What do you see instead? Close button deactivates FB for the open website. Which version of Firebug? (more specific than latest please): 1.4.0b7 Which version of Firefox? 3.5 On what operating system? Windows XP 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. 2 hours ago issue 1856 (Script panel on a non-html page doesn't make sense?) commented on by Altalas.com - Hi kpdecker, Yes, I'm viewing a HTML page containing several js files, now I open the script panel and select a file, I see something like this: "The resource from this URL is not text: http://localhost:8000/chrome/common/js/trac.js The js files are served by tracd. I checked their corresponding responce headers and found that the content-type fields were missing. So I assume it's because of this firebug thinks that they are binary files and refuse to open them? Now I have searched a bit it probably isn't a Trac issue (it seems they do have code for mime-type detection), maybe some of the plugins I installed messed up, etc. It's not a big deal so I don't intend to find exactly what's wrong here. And I have been able to debug my scripts by using another firefox install with firebug 1.3. And the problem can't be reproduced on their website because they don't use tracd to serve their contents.. I don't know of any production site served by tracd either so can't do a quick check. Hi kpdecker, Yes, I'm viewing a HTML page containing several js files, now I open the script panel and select a file, I see something like this: "The resource from this URL is not text: http://localhost:8000/chrome/common/js/trac.js The js files are served by tracd. I checked their corresponding responce headers and found that the content-type fields were missing. So I assume it's because of this firebug thinks that they are binary files and refuse to open them? Now I have searched a bit it probably isn't a Trac issue (it seems they do have code for mime-type detection), maybe some of the plugins I installed messed up, etc. It's not a big deal so I don't intend to find exactly what's wrong here. And I have been able to debug my scripts by using another firefox install with firebug 1.3. And the problem can't be reproduced on their website because they don't use tracd to serve their contents.. I don't know of any production site served by tracd either so can't do a quick check. 2 hours ago issue 1856 (Script panel on a non-html page doesn't make sense?) commented on by kpdecker - @Altalas.com I can't speak to Honza's fix, but this bug was filed on the case where the main page you are viewing is a non-HTML file, thus no javascript interpreter is loaded. Are you viewing a HTML page and scripts are missing? Can you reproduce this issue on http://trac.edgewall.org/? @Altalas.com I can't speak to Honza's fix, but this bug was filed on the case where the main page you are viewing is a non-HTML file, thus no javascript interpreter is loaded. Are you viewing a HTML page and scripts are missing? Can you reproduce this issue on http://trac.edgewall.org/? 3 hours ago issue 1856 (Script panel on a non-html page doesn't make sense?) commented on by Altalas.com - Well, guys, I think it would be best if you leave a link so that the user can force the display of a file. I'm using tracd (the standalone server app bundled with Trac), and for some reason all the static files it serves don't come with a content-type field. Now I can't debug my js because firebug refuses to open the source file... I know it's their fault on this one (or am I missing some settings to make it work?), but such things happen and as long as the js file is still recognized by firefox, there should be a way to debug it right? Oh, and keep up the good work:) I have always been a happy user of this great product. Well, guys, I think it would be best if you leave a link so that the user can force the display of a file. I'm using tracd (the standalone server app bundled with Trac), and for some reason all the static files it serves don't come with a content-type field. Now I can't debug my js because firebug refuses to open the source file... I know it's their fault on this one (or am I missing some settings to make it work?), but such things happen and as long as the js file is still recognized by firefox, there should be a way to debug it right? Oh, and keep up the good work:) I have always been a happy user of this great product. 4 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by directpathsolutions - I reverted back to 1.4.0b2 and I DO still get the same problems. Both on my private site and on the public www.xe.com site mentioned above. With the xe.com site it switches to a CSS for Print media rendering when I click on Inspect. On my site I don't need to click on inspect, some pages will jump to CSS/ Print when the page has finished loading without any further action. This is with 1.4.0b2 on FF3.5, WinXP SP3. I can't explain why weatherangel doesn't have this problem with this version and I still do. I reverted back to 1.4.0b2 and I DO still get the same problems. Both on my private site and on the public www.xe.com site mentioned above. With the xe.com site it switches to a CSS for Print media rendering when I click on Inspect. On my site I don't need to click on inspect, some pages will jump to CSS/ Print when the page has finished loading without any further action. This is with 1.4.0b2 on FF3.5, WinXP SP3. I can't explain why weatherangel doesn't have this problem with this version and I still do. 4 hours ago r3458 (Implementing the FBTrace, and some fixes.) committed by pedrosimonetti - Implementing the FBTrace, and some fixes. Implementing the FBTrace, and some fixes. 4 hours ago r3457 (Ported changes in layout to all other skins.) committed by pedrosimonetti - Ported changes in layout to all other skins. Ported changes in layout to all other skins. 6 hours ago issue 2011 (Firebug console does not stay open when navigating between t...) reported by mchung - What steps will reproduce the problem? 1. Open two tabs 2. On one tab, click the fbug icon in lower-right corner to open the console 2. Navigate to the second tab, then navigate back to first tab 3. The console is closed. What is the expected result? What do you see instead? I expect to see the console open and remain with the state that I last left it. Which version of Firebug? (more specific than latest please): 1.4.0b7 Which version of Firefox? 3.5 On what operating system? Mac OS X 10.5.7 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. No test case is required. The details above should repeat the bug. What steps will reproduce the problem? 1. Open two tabs 2. On one tab, click the fbug icon in lower-right corner to open the console 2. Navigate to the second tab, then navigate back to first tab 3. The console is closed. What is the expected result? What do you see instead? I expect to see the console open and remain with the state that I last left it. Which version of Firebug? (more specific than latest please): 1.4.0b7 Which version of Firefox? 3.5 On what operating system? Mac OS X 10.5.7 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. No test case is required. The details above should repeat the bug. 9 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by weatherangel - Yes, the console was enabled and the page was reloaded (shift-reload, cleared cache, cleared cookies, shift- reload again, and more from frustration). Reverted to 1.4b2, and this particular problem is no longer apparent. Yes, the console was enabled and the page was reloaded (shift-reload, cleared cache, cleared cookies, shift- reload again, and more from frustration). Reverted to 1.4b2, and this particular problem is no longer apparent. 9 hours ago issue 2006 (Failed to load source (All CSS)) commented on by samuelfreeman.zyrv - When I reload the page it will bring the CSS up but when I click on Edit I still get the "Failed to load source" When I reload the page it will bring the CSS up but when I click on Edit I still get the "Failed to load source" 9 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by johnjbar...@johnjbarton.com - Just to be certain, in all cases the Console was enabled and the page reloaded? I will look into this issue more if 1.4b2 works under those conditions. Just to be certain, in all cases the Console was enabled and the page reloaded? I will look into this issue more if 1.4b2 works under those conditions. 9 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by weatherangel - I was able to successfully revert to Firebug 1.4b2 which resolved this issue for me. I did not see this bug prior to upgrading beyond this version, which includes both Firefox 3.0 and 3.5. The issue seems to have been introduced between Firebug 1.4b2 and 1.4b5. For the record, I normally upgrade as soon as the next stable version becomes available... Also, prior to FF 3.5 release, I was using both 3.0x and 3.5b. 3.5b was run through a VM, but since release has replaced 3.0. I was able to successfully revert to Firebug 1.4b2 which resolved this issue for me. I did not see this bug prior to upgrading beyond this version, which includes both Firefox 3.0 and 3.5. The issue seems to have been introduced between Firebug 1.4b2 and 1.4b5. For the record, I normally upgrade as soon as the next stable version becomes available... Also, prior to FF 3.5 release, I was using both 3.0x and 3.5b. 3.5b was run through a VM, but since release has replaced 3.0. 9 hours ago issue 1948 (AJAX callback not fired in Firefox 3.5 + Firebug 1.4b3) commented on by david.titarenco - Showing XMLHttpRequests helps tremendously with debugging AJAX though :P -- it is, however, an adequate fix. I just won't update FF on some machines as I'm still pretty sure it's a Firefox issue, and not a Firebug one. Showing XMLHttpRequests helps tremendously with debugging AJAX though :P -- it is, however, an adequate fix. I just won't update FF on some machines as I'm still pretty sure it's a Firefox issue, and not a Firebug one. 9 hours ago issue 2004 (Adding margin removes css selector) changed by johnjbar...@johnjbarton.com - Thanks for the update. Status: Duplicate Owner: johnjbar...@johnjbarton.com Thanks for the update. Status: Duplicate Owner: johnjbar...@johnjbarton.com 9 hours ago issue 1894 (CSS-edit removes declaration if page with specific javascrip...) commented on by johnjbar...@johnjbarton.com - Issue 2004 has been merged into this issue. Issue 2004 has been merged into this issue. 9 hours ago issue 2006 (Failed to load source (All CSS)) Cc changed by johnjbar...@johnjbarton.com - Does it happen if you reload the page? Cc: johnjbar...@johnjbarton.com Does it happen if you reload the page? Cc: johnjbar...@johnjbarton.com 9 hours ago issue 2009 (Javascripts with console.log() functions stop running when s...) changed by johnjbar...@johnjbarton.com - Of course we cannot cause your code to work correctly with Firebug inactivate, because to cause your code to work we would have to have Firebug active. There are other solutions, like if (!console) // then no Firebug { var console = {log: function(){}, error: fucntion(){}, ...} Status: WontFix Owner: johnjbar...@johnjbarton.com Of course we cannot cause your code to work correctly with Firebug inactivate, because to cause your code to work we would have to have Firebug active. There are other solutions, like if (!console) // then no Firebug { var console = {log: function(){}, error: fucntion(){}, ...} Status: WontFix Owner: johnjbar...@johnjbarton.com 10 hours ago issue 1948 (AJAX callback not fired in Firefox 3.5 + Firebug 1.4b3) commented on by johnjbar...@johnjbarton.com - As far as I am able to determine, all of the relevant Firebug code is: try { spy.context.onReadySpy = spy; // maybe the handler will eval(), we want the URL. if (spy.onreadystatechange) spy.onreadystatechange.handleEvent(event); } ... That is, the exception here arises in the handleEvent() call. Firebug does not touch the event. The code in question runs correctly "most" of the time. Based on this I think it very unlikely that changes to Firebug code alone will solve this problem, and certainly I am out of ideas. The workaround here is to ensure that the 'spy' code is not called, by setting Firebug > Console > Show XMLHttpRequests OFF. As far as I am able to determine, all of the relevant Firebug code is: try { spy.context.onReadySpy = spy; // maybe the handler will eval(), we want the URL. if (spy.onreadystatechange) spy.onreadystatechange.handleEvent(event); } ... That is, the exception here arises in the handleEvent() call. Firebug does not touch the event. The code in question runs correctly "most" of the time. Based on this I think it very unlikely that changes to Firebug code alone will solve this problem, and certainly I am out of ideas. The workaround here is to ensure that the 'spy' code is not called, by setting Firebug > Console > Show XMLHttpRequests OFF. 10 hours ago issue 1961 ("Firebug's log limit has been reached" during simple operati...) commented on by johnjbar...@johnjbarton.com - Thanks for the update. Thanks for the update. 10 hours ago issue 1961 ("Firebug's log limit has been reached" during simple operati...) changed by johnjbar...@johnjbarton.com - Thanks for the update. Status: Verified Owner: johnjbar...@johnjbarton.com Cc: −johnjbar...@johnjbarton.com Labels: 1.4 −24 Thanks for the update. Status: Verified Owner: johnjbar...@johnjbarton.com Cc: −johnjbar...@johnjbarton.com Labels: 1.4 −24 10 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by johnjbar...@johnjbarton.com - As far as we know, the problem here is some kind of interference between Console injection and CSS analysis. It is possible that other versions of Firebug accidently have different interference, but I would be surprised if this was a general workaround. The console injection for 1.4 was done pretty early in 1.4 cycle. Has anyone seen this with Firefox 3.0? As far as we know, the problem here is some kind of interference between Console injection and CSS analysis. It is possible that other versions of Firebug accidently have different interference, but I would be surprised if this was a general workaround. The console injection for 1.4 was done pretty early in 1.4 cycle. Has anyone seen this with Firefox 3.0? 10 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by johnjbar...@johnjbarton.com - All versions of Firebug are available from http://getfirebug.com/releases All versions of Firebug are available from http://getfirebug.com/releases 10 hours ago issue 1998 (Console logging doesn't work) Status changed by johnjbar...@johnjbarton.com - Could the problem may be similar to issue 2003, that is deactivating Firebug on a page followed by opening Firebug but not reloading? Status: Triaged Could the problem may be similar to issue 2003, that is deactivating Firebug on a page followed by opening Firebug but not reloading? Status: Triaged 13 hours ago issue 1921 (logo issue) commented on by brent3721 - here it is, I saved a template file as well which would make it super easy to change in the future here it is, I saved a template file as well which would make it super easy to change in the future 15 hours ago issue 2010 (Tracing Console -> Rightclick on message -> Remove ~ fails t...) reported by BlindWanderer - Firebug: 1.5a10 Patch based on: r3454 What steps will reproduce the problem? 1. Open the Tracing Console 2. Switch to "Options" tab and selected some message types to monitor 3. Switch back to "Logs" 4. Generates messages 5. Expand a message by clicking it's title or "+" button 6. Right click on message title and select "Remove" What is the expected output? 7. The message and the message details should be removed. What do you see instead? 7. The message title row is the only row removed. The row containing the details remains. The patch addresses this problem by modifying onRemoveMessage so that it calls toggleRow to force it closed. toggleRow needed modifying as it only supported forcing a message open. The changes are trivial. I've examined every call sight for toggleRow to ensure that the changes made wouldn't break existing code. Firebug: 1.5a10 Patch based on: r3454 What steps will reproduce the problem? 1. Open the Tracing Console 2. Switch to "Options" tab and selected some message types to monitor 3. Switch back to "Logs" 4. Generates messages 5. Expand a message by clicking it's title or "+" button 6. Right click on message title and select "Remove" What is the expected output? 7. The message and the message details should be removed. What do you see instead? 7. The message title row is the only row removed. The row containing the details remains. The patch addresses this problem by modifying onRemoveMessage so that it calls toggleRow to force it closed. toggleRow needed modifying as it only supported forcing a message open. The changes are trivial. I've examined every call sight for toggleRow to ensure that the changes made wouldn't break existing code. 16 hours ago issue 64 (Displaying TextNodes with their content directly causes debu...) commented on by robmcampbell - committed r3456(!) to branches/firebug1.4 committed r3456(!) to branches/firebug1.4 16 hours ago r3456 (issue 64: Displaying TextNodes with their content directly c...) committed by robmcampbell - issue 64 : Displaying TextNodes with their content directly causes debugging headache, fixes textNode clicks and hovers in inspect, p=colmeiro, r=robc, backport from 1.5 issue 64 : Displaying TextNodes with their content directly causes debugging headache, fixes textNode clicks and hovers in inspect, p=colmeiro, r=robc, backport from 1.5 16 hours ago issue 64 (Displaying TextNodes with their content directly causes debu...) commented on by robmcampbell - just a minor nit: extra braces around inner if... else aren't consistent with the rest of the file. Removing them. Otherwise, A-OK! :) svn ci -m " issue 64 : Displaying TextNodes with their content directly causes debugging headache, fixes textNode clicks and hovers in inspect, p=colmeiro, r=robc" Sending content/firebug/inspector.js Sending content/firebug/reps.js Transmitting file data .. Committed revision 3455. we'll want this in 1.4 as well. Naturally, I missed the [&1.4] check-in tag because I am dumb. I'll apply it forthwith. just a minor nit: extra braces around inner if... else aren't consistent with the rest of the file. Removing them. Otherwise, A-OK! :) svn ci -m " issue 64 : Displaying TextNodes with their content directly causes debugging headache, fixes textNode clicks and hovers in inspect, p=colmeiro, r=robc" Sending content/firebug/inspector.js Sending content/firebug/reps.js Transmitting file data .. Committed revision 3455. we'll want this in 1.4 as well. Naturally, I missed the [&1.4] check-in tag because I am dumb. I'll apply it forthwith. 16 hours ago r3455 (issue 64: Displaying TextNodes with their content directly c...) committed by robmcampbell - issue 64 : Displaying TextNodes with their content directly causes debugging headache, fixes textNode clicks and hovers in inspect, p=colmeiro, r=robc issue 64 : Displaying TextNodes with their content directly causes debugging headache, fixes textNode clicks and hovers in inspect, p=colmeiro, r=robc 17 hours ago issue 1998 (Console logging doesn't work) commented on by hungry.rahly - I can also confirm I've seen this, but at the moment I can't reproduce it consistantly. The problem usually goes away if I do a refresh of the page. If I can find a way to reproduce it though, I'll post a test case. I can also confirm I've seen this, but at the moment I can't reproduce it consistantly. The problem usually goes away if I do a refresh of the page. If I can find a way to reproduce it though, I'll post a test case. 17 hours ago issue 2009 (Javascripts with console.log() functions stop running when s...) commented on by hungry.rahly - I don't think this is a bug per say. Because the code doesn't run if firebug isn't installed as well, as "console" isn't defined. We have always used code like. function trace(msg) { try { console.debug(msg); catch(e) { } } I don't think this is a bug per say. Because the code doesn't run if firebug isn't installed as well, as "console" isn't defined. We have always used code like. function trace(msg) { try { console.debug(msg); catch(e) { } } 18 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by weatherangel - I found the older versions after hunting more... Sorry :( I was able to roll back to the version prior to 1.4.0b5 (listed above) that throws exceptions, but at least it allows me to work with the styles. https://addons.mozilla.org/en-US/firefox/addons/versions/1843#version-1.4.0b2 I found the older versions after hunting more... Sorry :( I was able to roll back to the version prior to 1.4.0b5 (listed above) that throws exceptions, but at least it allows me to work with the styles. https://addons.mozilla.org/en-US/firefox/addons/versions/1843#version-1.4.0b2 19 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by matthew.milberry - A publicly accessible site where this can be seen is http://www.xe.com/. Clicking the Inspect button usually causes the page to re-render with the print media CSS instead of screen (using Firefox 3.5 beta and Firebug 1.4.0b7). A publicly accessible site where this can be seen is http://www.xe.com/. Clicking the Inspect button usually causes the page to re-render with the print media CSS instead of screen (using Firefox 3.5 beta and Firebug 1.4.0b7). 19 hours ago issue 1909 (DOM - Copy field name) commented on by BlindWanderer - New patch based on branch/firebug1.5 rev 3454. This implements "Copy Path" and properly wraps ordinals and impossible identifiers (though it doesn't handle keywords). New patch based on branch/firebug1.5 rev 3454. This implements "Copy Path" and properly wraps ordinals and impossible identifiers (though it doesn't handle keywords). 19 hours ago issue 1961 ("Firebug's log limit has been reached" during simple operati...) commented on by grigori.kochanov - yep, works now, thanks a lot! yep, works now, thanks a lot! 19 hours ago issue 1948 (AJAX callback not fired in Firefox 3.5 + Firebug 1.4b3) commented on by wajiw.casey - I found turning off the net tab helps reduce the chances of getting the error. Also it seems that the error almost always happens when the combine time of HXRs exceeds 2-3 seconds on body onload. Our site is request heavy(3-6 onload) and I've reproduced the bug on Leopard, Ubuntu, and XP. I found turning off the net tab helps reduce the chances of getting the error. Also it seems that the error almost always happens when the combine time of HXRs exceeds 2-3 seconds on body onload. Our site is request heavy(3-6 onload) and I've reproduced the bug on Leopard, Ubuntu, and XP. 19 hours ago issue 1948 (AJAX callback not fired in Firefox 3.5 + Firebug 1.4b3) commented on by nicholas.c.zakas - To others looking for a workaround, it seems that the onload event handler is always called appropriately regardless of what happens with onreadystatechange. I've used this as a temporary fix while this issue is being resolved. Also can confirm it's not a multi-request issue. In addition, I've also seen this happen periodically on normal-length response times (< 1s). I don't think this is unique to long responses, but it definitely pops up more frequently as the response time increases. To others looking for a workaround, it seems that the onload event handler is always called appropriately regardless of what happens with onreadystatechange. I've used this as a temporary fix while this issue is being resolved. Also can confirm it's not a multi-request issue. In addition, I've also seen this happen periodically on normal-length response times (< 1s). I don't think this is unique to long responses, but it definitely pops up more frequently as the response time increases. 19 hours ago issue 1948 (AJAX callback not fired in Firefox 3.5 + Firebug 1.4b3) commented on by jameskoch - Perhaps another clue here - http://www.mooforum.net/general12/firefox-5rc3-problems-with-request-solution-t1898.html - stating that setting your onreadystatechange handler AFTER calling send() might fix things. But that seems to introduce a bit of a race condition. Perhaps another clue here - http://www.mooforum.net/general12/firefox-5rc3-problems-with-request-solution-t1898.html - stating that setting your onreadystatechange handler AFTER calling send() might fix things. But that seems to introduce a bit of a race condition. 20 hours ago issue 1989 (Bug renders pages using CSS for Print media instead of Scree...) commented on by weatherangel - "The bad news is that it is very unlikely that we can fix this for 1.4. The console injection is proposed to be re-written in 1.6." The version having this issue is the latest stable version. Can I get the prior stable version? I have been looking around for it and cannot find a way to get a prior version - which did work prior to my allowing Firebug's most recent update. Also, why is a beta listed as the latest stable version in the Firefox Extensions directory? This version is not stable IMHO, and the version that has been with the Firefox betas was MUCH more stable from a usability perspective, again, IMHO. "The bad news is that it is very unlikely that we can fix this for 1.4. The console injection is proposed to be re-written in 1.6." The version having this issue is the latest stable version. Can I get the prior stable version? I have been looking around for it and cannot find a way to get a prior version - which did work prior to my allowing Firebug's most recent update. Also, why is a beta listed as the latest stable version in the Firefox Extensions directory? This version is not stable IMHO, and the version that has been with the Firefox betas was MUCH more stable from a usability perspective, again, IMHO. 20 hours ago issue 2009 (Javascripts with console.log() functions stop running when s...) commented on by wirtes - Also, if you activate the Firebug console, everything runs OK. So I have two ways make the Javascript work: 1) activate Firebug, or 2) keep Firebug off and comment out my console.log()s Also, if you activate the Firebug console, everything runs OK. So I have two ways make the Javascript work: 1) activate Firebug, or 2) keep Firebug off and comment out my console.log()s 20 hours ago issue 1948 (AJAX callback not fired in Firefox 3.5 + Firebug 1.4b3) commented on by david.titarenco - This is quite an annoying bug and it's also taking it's toll on several of our apps. It typically happens when using comet (long-polling) requests via prototype and I can confirm it's NOT a multiple-request issue. http://www.jumpino.com/welcome - live link On our dev machines running older versions of FF and FB, everything works fine, but on mine (FF 3.5, FB 1.4X0b7), onreadystatechange FAILS errors are rampant. From what I've read, this COULD be a Firefox bug on how it propagates events. This is quite an annoying bug and it's also taking it's toll on several of our apps. It typically happens when using comet (long-polling) requests via prototype and I can confirm it's NOT a multiple-request issue. http://www.jumpino.com/welcome - live link On our dev machines running older versions of FF and FB, everything works fine, but on mine (FF 3.5, FB 1.4X0b7), onreadystatechange FAILS errors are rampant. From what I've read, this COULD be a Firefox bug on how it propagates events.

issue 2014 (List of scripts missing from script panel) reported by ben.periton - Firefox: 3.5 Firebug: 1.4.0b7 I've come across an issue with a site I have been working on. This site has 2 modes; live and development. In live firebug works fine, but in development mode it does not. When in the Script panel, clicking the dropdown to display the list of scripts on the page doesnt populate the list - it is empty. From what I can gather, the issue lies with this: <iframe style="border-width: 0pt; position: absolute; visibility: visible; width: 10em; height: 10em; top: -104px; left: -104px;" id="_yuiResizeMonitor" src="data:text/html;charset=utf-8,%3Chtml%3E %3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize %3Dfunction %28%29%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire %28%29%3B%7D%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C %2Fhtml%3E"></iframe> I had a look around the extension, and after a bit of playing this seems to do the trick: [lib.js 2381] props['name'] = decodeURIComponent(props['encodedContent'].substr (0,200)).replace(/\s*$/, ""); replace with props['name'] = decodeURIComponent(props['encodedContent']).replace(/ \s*$/, ""); The only way I've been able to reproduce this is using the development area of the product I work on, its a bit tricky. The development mode is only available using a username/password which would allow access to private data. I have attached a firefox trace. I will try and get a test case uploaded soon.

Firefox: 3.5 Firebug: 1.4.0b7 I've come across an issue with a site I have been working on. This site has 2 modes; live and development. In live firebug works fine, but in development mode it does not. When in the Script panel, clicking the dropdown to display the list of scripts on the page doesnt populate the list - it is empty. From what I can gather, the issue lies with this: <iframe style="border-width: 0pt; position: absolute; visibility: visible; width: 10em; height: 10em; top: -104px; left: -104px;" id="_yuiResizeMonitor" src="data:text/html;charset=utf-8,%3Chtml%3E %3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize %3Dfunction %28%29%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire %28%29%3B%7D%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C %2Fhtml%3E"></iframe> I had a look around the extension, and after a bit of playing this seems to do the trick: [lib.js 2381] props['name'] = decodeURIComponent(props['encodedContent'].substr (0,200)).replace(/\s*$/, ""); replace with props['name'] = decodeURIComponent(props['encodedContent']).replace(/ \s*$/, ""); The only way I've been able to reproduce this is using the development area of the product I work on, its a bit tricky. The development mode is only available using a username/password which would allow access to private data. I have attached a firefox trace. I will try and get a test case uploaded soon.

Today