User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:188.8.131.52) Gecko/2009032609 Firefox/3.0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:184.108.40.206) Gecko/2009032609 Firefox/3.0.8 When altering the CSS property 'display: block;' of the standard (apply's to all pages) css file html.css (line 56) the following things will happen: - Firebug layout will mess up - Firefox rendering engine will mess up any webpages called in the future - The firefox chrome will mess up (the url bar goes empty when you hover it, the text will 'still be there') - Firefox will crash if the window is restored Reproducible: Always Steps to Reproduce: 1. Open a random webpage 2. Open firebug 3. Select the <html> element 4. Click the 'block' of the 'display: block;' line showed on the right 5. Remove the word 'block'; 6. Click anywere Actual Results: The messing up starts, here is to trigger some: - Load a page (or reload this one) - Minemize and restore firefox - Hover the address bar Expected Results: That firefox doesn't do the above things Sorry for the bad english.
Ow and btw im using Firebug version 1.3.3
Did you notified the Firebug developers about this issue ?
This issue is known, ua styles are not supposed to be changed, the styles are cached on startup (IIRC) not re-read.
@Matthias No i didn't but then i dont think a plug-in should be abel to mess up the whole program.
A plugin (like flash, java) can crash the browser, can format the hdd, do anything else with system but it will be possible to isolate plugins and this will be implemented in future versions but in this case is no plugin involved, Firebug is an addon. An addon can of course mess up the whole Firefox. There is no way to isolate addons. We implmented the Firefox safemode for example for addons that are breaking Firefox already at startup. Please always report such addon errors to the addon developers. They can itself write a bug if it's a bug in Firefox itself. -> invalid
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.