Firebug 1.9b5
290 views
Skip to first unread message
Jan Honza Odvarko
Dec 23, 2011, 8:36:12 AM12/23/11
to fir...@googlegroups.com
Arthur Berkell
Dec 26, 2011, 9:18:15 PM12/26/11
to fir...@googlegroups.com
I don't think I'm that dense, but I'll be damned if I can find the link from which to download 1.9b5. The "ready to install" link leads you to another page, which in turn puts you back on the page with "ready to install". The non-obviousness of the link from which to download a new firebug version is more-or-less ubiquitous in this arena. Usually, I can find the proper link after a few false clicks, but this time around it's totally missing. (Or so it seems.)
Arthur Berkell
Dec 26, 2011, 9:18:45 PM12/26/11
to fir...@googlegroups.com
BTW, Firebug is a great too - close to indespensible!
Andrew Whitfield
Dec 28, 2011, 5:17:51 PM12/28/11
to fir...@googlegroups.com
First time posting. Absolutely love FireBug.
I've just updated to Firefox 10.0 and Firebug 1.9b5.
I've noticed that pressing F12 brings up Firebug like normal but doesn't load the console properly. You have to press F12 twice to bring up the console. Causing deliberate JavaScript errors doesn't cause errors to show up in the console either. I think there's something in the latest update that's tripping up the console itself. The HTML tab works fine and CSS editing works fine.
I'm on Windows 7 as well.
The firebug options button (which appears on the row to the left of the element select button) doesn't trigger the menu to open like it did in previous versions.
Anything I can do to help you with these?
Kindest thanks for an amazing creation.
Andrew
I've just updated to Firefox 10.0 and Firebug 1.9b5.
I've noticed that pressing F12 brings up Firebug like normal but doesn't load the console properly. You have to press F12 twice to bring up the console. Causing deliberate JavaScript errors doesn't cause errors to show up in the console either. I think there's something in the latest update that's tripping up the console itself. The HTML tab works fine and CSS editing works fine.
I'm on Windows 7 as well.
The firebug options button (which appears on the row to the left of the element select button) doesn't trigger the menu to open like it did in previous versions.
Anything I can do to help you with these?
Kindest thanks for an amazing creation.
Andrew
Jan Honza Odvarko
Jan 2, 2012, 3:22:10 AM1/2/12
to fir...@googlegroups.com
On Tuesday, December 27, 2011 3:18:15 AM UTC+1, Arthur Berkell wrote:
I don't think I'm that dense, but I'll be damned if I can find the link from which to download 1.9b5. The "ready to install" link leads you to another page, which in turn puts you back on the page with "ready to install".
The link should be already fixed.
Honza
Honza
Jan Honza Odvarko
Jan 2, 2012, 3:31:51 AM1/2/12
to fir...@googlegroups.com
On Wednesday, December 28, 2011 11:17:51 PM UTC+1, Andrew Whitfield wrote:
I've noticed that pressing F12 brings up Firebug like normal but doesn't load the console properly. You have to press F12 twice to bring up the console. Causing deliberate JavaScript errors doesn't cause errors to show up in the console either. I think there's something in the latest update that's tripping up the console itself.
I am not sure if I understand the problem, what exactly should I do to see it?
Here is what I am trying:
1) Load http://getfirebug.com/tests/content/branches/1.9/console/872/main.html
2) Press F12 to activate Firebug (opens Firebug UI)
3) Select and Enable the Console panel
4) Refresh the page
5) The console panel is displaying an error log: "This is an error from an iframe!"
Here is what I am trying:
1) Load http://getfirebug.com/tests/content/branches/1.9/console/872/main.html
2) Press F12 to activate Firebug (opens Firebug UI)
3) Select and Enable the Console panel
4) Refresh the page
5) The console panel is displaying an error log: "This is an error from an iframe!"
I'm on Windows 7 as well.
The firebug options button (which appears on the row to the left of the element select button) doesn't trigger the menu to open like it did in previous versions.
This seems to be working for me. Do you see any errors in Firefox error Console?
Anything I can do to help you with these?
Regarding to the Console panel problem:
Please provide a test page with detailed steps-to-reproduce
Regarding to the option menu:
Do you see any errors if you install Firebug Tracing Console and check the ERRORS option?
http://getfirebug.com/releases/fbtrace/1.9/fbTrace-1.9b4.xpi
Honza
Andrew Whitfield
Jan 2, 2012, 8:53:27 AM1/2/12
to Firebug
Happy New Year!
Here's a sample page:
http://www.mystream.co.uk/this-should-break.html
I've added this code:
<script type="text/javascript">
var a=;
</script>
which should trigger an error in firefox.
Here's a JS Fiddle of the code/error.
http://jsfiddle.net/Q7pGX/
If I open this code in Firefox and then press F12, I see no error
triggered (that's fine - it's not yet open when the error happened, so
that makes sense). So, with the console open, now refresh the page
and watch the console.
Here's a video of what I am seeing for the steps below:
a) Open http://www.mystream.co.uk/this-should-break.html with Firebug
open
b) Observe that no error is shown
c) Press f12 again and it brings up the actual right hand side console
window
d) Refresh the page
e) No errors reported
Video URL: http://www.mystream.co.uk/firebug-anomaly.mp4
I have installed this Add-On as well:
http://getfirebug.com/releases/fbtrace/1.9/fbTrace-1.9b4.xpi
On loading just the url above, I saved the results to a file here:
http://www.mystream.co.uk/firebug-tracing-logs.ftl
I have also visited the url below with the iframe and no error is
shown in FireBug's console (or elsewhere that I can see so far).
I've left the Tracing window open during the video so you can see if
there's something I should be doing to help with the debugging
process. Please let me know if there's anything I can provide to help
narrow down the steps.
Kindest Thanks,
Andrew
On Jan 2, 8:31 am, Jan Honza Odvarko <odva...@gmail.com> wrote:
> On Wednesday, December 28, 2011 11:17:51 PM UTC+1, Andrew Whitfield wrote:
>
> > I've noticed that pressing F12 brings up Firebug like normal but doesn't
> > load the console properly. You have to press F12 twice to bring up the
> > console. Causing deliberate JavaScript errors doesn't cause errors to show
> > up in the console either. I think there's something in the latest update
> > that's tripping up the console itself.
>
> I am not sure if I understand the problem, what exactly should I do to see
> it?
>
> Here is what I am trying:
>
> 1) Loadhttp://getfirebug.com/tests/content/branches/1.9/console/872/main.html
Here's a sample page:
http://www.mystream.co.uk/this-should-break.html
I've added this code:
<script type="text/javascript">
var a=;
</script>
which should trigger an error in firefox.
Here's a JS Fiddle of the code/error.
http://jsfiddle.net/Q7pGX/
If I open this code in Firefox and then press F12, I see no error
triggered (that's fine - it's not yet open when the error happened, so
that makes sense). So, with the console open, now refresh the page
and watch the console.
Here's a video of what I am seeing for the steps below:
a) Open http://www.mystream.co.uk/this-should-break.html with Firebug
open
b) Observe that no error is shown
c) Press f12 again and it brings up the actual right hand side console
window
d) Refresh the page
e) No errors reported
Video URL: http://www.mystream.co.uk/firebug-anomaly.mp4
I have installed this Add-On as well:
http://getfirebug.com/releases/fbtrace/1.9/fbTrace-1.9b4.xpi
On loading just the url above, I saved the results to a file here:
http://www.mystream.co.uk/firebug-tracing-logs.ftl
I have also visited the url below with the iframe and no error is
shown in FireBug's console (or elsewhere that I can see so far).
I've left the Tracing window open during the video so you can see if
there's something I should be doing to help with the debugging
process. Please let me know if there's anything I can provide to help
narrow down the steps.
Kindest Thanks,
Andrew
On Jan 2, 8:31 am, Jan Honza Odvarko <odva...@gmail.com> wrote:
> On Wednesday, December 28, 2011 11:17:51 PM UTC+1, Andrew Whitfield wrote:
>
> > I've noticed that pressing F12 brings up Firebug like normal but doesn't
> > load the console properly. You have to press F12 twice to bring up the
> > console. Causing deliberate JavaScript errors doesn't cause errors to show
> > up in the console either. I think there's something in the latest update
> > that's tripping up the console itself.
>
> I am not sure if I understand the problem, what exactly should I do to see
> it?
>
> Here is what I am trying:
>
> 2) Press F12 to activate Firebug (opens Firebug UI)
> 3) Select and Enable the Console panel
> 4) Refresh the page
> 5) The console panel is displaying an error log: "This is an error from an
> iframe!"
>
>
>
> > I'm on Windows 7 as well.
>
> > The firebug options button (which appears on the row to the left of the
> > element select button) doesn't trigger the menu to open like it did in
> > previous versions.
>
> This seems to be working for me. Do you see any errors in Firefox error
> Console?
>
> > Anything I can do to help you with these?
>
> Regarding to the Console panel problem:
> Please provide a test page with detailed steps-to-reproduce
>
> Regarding to the option menu:
> Do you see any errors if you install Firebug Tracing Console and check the
> ERRORS option?http://getfirebug.com/releases/fbtrace/1.9/fbTrace-1.9b4.xpi
> 3) Select and Enable the Console panel
> 4) Refresh the page
> 5) The console panel is displaying an error log: "This is an error from an
> iframe!"
>
>
>
> > I'm on Windows 7 as well.
>
> > The firebug options button (which appears on the row to the left of the
> > element select button) doesn't trigger the menu to open like it did in
> > previous versions.
>
> This seems to be working for me. Do you see any errors in Firefox error
> Console?
>
> > Anything I can do to help you with these?
>
> Regarding to the Console panel problem:
> Please provide a test page with detailed steps-to-reproduce
>
> Regarding to the option menu:
> Do you see any errors if you install Firebug Tracing Console and check the
Jan Honza Odvarko
Jan 2, 2012, 11:09:28 AM1/2/12
to fir...@googlegroups.com
On Monday, January 2, 2012 2:53:27 PM UTC+1, Andrew Whitfield wrote:
I've left the Tracing window open during the video so you can see if
there's something I should be doing to help with the debugging
process. Please let me know if there's anything I can provide to help
narrow down the steps.
I can't play the video, it's just black (anybody can?)
Anyway, I am seeing an exception coming from Flashbug in the attached log.
Does it help if you disable Flashbug? (and perhaps any other extension except Firebug)
Honza
Anyway, I am seeing an exception coming from Flashbug in the attached log.
Does it help if you disable Flashbug? (and perhaps any other extension except Firebug)
Honza
Sebo
Jan 2, 2012, 12:16:28 PM1/2/12
to fir...@googlegroups.com
I can't play the video, it's just black (anybody can?)
I can with VLC and I see a lot of Firebug extensions. Andrew, if it's not Flashbug, that causes the problem, please disable the other extensions and enable them again one by one as described in I found a Firebug bug! to find out, which one is the culprit.
Happy New Year!
Sebastian
Happy New Year!
Sebastian
Andrew Whitfield
Jan 2, 2012, 1:54:40 PM1/2/12
to Firebug
Hi Sebastian,
I hope you're well.
I disabled all of the plugins and re-enabled them again as needed. I
removed SenSEO, FlashBug, Flash FireBug and EventBug. One of these
seems to have caused the issue, but I couldn't say for certain which
one. None gave any direct error, but bugginess did seem to arise from
having one or more of these enabled with the current version of
Firefox/Firebug combination.
Thank you for the heads-up and reminder to keep it simple :)
Kindest,
Andrew
On Jan 2, 5:16 pm, Sebo <sebastianzart...@gmx.de> wrote:
> > I can't play the video, it's just black (anybody can?)
>
> I can with VLC and I see a lot of Firebug extensions. Andrew, if it's not
> Flashbug, that causes the problem, please disable the other extensions and
> enable them again one by one as described in *I found a Firebug bug!*<http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug%21>to find out, which one is the culprit.
>
> Happy New Year!
>
> Sebastian
I hope you're well.
I disabled all of the plugins and re-enabled them again as needed. I
removed SenSEO, FlashBug, Flash FireBug and EventBug. One of these
seems to have caused the issue, but I couldn't say for certain which
one. None gave any direct error, but bugginess did seem to arise from
having one or more of these enabled with the current version of
Firefox/Firebug combination.
Thank you for the heads-up and reminder to keep it simple :)
Kindest,
Andrew
On Jan 2, 5:16 pm, Sebo <sebastianzart...@gmx.de> wrote:
> > I can't play the video, it's just black (anybody can?)
>
> I can with VLC and I see a lot of Firebug extensions. Andrew, if it's not
> Flashbug, that causes the problem, please disable the other extensions and
>
> Happy New Year!
>
> Sebastian
Andrew Whitfield
Jan 2, 2012, 1:55:40 PM1/2/12
to Firebug
Hi Honza,
I'm not sure which one did the trick, but it was one of the ones
listed below that seems to have caused the conflict.
Many thanks again for a fabulous and essential addon.
Kindest,
Andrew
I'm not sure which one did the trick, but it was one of the ones
listed below that seems to have caused the conflict.
Many thanks again for a fabulous and essential addon.
Kindest,
Andrew
dotnetCarpenter
Jan 3, 2012, 3:24:53 PM1/3/12
to fir...@googlegroups.com
Hi Honza.
There seems to be an issue with rotated elements (-moz-transform: rotate(270deg);) and the in-page visual highlight. It's rather confusing. I don't have time right now to produce a test case (should be rather trivial though) but was just wondering if I'm the only one to see it.
Firebug: 1.9b5
Firefox: 9.0.1
OS: Linux/Ubuntu 11.04
Cheers, Jon
There seems to be an issue with rotated elements (-moz-transform: rotate(270deg);) and the in-page visual highlight. It's rather confusing. I don't have time right now to produce a test case (should be rather trivial though) but was just wondering if I'm the only one to see it.
Firebug: 1.9b5
Firefox: 9.0.1
OS: Linux/Ubuntu 11.04
Cheers, Jon
Mike Ratcliffe
Jan 3, 2012, 5:49:05 PM1/3/12
to Firebug
Do you mean that the box model highlighter (the one that shows margins
etc.) appears where the element was before the transform was applied
to it? If you do then this behavior is correct because transforms do
not effect the box model ... all margins etc. are applied to the
element as if it is not transformed.
~Mike Ratcliffe
etc.) appears where the element was before the transform was applied
to it? If you do then this behavior is correct because transforms do
not effect the box model ... all margins etc. are applied to the
element as if it is not transformed.
~Mike Ratcliffe
Sebo
Jan 4, 2012, 2:02:51 AM1/4/12
to fir...@googlegroups.com
If you're meaning the Inspector frame, than this is issue 2273.
Also note, that bug 591718 was fixed lately, which causes Inspector frame problems. Though this is currently only visible in FF 12.0a1.
Sebastian
Also note, that bug 591718 was fixed lately, which causes Inspector frame problems. Though this is currently only visible in FF 12.0a1.
Sebastian
Jan Honza Odvarko
Jan 4, 2012, 4:24:52 AM1/4/12
to fir...@googlegroups.com
On Tuesday, January 3, 2012 9:24:53 PM UTC+1, dotnetCarpenter wrote:
Hi Honza.
There seems to be an issue with rotated elements (-moz-transform: rotate(270deg);) and the in-page visual highlight. It's rather confusing. I don't have time right now to produce a test case (should be rather trivial though) but was just wondering if I'm the only one to see it.
Jon Ronnenberg
Jan 5, 2012, 4:33:51 PM1/5/12
to fir...@googlegroups.com
Just read through the bug reports. I'm glad it's reported and appreciate the complexity of the task. It pains me that the work-around is using Chrome. I poked around their Inspector code for a bit but didn't find anything.
I guess you could close version 1.9 without fixing this bug as it relates to a firefox bug. Waiting for firefox 12 is however an unfortunate reality IMHO.
I guess you could close version 1.9 without fixing this bug as it relates to a firefox bug. Waiting for firefox 12 is however an unfortunate reality IMHO.
2012/1/4 Jan Honza Odvarko <odv...@gmail.com>
--
You received this message because you are subscribed to the Google
Groups "Firebug" group.
To post to this group, send email to fir...@googlegroups.com
To unsubscribe from this group, send email to
firebug+u...@googlegroups.com
For more options, visit this group at
https://groups.google.com/forum/#!forum/firebug
Sebo
Jan 6, 2012, 6:53:18 AM1/6/12
to fir...@googlegroups.com
Just read through the bug reports. I'm glad it's reported and appreciate the complexity of the task. It pains me that the work-around is using Chrome. I poked around their Inspector code for a bit but didn't find anything.
I guess you could close version 1.9 without fixing this bug as it relates to a firefox bug. Waiting for firefox 12 is however an unfortunate reality IMHO.
As described in the issues we can just fix issue 4416 and issue 2273 as soon as Firefox exposes the right API, which is still not implemented. So we can't say yet, in which Firebug version these will be fixed, but it definitely won't be 1.9.
Sebastian
Sebastian
Reply all
Reply to author
Forward
0 new messages