Actually there is already an issue for this: http://code.google.com/p/fbug/issues/detail?id=791 Though comment 3 of this issue is still waiting for further discussion... What shall we do with issue 3505?
On Oct 4, 9:00 pm, "Jan Odvarko" <[email protected]> wrote: > Yep, make sense to me, please report a new issue so, it isn't forgotten here > in the noise. > > http://code.google.com/p/fbug/issues/list?start=0 > > Thanks! > Honza > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf > > Of ed > > Sent: Monday, October 04, 2010 8:54 PM > > To: Firebug > > Subject: Re: colors > > > You're correct. I hadn't touched my theme, but this a work notebook > > that came to me with a corporate defined theme. I switched to "windows > > classic" and can read the html panel now. I'm with Pedro, though if > > firebug is going to participate in windows themes, it needs to use > > theme colors for foreground and background colors to avoid contrast > > issues. > > > On Oct 4, 1:49 pm, Pedro Simonetti Garcia <[email protected]> > > wrote: > > > Hi Ed and Honza, > > > > The "highlight" color is defined as a "system color", so it will > > > depend on the color settings of the OS. I guess Ed is using a > > > different color theme than the default, or classic. > > > > Anyway, in my opinion we should avoid using system colors because we > > > can't predict what colors will be used, and therefore, we can't > > > prevent color-contrast problems such as this one reported by Ed. > > > > regards, > > > > Pedro Simonetti. > > > > 2010/10/4 Honza (Jan Odvarko) <[email protected]>: > > > > >> I should have included that I'm running windows xp professional sp3 > > > > I am also running WinXP (on other machine), but my screen looks > > > > different comparing to your screenshot. What Firefox theme do you use? > > > > Or could it be a custom OS theme that could cause the difference? > > > > > Honza > > > > > On Oct 4, 7:19 pm, ed <[email protected]> wrote: > > > >> I should have included that I'm running windows xp professional sp3 > > > > >> On Oct 4, 1:14 pm, Ed Schiebel <[email protected]> wrote: > > > > >> > I see this problem with both 1.5.4 and 1.6b1 running in firefox > > 3.6.10 > > > >> > (though it's been this way for a long time). I've attached 3 > > images. > > > >> > normal_div shows a normal, visible div highlighted in the HTML tab > > > >> > hidden_div shows a div with style="display:none" highlighted in the > > HTML tab > > > >> > orphan_div shows a div created via document.createElement("div"), > > but not > > > >> > added to the document yet. To get this, I used the console to show > > me > > > >> > orphan_div, then clicked on the link. > > > > >> > as you can see, in the last 2, the HTML is unreadable. > > > >> > --ed > > > > >> > > Topic: > > colors<http://groups.google.com/group/firebug/t/9a5f273c3710be36> > > > > >> > > Jan Odvarko <[email protected]> Oct 04 01:54PM +0200 > > ^<#12b781ebb1f38450_digest_top> > > > > >> > > What Firebug version do you use? > > > > >> > > I have tried that with Firebug 1.6 and selected HTML nodes (in > > the HTML > > > >> > > panel) are always using blue background with white text, > > doesn't matter > > > >> > > if > > > >> > > the selected node is currently visible or not. > > > > >> > > http://getfirebug.com/releases/firebug/1.6X/firebug- > > 1.6X.0b1.xpi > > > > >> > > I am attaching a screenshot. > > > > >> > > But perhaps, I don't understand the problem well? > > > > >> > > Honza > > > > >> > > Topic: New Feature Request: Saving > > Profiles<http://groups.google.com/group/firebug/t/b069070d680c6163> > > > > >> > > "Honza (Jan Odvarko)" <[email protected]> Oct 04 04:47AM -0700 > > ^<#12b781ebb1f38450_digest_top> > > > > >> > > Seehttps://addons.mozilla.org/en-US/firefox/addon/2108/ > > > > >> > > Honza > > > > >> > > Topic: about memory > > breakpoint<http://groups.google.com/group/firebug/t/9d187c503bb7ee36> > > > > >> > > aj3423 <[email protected]> Oct 04 06:13PM +0800 > > ^<#12b781ebb1f38450_digest_top> > > > > >> > > in some debugger like ollydbg, user can set a break point to a > > memory > > > >> > > address, when there is a read/write access to that memory > > address, the > > > >> > > debugger will break. I think it is very useful in javascript > > debugging. > > > >> > > Sometime my variable value is changed and I couldn't found > > where it is > > > >> > > modified. It'll be great if I can set a variable break point > > to > > > >> > > variables > > > >> > > like a.b.c, then it breaks when the code does a.b.c = 123, > > > >> > > Is it possible for the enhancement? Will firebug add the new > > 'variable > > > >> > > break > > > >> > > point' in the future version? > > > > >> > > Thanks. > > > > >> > > "Honza (Jan Odvarko)" <[email protected]> Oct 04 04:41AM -0700 > > ^<#12b781ebb1f38450_digest_top> > > > > >> > > There is already partial support for this within the DOM > > panel. > > > > >> > > For example, if you have an object a = {prop1: 1, prop2: 2} > > you can > > > >> > > create a breakpoint for its properties. > > > > >> > > 1) Select the DOM panel > > > >> > > 2) Expand the object |a| > > > >> > > 3) Create a breakpoint for |prop1| by clicking on the > > breakpoint > > > >> > > column. > > > >> > > 4) Change the value -> Firebug's debugger should break and > > switch to > > > >> > > the Script panel showing the source line that caused the > > break; > > > > >> > > See more here: > > > >> > > http://getfirebug.com/doc/breakpoints/demo.html#dom > > > > >> > > Honza > > > > >> > > Topic: Firebug : How to make net tab > > persistent?<http://groups.google.com/group/firebug/t/f6a170f73054ba71> > > > > >> > > "Honza (Jan Odvarko)" <[email protected]> Oct 04 04:37AM -0700 > > ^<#12b781ebb1f38450_digest_top> > > > > >> > > > Off line Honza and I agreed to just let the Persist be > > manual: you > > > >> > > > will accumulate net traffic until you press it off. > > > >> > > Will be in Firebug 1.7a3 > > > >> > > Honza > > > > >> > > -- > > > >> > > You received this message because you are subscribed to the > > Google Groups > > > >> > > "Firebug" group. > > > >> > > To post to this group, send email to [email protected]. > > > >> > > To unsubscribe from this group, send email to > > > [email protected]<firebug%[email protected] > > m > > > > >> > > . > > > >> > > For more options, visit this group at > > > >> > >http://groups.google.com/group/firebug?hl=en. > > > > >> > normal_div.jpg > > > >> > 53KViewDownload > > > > >> > hidden_div.jpg > > > >> > 52KViewDownload > > > > >> > orphan_div.jpg > > > >> > 55KViewDownload > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups "Firebug" group. > > > > To post to this group, send email to [email protected]. > > > > To unsubscribe from this group, send email to > > [email protected]. > > > > For more options, visit this group > > athttp://groups.google.com/group/firebug?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Firebug" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/firebug?hl=en. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
