fbug - Project Hosting on Google Code

Today 26 min ago r4798 (Fix chrome URL (stylesheet). It must be case sensitive.) committed by odvarko - Fix chrome URL (stylesheet). It must be case sensitive. Fix chrome URL (stylesheet). It must be case sensitive. 32 min ago r4797 (Update locale (es-AR)) committed by odvarko - Update locale (es-AR) Update locale (es-AR) 39 min ago r4796 (Update locale ro-RO) committed by odvarko - Update locale ro-RO Update locale ro-RO 44 min ago issue 289 (Incorrect highlighting when inspecting elements of a positi...) Status changed by sabine.michael.ratcliffe - Thanks for your feedback. Status: Verified Thanks for your feedback. Status: Verified 45 min ago r4795 (New locale (hr-HR/Croatia)) committed by odvarko - New locale (hr-HR/Croatia) New locale (hr-HR/Croatia) 63 min ago r4794 (Fix localization string.) committed by odvarko - Fix localization string. Fix localization string. 70 min ago issue 2372 (Possible Memory Leak Still Around) commented on by m...@bittouch.nl - We use Firebug a lot during development and the memory problem is real. Our pages also use xmlhttprequest calls. To indicate : yesterday I did a lot of development and refreshing ; I left firefox running overnight with only one tab ; this morning it had 500+ MB of memory usage. (sadly I did not check how much it had when I left for home yesterday) I have tried the testpage presented by Honza. Firebug console active, Net tab not active. Here's my results. Initial memory usage before the test : 110 MB Opened Honza's testpage : still 110 MB Started the test : usage steadily increased from 110 MB to 140 MB in only 1 minute Reload the page, in effect stopping the test : memory drops to 125 MB Close the tab containing the test page : memory drops to 123 MB There seem to be two problems ; the first being the ever and fast increasing memory consumption, secondly after closing the page not all memory is released (went from 110 before the test to 123 afterwards) To indicate this indeed is a firebug problem ; opened up the page again, firebug disabled. Start test ... no memory increase at all. Ubuntu 9.10 ; Firefox 3.5.4 ; Firebug 1.4.5 We use Firebug a lot during development and the memory problem is real. Our pages also use xmlhttprequest calls. To indicate : yesterday I did a lot of development and refreshing ; I left firefox running overnight with only one tab ; this morning it had 500+ MB of memory usage. (sadly I did not check how much it had when I left for home yesterday) I have tried the testpage presented by Honza. Firebug console active, Net tab not active. Here's my results. Initial memory usage before the test : 110 MB Opened Honza's testpage : still 110 MB Started the test : usage steadily increased from 110 MB to 140 MB in only 1 minute Reload the page, in effect stopping the test : memory drops to 125 MB Close the tab containing the test page : memory drops to 123 MB There seem to be two problems ; the first being the ever and fast increasing memory consumption, secondly after closing the page not all memory is released (went from 110 before the test to 123 afterwards) To indicate this indeed is a firebug problem ; opened up the page again, firebug disabled. Start test ... no memory increase at all. Ubuntu 9.10 ; Firefox 3.5.4 ; Firebug 1.4.5 4 hours ago issue 2482 (Editing Disabled) reported by webflashing - 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. Enter any website, even localhost. 2. Start Firebug to inspect the page structure 3. Any kind of edition is disabled. What is the expected result? What do you see instead? the expected result is the ability of the user to edit the page at "runtime". But instead, I see Firebug like plan text, with colors, links and so.. but editing is disabled. Which version of Firebug? (more specific than latest please): 1.4.5 Which version of Firefox? 3.5.5 On what operating system? XP 64-bit 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. Enter any website, even localhost. 2. Start Firebug to inspect the page structure 3. Any kind of edition is disabled. What is the expected result? What do you see instead? the expected result is the ability of the user to edit the page at "runtime". But instead, I see Firebug like plan text, with colors, links and so.. but editing is disabled. Which version of Firebug? (more specific than latest please): 1.4.5 Which version of Firefox? 3.5.5 On what operating system? XP 64-bit 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. 11 hours ago issue 2481 ('Add watch' on 2nd expression of a multi-conditional will us...) reported by Prefon...@hotmail.com - 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. open up addwatch.html 2. set a breakpoint on the conditional statement 3. click 'do test' button 4. when it breaks, try to add a watch on the 'document.get...' expression. 5. the incorrect expression will get added, causing it to display a syntax error What is the expected result? What do you see instead? If i highlight 'document.getElementById("button1")' and add a watch for it, the added watch is '&p; document.getElementById("b'. Which version of Firebug? (more specific than latest please): 1.5b3 Which version of Firefox? 3.5.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. 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. open up addwatch.html 2. set a breakpoint on the conditional statement 3. click 'do test' button 4. when it breaks, try to add a watch on the 'document.get...' expression. 5. the incorrect expression will get added, causing it to display a syntax error What is the expected result? What do you see instead? If i highlight 'document.getElementById("button1")' and add a watch for it, the added watch is '&p; document.getElementById("b'. Which version of Firebug? (more specific than latest please): 1.5b3 Which version of Firefox? 3.5.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. 12 hours ago issue 2480 ([Enhancement] Add an option setting for logging level in Fir...) reported by jjathman - It would be nice to have an option in Firebug to be able to set what level of logging is displayed by Firebug in the console. This option could be set in the same place that Text Size or the other options are set. I would see this being a list of choices like "Debug", "Info", "Warn", "Error". So if the user selected "Warn", then any console.warn or console.error messages would display in the console, but any console.debug messages would be ignored. By default all console messages would display. Which version of Firebug? (more specific than latest please): 1.4.5, though I think this could apply to any version of Firebug Which version of Firefox? 3.0.14 On what operating system? Windows XP It would be nice to have an option in Firebug to be able to set what level of logging is displayed by Firebug in the console. This option could be set in the same place that Text Size or the other options are set. I would see this being a list of choices like "Debug", "Info", "Warn", "Error". So if the user selected "Warn", then any console.warn or console.error messages would display in the console, but any console.debug messages would be ignored. By default all console messages would display. Which version of Firebug? (more specific than latest please): 1.4.5, though I think this could apply to any version of Firebug Which version of Firefox? 3.0.14 On what operating system? Windows XP 12 hours ago issue 289 (Incorrect highlighting when inspecting elements of a positi...) commented on by splintor - Tested it with the test page with Firebug 1.5X.0b3 and the problem seems to be solved. Thanks, splintor Tested it with the test page with Firebug 1.5X.0b3 and the problem seems to be solved. Thanks, splintor 13 hours ago issue 2467 (timeline bars don't show) commented on by tasoss - lolll thank you! :) i was afraid i had to visit again my eye-doctor ;) lolll thank you! :) i was afraid i had to visit again my eye-doctor ;) 13 hours ago issue 2478 (Copy HTML on HTML element) Status changed by sroussey - Status: New Status: New 13 hours ago issue 2479 (Net panel doesn't show timed out requests) commented on by sroussey - Good test. In 1.5b3 you see the attempt running, but it never ends (always spinning) in Fx 3.5/3.6 Good test. In 1.5b3 you see the attempt running, but it never ends (always spinning) in Fx 3.5/3.6 14 hours ago issue 2479 (Net panel doesn't show timed out requests) commented on by ojracc - I don't know what level of detail Firefox provides for requests that failed trying to establish a TCP connection, but it's at least possible to get the request time; with YSlow 2.0.1, it shows up under Components -> js in the "Response Time" column. I don't know what level of detail Firefox provides for requests that failed trying to establish a TCP connection, but it's at least possible to get the request time; with YSlow 2.0.1, it shows up under Components -> js in the "Response Time" column. 14 hours ago issue 2479 (Net panel doesn't show timed out requests) reported by ojracc - What steps will reproduce the problem? 1. Open the Net panel 2. View http://ojrac.com/fbug-timeout.php 3. If it loads rapidly, find an unused IP address (any IP that won't respond to TCP SYN packets on port 80) 4. Go to go to http://ojrac.com/fbug-timeout.php?ip=10.0.0.1 (but with the IP you just found) What is the expected result? What do you see instead? Expected: The Net panel shows 2 page requests -- one to GET /fbug-timeout.php, and a second to get http://$ip/example.js The overall request time is multiple seconds long, and the example.js line should show a very long connection time. Actual: The first GET shows up correctly, as does the total load time, however, there is no reference to the attempted (and failed) load of http://$ip/example.js This is important because it's a significant failure mode that immediately sends developers like me to the Firebug net screen to debug the slow page load time, but provides no insight into the failure. Which version of Firebug? (more specific than latest please): 1.4.5 Which version of Firefox? 3.5.4 On what operating system? Ubuntu 9.10 What steps will reproduce the problem? 1. Open the Net panel 2. View http://ojrac.com/fbug-timeout.php 3. If it loads rapidly, find an unused IP address (any IP that won't respond to TCP SYN packets on port 80) 4. Go to go to http://ojrac.com/fbug-timeout.php?ip=10.0.0.1 (but with the IP you just found) What is the expected result? What do you see instead? Expected: The Net panel shows 2 page requests -- one to GET /fbug-timeout.php, and a second to get http://$ip/example.js The overall request time is multiple seconds long, and the example.js line should show a very long connection time. Actual: The first GET shows up correctly, as does the total load time, however, there is no reference to the attempted (and failed) load of http://$ip/example.js This is important because it's a significant failure mode that immediately sends developers like me to the Firebug net screen to debug the slow page load time, but provides no insight into the failure. Which version of Firebug? (more specific than latest please): 1.4.5 Which version of Firefox? 3.5.4 On what operating system? Ubuntu 9.10 15 hours ago r4793 (Move FBTestFirebug.js lib into FBTest extension so we can ad...) committed by odvarko - Move FBTestFirebug.js lib into FBTest extension so we can adapt it for new Firebug version if necessary. Move FBTestFirebug.js lib into FBTest extension so we can adapt it for new Firebug version if necessary. 15 hours ago issue 2478 (Copy HTML on HTML element) reported by sroussey - When copying the html from the context menu of the html element in the html panel of firebug, the copied data includes the <div> for the firebug console. This happens in 1.4 and 1.5. In 1.5, the stylesheet data is also copied. When copying the html from the context menu of the html element in the html panel of firebug, the copied data includes the <div> for the firebug console. This happens in 1.4 and 1.5. In 1.5, the stylesheet data is also copied. 15 hours ago issue 2448 (Firebug HTML panel encoding display and editing) commented on by sroussey - Slight change to the console injector to vary insertion type based on type of document (HTML vs XHTML/SVG). This way, normal HTML users don't see the console as <html:div>... Slight change to the console injector to vary insertion type based on type of document (HTML vs XHTML/SVG). This way, normal HTML users don't see the console as <html:div>... 15 hours ago issue 2473 (Latest Firebug versions not activating in Jetpack Developmen...) Status changed by odvarko - Yes, I am closing this one. Honza Status: OtherComponent Yes, I am closing this one. Honza Status: OtherComponent 16 hours ago issue 2473 (Latest Firebug versions not activating in Jetpack Developmen...) commented on by johnjbar...@johnjbarton.com - Shouldn't this be closed on "OtherComponent"? Shouldn't this be closed on "OtherComponent"? 16 hours ago issue 2475 (Firefox freezes on reload when CSS file is changed with Fire...) changed by johnjbar...@johnjbarton.com - It is not possible to perform step #2 on the site you list because we do not have access to its CSS files. Please attach a test case that shows the problem. Status: NeedInfo Cc: johnjbar...@johnjbarton.com It is not possible to perform step #2 on the site you list because we do not have access to its CSS files. Please attach a test case that shows the problem. Status: NeedInfo Cc: johnjbar...@johnjbarton.com 16 hours ago issue 2477 (Menu Item <<Firebug Menu::Firebug Online::Issue Tracker>> im...) changed by johnjbar...@johnjbarton.com - Status: Triaged Cc: johnjbar...@johnjbarton.com Labels: Type-Enhancement ui 1.5 Status: Triaged Cc: johnjbar...@johnjbarton.com Labels: Type-Enhancement ui 1.5 16 hours ago issue 1751 (page reload is very slow and browser becomes unresponsive) commented on by johnjbar...@johnjbarton.com - Please try Firebug 1.5b3 and let us know. Please try Firebug 1.5b3 and let us know. 16 hours ago issue 1751 (page reload is very slow and browser becomes unresponsive) commented on by Iker.Jimenez - Ubuntu 8.10, FF 3.0.15 and FB 1.4.5 The issue can be reproduced only when the console is enabled. CPU skyrockets to 50% (this is a dual core, so one core is fully used) Ubuntu 8.10, FF 3.0.15 and FB 1.4.5 The issue can be reproduced only when the console is enabled. CPU skyrockets to 50% (this is a dual core, so one core is fully used) 16 hours ago issue 2013 (Declaring "var console" results in "Firebug cannot find _fir...) commented on by johnjbar...@johnjbarton.com - Regarding comment 8: do you mean you tried the test case here and it fails on 1.4.5? Please try 1.5b3, that is the version we are fixing now. Regarding comment 8: do you mean you tried the test case here and it fails on 1.4.5? Please try 1.5b3, that is the version we are fixing now. 16 hours ago issue 2067 (Open in a new Window fails with tab switching once Firebug i...) Labels changed by johnjbar...@johnjbarton.com - Labels: blocks1.5 Labels: blocks1.5 16 hours ago issue 2477 (Menu Item <<Firebug Menu::Firebug Online::Issue Tracker>> im...) reported by sroussey - The menu item <<Firebug Menu::Firebug Online::Issue Tracker>> could be altered (or a new menu item added) to show a chrome url with information about common problems with Firebug, like installation, creating a new profile, etc. In addition, it could present a textarea filled with data (possibly already copied to the clipboard) about the user's current profile: version #s, other extensions, and Fx/fbug preference settings (thus why a chrome page). Eventually we might notice certain settings that cause problems and be able to fix them without the need to recommend a new profile. The menu item <<Firebug Menu::Firebug Online::Issue Tracker>> could be altered (or a new menu item added) to show a chrome url with information about common problems with Firebug, like installation, creating a new profile, etc. In addition, it could present a textarea filled with data (possibly already copied to the clipboard) about the user's current profile: version #s, other extensions, and Fx/fbug preference settings (thus why a chrome page). Eventually we might notice certain settings that cause problems and be able to fix them without the need to recommend a new profile. 17 hours ago issue 2476 (Editing a node in HTML panel causes break on mutate to stop ...) reported by sroussey - Test case: http://www.janodvarko.cz/firebug/tests/BreakOnMutate/breakOnMutate.html 1) Load the page and select the HTML panel 2) Click the pause/break on mutate button in the HTML panel 3) Use HTML Inspector to inspect the "Text Element" (h3, green, just above the buttons on the page) so, element's source is visible in the HTML panel. 4) Edit the text in the HTML panel 5) Click the "Break On Text Modified" button in the web page 6) The code within that if statement is executed, but no break occurs Test case: http://www.janodvarko.cz/firebug/tests/BreakOnMutate/breakOnMutate.html 1) Load the page and select the HTML panel 2) Click the pause/break on mutate button in the HTML panel 3) Use HTML Inspector to inspect the "Text Element" (h3, green, just above the buttons on the page) so, element's source is visible in the HTML panel. 4) Edit the text in the HTML panel 5) Click the "Break On Text Modified" button in the web page 6) The code within that if statement is executed, but no break occurs 17 hours ago issue 2475 (Firefox freezes on reload when CSS file is changed with Fire...) reported by melpangborn - 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.View webpage on HTML tab in Firebug using the inspection feature 2.Change external CSS file and save file (any change, aka: background-color:#ffffff; ) 3.reload webpage 4.Firefox freezes and requires task manager to close (If I turn firebug off, firefox does not freeze) What is the expected result? What do you see instead? Web page should reload without freezing firefox even when firebug is active. Which version of Firebug? (more specific than latest please): 1.4.5 Which version of Firefox? 3.5.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. Don't think the page matters as it has happened with all sites I've worked on. Most recently: http://www.transportation-tech.com 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.View webpage on HTML tab in Firebug using the inspection feature 2.Change external CSS file and save file (any change, aka: background-color:#ffffff; ) 3.reload webpage 4.Firefox freezes and requires task manager to close (If I turn firebug off, firefox does not freeze) What is the expected result? What do you see instead? Web page should reload without freezing firefox even when firebug is active. Which version of Firebug? (more specific than latest please): 1.4.5 Which version of Firefox? 3.5.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. Don't think the page matters as it has happened with all sites I've worked on. Most recently: http://www.transportation-tech.com 17 hours ago r4792 (Initialize mutationBreakpoints at the right time.) committed by odvarko - Initialize mutationBreakpoints at the right time. Initialize mutationBreakpoints at the right time. 17 hours ago issue 2067 (Open in a new Window fails with tab switching once Firebug i...) commented on by scott.vivian - I didn't see a version a27 so I tried both a26 and b3. The second issue above appears to be fixed - if I close the Firebug window (by clicking the red X in Windows) then do "right-click > Inspect element", the Firebug window does appear again. However the issue that I reported still occurs. Close the window by clicking the X, then either switch to a different tab and back or simply click a link on the current page to load a new page. The window reappears unexpectedly. I don't know if that is intended, but to me if you close the window (to "minimize" Firebug) then it should keep popping up every time you load a new page. As previously stated this only happens if you have the option "Always open in new window" on. If Firebug is attached, and you minimise it, then the problem doesn't happen. I didn't see a version a27 so I tried both a26 and b3. The second issue above appears to be fixed - if I close the Firebug window (by clicking the red X in Windows) then do "right-click > Inspect element", the Firebug window does appear again. However the issue that I reported still occurs. Close the window by clicking the X, then either switch to a different tab and back or simply click a link on the current page to load a new page. The window reappears unexpectedly. I don't know if that is intended, but to me if you close the window (to "minimize" Firebug) then it should keep popping up every time you load a new page. As previously stated this only happens if you have the option "Always open in new window" on. If Firebug is attached, and you minimise it, then the problem doesn't happen. 17 hours ago issue 2459 (Net Panel does not show prefetch requests) Cc changed by odvarko - The problem is that all the prefetched documents are requested without a relationship to the page that contained the ref="prefetch" (there is no parent window for the request). Since Firebug Net panel displays only requests that belong to the current page, these are skipped. Honza Cc: odvarko The problem is that all the prefetched documents are requested without a relationship to the page that contained the ref="prefetch" (there is no parent window for the request). Since Firebug Net panel displays only requests that belong to the current page, these are skipped. Honza Cc: odvarko 17 hours ago issue 2467 (timeline bars don't show) commented on by odvarko - Patch committed at R4791 Will be available in Firebug 1.5b4 http://getfirebug.com/releases/firebug/1.5X/ Honza Patch committed at R4791 Will be available in Firebug 1.5b4 http://getfirebug.com/releases/firebug/1.5X/ Honza 17 hours ago r4791 (Second part of: Issue 2467: timeline bars don't show) committed by odvarko - Second part of: Issue 2467: timeline bars don't show Second part of: Issue 2467: timeline bars don't show 19 hours ago issue 2467 (timeline bars don't show) commented on by odvarko - OK, you have persuaded me, it's a bug :-) I'll fix it. Thanks for the help, we appreciate that! Honza OK, you have persuaded me, it's a bug :-) I'll fix it. Thanks for the help, we appreciate that! Honza 21 hours ago issue 2468 (firefox 3.5.5 and firebug 1.4.5) commented on by aymoskalev - Fixed in autopatch "a", will be realesed soon. Regards, Andrei Moskaliov Kaspersky Lab's tester. Fixed in autopatch "a", will be realesed soon. Regards, Andrei Moskaliov Kaspersky Lab's tester. 21 hours ago issue 2468 (firefox 3.5.5 and firebug 1.4.5) commented on by zerkmss - at kaspersky support forums i get response that this KAV behaviour already fixed and will be distributed via updates soon. thank you. at kaspersky support forums i get response that this KAV behaviour already fixed and will be distributed via updates soon. thank you. 21 hours ago issue 2468 (firefox 3.5.5 and firebug 1.4.5) changed by odvarko - Thanks for the update, I am closing this bug. Honza Status: UserResolved Owner: odvarko Cc: −odvarko Thanks for the update, I am closing this bug. Honza Status: UserResolved Owner: odvarko Cc: −odvarko 22 hours ago issue 2468 (firefox 3.5.5 and firebug 1.4.5) commented on by zerkmss - yep, pausing kaspersky helps. yep, pausing kaspersky helps. 23 hours ago issue 2473 (Latest Firebug versions not activating in Jetpack Developmen...) changed by odvarko - https://bugzilla.mozilla.org/show_bug.cgi?id=527647 Status: Triaged Owner: odvarko Cc: −odvarko Labels: bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=527647 Status: Triaged Owner: odvarko Cc: −odvarko Labels: bugzilla Yesterday 24 hours ago r4790 (Jsdoc for spy) committed by odvarko - Jsdoc for spy Jsdoc for spy 25 hours ago issue 2448 (Firebug HTML panel encoding display and editing) commented on by sroussey - I had a couple lines added in the patch that I didn't write and I guess were a result of updating my svn repo. They don't exist in the current patch. I had a couple lines added in the patch that I didn't write and I guess were a result of updating my svn repo. They don't exist in the current patch. 26 hours ago issue 2013 (Declaring "var console" results in "Firebug cannot find _fir...) commented on by ttann...@bloomberg.net - It happens for me with firebug 1.4.5, firefox 3.5.4, on vista (32 bit) It happens for me with firebug 1.4.5, firefox 3.5.4, on vista (32 bit) 26 hours ago issue 2448 (Firebug HTML panel encoding display and editing) commented on by johnjbar...@johnjbarton.com - >lib.js: > >versionChecker/appInfo -- I didn't add these - and don't know where they come from. >Any thoughts? I don't understand why you are asking about this. We'll discuss this patch in our call tomorrow. I'm inclined to put it in 1.5b4. >lib.js: > >versionChecker/appInfo -- I didn't add these - and don't know where they come from. >Any thoughts? I don't understand why you are asking about this. We'll discuss this patch in our call tomorrow. I'm inclined to put it in 1.5b4. 26 hours ago issue 2468 (firefox 3.5.5 and firebug 1.4.5) commented on by zerkmss - this may be nice catch, because i'm using it too, but it don't notify me on any suspicious activity it blocked. so i will report later here about results and if that true will post but-report to kaspersky too. thank you. this may be nice catch, because i'm using it too, but it don't notify me on any suspicious activity it blocked. so i will report later here about results and if that true will post but-report to kaspersky too. thank you. 27 hours ago issue 2468 (firefox 3.5.5 and firebug 1.4.5) commented on by johnjbar...@johnjbarton.com - Several people have reported success on this problem after pausing antivirus esp. one called Kaspersky AV. Several people have reported success on this problem after pausing antivirus esp. one called Kaspersky AV. 27 hours ago issue 2474 (Form input named 'action' causes problems in DOM attribute i...) changed by johnjbar...@johnjbarton.com - Thanks for the update, I take it this is already fixed. Status: ProbablyWorks Owner: johnjbar...@johnjbarton.com Thanks for the update, I take it this is already fixed. Status: ProbablyWorks Owner: johnjbar...@johnjbarton.com 29 hours ago issue 2474 (Form input named 'action' causes problems in DOM attribute i...) commented on by spencer.w.thomas - That has fixed not only my simple example, but almost the more complex page on which it was based. That has fixed not only my simple example, but almost the more complex page on which it was based. 30 hours ago issue 2448 (Firebug HTML panel encoding display and editing) commented on by sroussey - Cleaned up and consolidated old comments: Issues addressed: Issue #2470 Issue #2453 Issue #2439 Issue #2438 Issue #2435 Issue #2359 Issue #2299 Issue #2250 Issue #1980 Issue #1588 Issue #1138 Issue #838 Notes: Entity handling is done by creating regexps to do splits (fastest), they get created on demand when needed and cached. While most conversions are straight forward, the conversions for text nodes are done in such a way that we can see which entity list was responsible for the purpose of marking up the entities with different styles. The Show White Space option and the Text As Source option style their entities/whitespace somewhat differently. XHTML/MathML/SVG: I personally don't see much use of these since they have to be served from the webserver in such a way that IE chokes on such documents. Even so, some people do use them, and thus they don't use IE. Likely they use Firefox, and thus Firebug if they are going to debug these documents. Firebug should at least not fail as much. I've added in some support, a little better handling of errors, and alter the UI to address them directly. When HTML5 comes around and it becomes a lot easier to use svg/mathml, additional direct support will be warranted. But for now, the goal was to work better and fail less. Firefox puts CSS styling stuff in attributes internally for MathML. This causes a number of problems. The quick fix was to remove them sight, when serializing to a string (copy and editing), and when showing in the html panel. Editing nodes with such styles could lead to their loosing of their styles. There should be more research on this, and likely an issue for fbug and one for Mozilla. In errors.js: I found that if I had chromebug set to break on errors, I would stop on a line that was checking for the existance of FBTrace, but it was undefined. I suppose this is why it is bracketed by try/catch but I dislike breaking on it, so I use typeof to see if it is undefined first (which the only way to see if a variable is defined or not without throwing an exception). browserOverlay.xul, lib/entities.js: I moved entity definitions to their own file. Multiple files, renaming and adding of options: escapeHTML - changed to escapeForCss/escapeForTextNode/escapeForAttribute since the rules are slightly different depending on why it is being called. Attributes, since they are always displayed with double quotes would show a double quote in entity form, for example. Completely removing escapeHTML forced finding all the cases. showWhitespaceNodes - the way the code was, it was simply dealing with text nodes, not text nodes that contained only whitespace (which Fx has an attribute for, if I remember correctly). As such, it was showing whitespace inside text nodes, so I renamed it showTextNodesWithWhitespace. I needed this to keep things clear as to what things meant, but I no longer need the mental crutch, though it might be helpful to someone in the future. showTextNodesAsSource - open to a better name. This references the feature, both in display and in editing to treat the text as if it were source code. Thus show entities, and if a user types <b> they mean bold. With this option off, if a user types <b> it means as the browser would see it and converts it to <b>. lib.js: versionChecker/appInfo -- I didn't add these - and don't know where they come from. Any thoughts? Some functions were added to check if a node is xhtml/svg/mathml. Being xml derived, xhtml, mathml, svg all have issues with bad markup. So some error handling was added, since bad markup is the default while someone is editing a node and getting updates live. Some error handing was added that essentially cancels updates until it is conformant. SVG/MathML tags self close if empty. Also in html panel I found a list of void tags and updated selfClosingTags/invisibleTags html.js domplate stuff for textnode/textelement changed to use getNodeTextGroups which returns an array of strings and style information. Removal of WhitespaceNode. Split out TextNodeEditor from AttributeEditor (there was a todo comment from Joe to do so). TextNodeEditor deals with text nodes that have sibling elements by keeping track of their position via a range (this is in part because as people type html, the range will keep track of the text nodes and elements that the user is creating as they type, and this range could be in the middle of the parent elements children). editNode made to recognize the type of node and use a specialized editor. Just a hook for now. All editors are just aliases of HTMLEditor. Possible extension point. A MathML extension could use a ASCIIMathML based editor, for example, by replacing Firebug.HTMLPanel.Editors.MathML. htmlLib.js added hasCommentChildren reps.js remove MathMl -moz-XXX attributes that are really css getNodeText => getNodeTextGroups - return an array of string/class info for styling in domplate getContextMenuItems takes care of noticing svg/mathml nodes for the context menus Cleaned up and consolidated old comments: Issues addressed: Issue #2470 Issue #2453 Issue #2439 Issue #2438 Issue #2435 Issue #2359 Issue #2299 Issue #2250 Issue #1980 Issue #1588 Issue #1138 Issue #838 Notes: Entity handling is done by creating regexps to do splits (fastest), they get created on demand when needed and cached. While most conversions are straight forward, the conversions for text nodes are done in such a way that we can see which entity list was responsible for the purpose of marking up the entities with different styles. The Show White Space option and the Text As Source option style their entities/whitespace somewhat differently. XHTML/MathML/SVG: I personally don't see much use of these since they have to be served from the webserver in such a way that IE chokes on such documents. Even so, some people do use them, and thus they don't use IE. Likely they use Firefox, and thus Firebug if they are going to debug these documents. Firebug should at least not fail as much. I've added in some support, a little better handling of errors, and alter the UI to address them directly. When HTML5 comes around and it becomes a lot easier to use svg/mathml, additional direct support will be warranted. But for now, the goal was to work better and fail less. Firefox puts CSS styling stuff in attributes internally for MathML. This causes a number of problems. The quick fix was to remove them sight, when serializing to a string (copy and editing), and when showing in the html panel. Editing nodes with such styles could lead to their loosing of their styles. There should be more research on this, and likely an issue for fbug and one for Mozilla. In errors.js: I found that if I had chromebug set to break on errors, I would stop on a line that was checking for the existance of FBTrace, but it was undefined. I suppose this is why it is bracketed by try/catch but I dislike breaking on it, so I use typeof to see if it is undefined first (which the only way to see if a variable is defined or not without throwing an exception). browserOverlay.xul, lib/entities.js: I moved entity definitions to their own file. Multiple files, renaming and adding of options: escapeHTML - changed to escapeForCss/escapeForTextNode/escapeForAttribute since the rules are slightly different depending on why it is being called. Attributes, since they are always displayed with double quotes would show a double quote in entity form, for example. Completely removing escapeHTML forced finding all the cases. showWhitespaceNodes - the way the code was, it was simply dealing with text nodes, not text nodes that contained only whitespace (which Fx has an attribute for, if I remember correctly). As such, it was showing whitespace inside text nodes, so I renamed it showTextNodesWithWhitespace. I needed this to keep things clear as to what things meant, but I no longer need the mental crutch, though it might be helpful to someone in the future. showTextNodesAsSource - open to a better name. This references the feature, both in display and in editing to treat the text as if it were source code. Thus show entities, and if a user types <b> they mean bold. With this option off, if a user types <b> it means as the browser would see it and converts it to <b>. lib.js: versionChecker/appInfo -- I didn't add these - and don't know where they come from. Any thoughts? Some functions were added to check if a node is xhtml/svg/mathml. Being xml derived, xhtml, mathml, svg all have issues with bad markup. So some error handling was added, since bad markup is the default while someone is editing a node and getting updates live. Some error handing was added that essentially cancels updates until it is conformant. SVG/MathML tags self close if empty. Also in html panel I found a list of void tags and updated selfClosingTags/invisibleTags html.js domplate stuff for textnode/textelement changed to use getNodeTextGroups which returns an array of strings and style information. Removal of WhitespaceNode. Split out TextNodeEditor from AttributeEditor (there was a todo comment from Joe to do so). TextNodeEditor deals with text nodes that have sibling elements by keeping track of their position via a range (this is in part because as people type html, the range will keep track of the text nodes and elements that the user is creating as they type, and this range could be in the middle of the parent elements children). editNode made to recognize the type of node and use a specialized editor. Just a hook for now. All editors are just aliases of HTMLEditor. Possible extension point. A MathML extension could use a ASCIIMathML based editor, for example, by replacing Firebug.HTMLPanel.Editors.MathML. htmlLib.js added hasCommentChildren reps.js remove MathMl -moz-XXX attributes that are really css getNodeText => getNodeTextGroups - return an array of string/class info for styling in domplate getContextMenuItems takes care of noticing svg/mathml nodes for the context menus

issue 2448 (Firebug HTML panel encoding display and editing) commented on by sroussey - Cleaned up and consolidated old comments: Issues addressed: Issue #2470 Issue #2453 Issue #2439 Issue #2438 Issue #2435 Issue #2359 Issue #2299 Issue #2250 Issue #1980 Issue #1588 Issue #1138 Issue #838 Notes: Entity handling is done by creating regexps to do splits (fastest), they get created on demand when needed and cached. While most conversions are straight forward, the conversions for text nodes are done in such a way that we can see which entity list was responsible for the purpose of marking up the entities with different styles. The Show White Space option and the Text As Source option style their entities/whitespace somewhat differently. XHTML/MathML/SVG: I personally don't see much use of these since they have to be served from the webserver in such a way that IE chokes on such documents. Even so, some people do use them, and thus they don't use IE. Likely they use Firefox, and thus Firebug if they are going to debug these documents. Firebug should at least not fail as much. I've added in some support, a little better handling of errors, and alter the UI to address them directly. When HTML5 comes around and it becomes a lot easier to use svg/mathml, additional direct support will be warranted. But for now, the goal was to work better and fail less. Firefox puts CSS styling stuff in attributes internally for MathML. This causes a number of problems. The quick fix was to remove them sight, when serializing to a string (copy and editing), and when showing in the html panel. Editing nodes with such styles could lead to their loosing of their styles. There should be more research on this, and likely an issue for fbug and one for Mozilla. In errors.js: I found that if I had chromebug set to break on errors, I would stop on a line that was checking for the existance of FBTrace, but it was undefined. I suppose this is why it is bracketed by try/catch but I dislike breaking on it, so I use typeof to see if it is undefined first (which the only way to see if a variable is defined or not without throwing an exception). browserOverlay.xul, lib/entities.js: I moved entity definitions to their own file. Multiple files, renaming and adding of options: escapeHTML - changed to escapeForCss/escapeForTextNode/escapeForAttribute since the rules are slightly different depending on why it is being called. Attributes, since they are always displayed with double quotes would show a double quote in entity form, for example. Completely removing escapeHTML forced finding all the cases. showWhitespaceNodes - the way the code was, it was simply dealing with text nodes, not text nodes that contained only whitespace (which Fx has an attribute for, if I remember correctly). As such, it was showing whitespace inside text nodes, so I renamed it showTextNodesWithWhitespace. I needed this to keep things clear as to what things meant, but I no longer need the mental crutch, though it might be helpful to someone in the future. showTextNodesAsSource - open to a better name. This references the feature, both in display and in editing to treat the text as if it were source code. Thus show entities, and if a user types they mean bold. With this option off, if a user types it means as the browser would see it and converts it to . lib.js: versionChecker/appInfo -- I didn't add these - and don't know where they come from. Any thoughts? Some functions were added to check if a node is xhtml/svg/mathml. Being xml derived, xhtml, mathml, svg all have issues with bad markup. So some error handling was added, since bad markup is the default while someone is editing a node and getting updates live. Some error handing was added that essentially cancels updates until it is conformant. SVG/MathML tags self close if empty. Also in html panel I found a list of void tags and updated selfClosingTags/invisibleTags html.js domplate stuff for textnode/textelement changed to use getNodeTextGroups which returns an array of strings and style information. Removal of WhitespaceNode. Split out TextNodeEditor from AttributeEditor (there was a todo comment from Joe to do so). TextNodeEditor deals with text nodes that have sibling elements by keeping track of their position via a range (this is in part because as people type html, the range will keep track of the text nodes and elements that the user is creating as they type, and this range could be in the middle of the parent elements children). editNode made to recognize the type of node and use a specialized editor. Just a hook for now. All editors are just aliases of HTMLEditor. Possible extension point. A MathML extension could use a ASCIIMathML based editor, for example, by replacing Firebug.HTMLPanel.Editors.MathML. htmlLib.js added hasCommentChildren reps.js remove MathMl -moz-XXX attributes that are really css getNodeText => getNodeTextGroups - return an array of string/class info for styling in domplate getContextMenuItems takes care of noticing svg/mathml nodes for the context menus

Cleaned up and consolidated old comments: Issues addressed: Issue #2470 Issue #2453 Issue #2439 Issue #2438 Issue #2435 Issue #2359 Issue #2299 Issue #2250 Issue #1980 Issue #1588 Issue #1138 Issue #838 Notes: Entity handling is done by creating regexps to do splits (fastest), they get created on demand when needed and cached. While most conversions are straight forward, the conversions for text nodes are done in such a way that we can see which entity list was responsible for the purpose of marking up the entities with different styles. The Show White Space option and the Text As Source option style their entities/whitespace somewhat differently. XHTML/MathML/SVG: I personally don't see much use of these since they have to be served from the webserver in such a way that IE chokes on such documents. Even so, some people do use them, and thus they don't use IE. Likely they use Firefox, and thus Firebug if they are going to debug these documents. Firebug should at least not fail as much. I've added in some support, a little better handling of errors, and alter the UI to address them directly. When HTML5 comes around and it becomes a lot easier to use svg/mathml, additional direct support will be warranted. But for now, the goal was to work better and fail less. Firefox puts CSS styling stuff in attributes internally for MathML. This causes a number of problems. The quick fix was to remove them sight, when serializing to a string (copy and editing), and when showing in the html panel. Editing nodes with such styles could lead to their loosing of their styles. There should be more research on this, and likely an issue for fbug and one for Mozilla. In errors.js: I found that if I had chromebug set to break on errors, I would stop on a line that was checking for the existance of FBTrace, but it was undefined. I suppose this is why it is bracketed by try/catch but I dislike breaking on it, so I use typeof to see if it is undefined first (which the only way to see if a variable is defined or not without throwing an exception). browserOverlay.xul, lib/entities.js: I moved entity definitions to their own file. Multiple files, renaming and adding of options: escapeHTML - changed to escapeForCss/escapeForTextNode/escapeForAttribute since the rules are slightly different depending on why it is being called. Attributes, since they are always displayed with double quotes would show a double quote in entity form, for example. Completely removing escapeHTML forced finding all the cases. showWhitespaceNodes - the way the code was, it was simply dealing with text nodes, not text nodes that contained only whitespace (which Fx has an attribute for, if I remember correctly). As such, it was showing whitespace inside text nodes, so I renamed it showTextNodesWithWhitespace. I needed this to keep things clear as to what things meant, but I no longer need the mental crutch, though it might be helpful to someone in the future. showTextNodesAsSource - open to a better name. This references the feature, both in display and in editing to treat the text as if it were source code. Thus show entities, and if a user types they mean bold. With this option off, if a user types it means as the browser would see it and converts it to . lib.js: versionChecker/appInfo -- I didn't add these - and don't know where they come from. Any thoughts? Some functions were added to check if a node is xhtml/svg/mathml. Being xml derived, xhtml, mathml, svg all have issues with bad markup. So some error handling was added, since bad markup is the default while someone is editing a node and getting updates live. Some error handing was added that essentially cancels updates until it is conformant. SVG/MathML tags self close if empty. Also in html panel I found a list of void tags and updated selfClosingTags/invisibleTags html.js domplate stuff for textnode/textelement changed to use getNodeTextGroups which returns an array of strings and style information. Removal of WhitespaceNode. Split out TextNodeEditor from AttributeEditor (there was a todo comment from Joe to do so). TextNodeEditor deals with text nodes that have sibling elements by keeping track of their position via a range (this is in part because as people type html, the range will keep track of the text nodes and elements that the user is creating as they type, and this range could be in the middle of the parent elements children). editNode made to recognize the type of node and use a specialized editor. Just a hook for now. All editors are just aliases of HTMLEditor. Possible extension point. A MathML extension could use a ASCIIMathML based editor, for example, by replacing Firebug.HTMLPanel.Editors.MathML. htmlLib.js added hasCommentChildren reps.js remove MathMl -moz-XXX attributes that are really css getNodeText => getNodeTextGroups - return an array of string/class info for styling in domplate getContextMenuItems takes care of noticing svg/mathml nodes for the context menus

Today

Yesterday