Firebug 1.3a3 on getfirebug.com/releases
3 views
Skip to first unread message
John J Barton
Oct 2, 2008, 5:59:54 PM10/2/08
to Firebug
getfirebug.com/releases should offer Firebug 1.3a3 shortly. This
version has more changes than earlier alphas:
1) 1.3X traceConsole added, FBTrace panel removed. Tracing now need
not go to the OS console window but rather is presented in the new
Firebug Trace Console using Firebug technology for display.
2) Re-write of Firebug console implementation. Attempt to address
intermittent "console undefined" messages. Many console bugs fixed.
3) Array presentation bugs fixed.
4) Added scope chain to Watches panel when stopped in debugger
4) different algorithm for routing debugger info.
So its possible that a3 will be a bit rougher that a2.
We plan to start 1.3 beta on Monday Oct. 6.
jjb
version has more changes than earlier alphas:
1) 1.3X traceConsole added, FBTrace panel removed. Tracing now need
not go to the OS console window but rather is presented in the new
Firebug Trace Console using Firebug technology for display.
2) Re-write of Firebug console implementation. Attempt to address
intermittent "console undefined" messages. Many console bugs fixed.
3) Array presentation bugs fixed.
4) Added scope chain to Watches panel when stopped in debugger
4) different algorithm for routing debugger info.
So its possible that a3 will be a bit rougher that a2.
We plan to start 1.3 beta on Monday Oct. 6.
jjb
jjathman
Oct 5, 2008, 2:12:25 PM10/5/08
to Firebug
It looks like 1.3a3 seems to be putting my site in to quirks mode
incorrectly. When I revert to 1.3a2 the site looks normal again. I'm
not really sure how to help debug this, but I can give as more
information if someone tells me what to look for. The site is only
internal so I can't give a link to it, sorry.
Joe
incorrectly. When I revert to 1.3a2 the site looks normal again. I'm
not really sure how to help debug this, but I can give as more
information if someone tells me what to look for. The site is only
internal so I can't give a link to it, sorry.
Joe
John J Barton
Oct 5, 2008, 2:34:31 PM10/5/08
to Firebug
How did you decide it was in quirks mode?
We have a bug report about the problem:
http://code.google.com/p/fbug/issues/detail?id=1190
but no clue. (This problem also happens in 1.2 but much less common).
But quirks mode is a great hint: maybe the console injection is
interfering with doctype detection?
jjb
We have a bug report about the problem:
http://code.google.com/p/fbug/issues/detail?id=1190
but no clue. (This problem also happens in 1.2 but much less common).
But quirks mode is a great hint: maybe the console injection is
interfering with doctype detection?
jjb
jjathman
Oct 5, 2008, 4:28:20 PM10/5/08
to Firebug
Well whenever the page looks "weird" I inspect the CSS and turn on
"Show User Agent CSS" option and I see a "quirks.css" stylesheet
listed. I just kind of assumed that meant it was in quirks mode. The
problem mentioned in issue 1190 looks kind of similar to mine. The
size of some text and fields just does not look right. Is that any
help?
Joe
"Show User Agent CSS" option and I see a "quirks.css" stylesheet
listed. I just kind of assumed that meant it was in quirks mode. The
problem mentioned in issue 1190 looks kind of similar to mine. The
size of some text and fields just does not look right. Is that any
help?
Joe
jjathman
Oct 5, 2008, 4:29:20 PM10/5/08
to Firebug
Oops. It is actually "quirk.css", not "quirks.css".
jjathman
Oct 5, 2008, 4:36:09 PM10/5/08
to Firebug
I can also confirm that disabling the console (Script and Net are both
still enabled) returns the page to normal. Also, with the console
enabled I see an element in my HTML like this:
<div id="_firebugConsole" style="display: none;"
FirebugVersion="1.3.0a3"/>
I assume this is expected, I just hadn't ever noticed it with previous
FB versions. Thanks.
Joe
still enabled) returns the page to normal. Also, with the console
enabled I see an element in my HTML like this:
<div id="_firebugConsole" style="display: none;"
FirebugVersion="1.3.0a3"/>
I assume this is expected, I just hadn't ever noticed it with previous
FB versions. Thanks.
Joe
John J Barton
Oct 7, 2008, 1:37:14 AM10/7/08
to Firebug
1.3a4 or b1 will have a fix for this problem (and hide the element as
well). Thanks for your help.
well). Thanks for your help.
jjathman
Oct 7, 2008, 3:21:32 PM10/7/08
to Firebug
Great! Thanks, I look forward to trying it out.
Joe
Joe
Reply all
Reply to author
Forward
0 new messages