On 2010-06-15 10:56, John J Barton wrote:
On Jun 15, 12:19 am, Nicolas Hatier<[email protected]> wrote:
I first noticed issue #3078
<http://code.google.com/p/fbug/issues/detail?id=3078> was back in
Firebug 1.6X.0a12 / Firefox 3.6.3
3078 is about scrolling to the bottom and a12 just came out last
night. So the title of your post seems a bit dramatic ;-)
Well, the title applied to the whole set of errors I get with a12 which
makes it pretty unusable here, not just to issue 3078, which is more a
small recurring annoyance than anything else.
The test case should
behttp://getfirebug.com/tests/content/console/3078/issue3078.html- but it
completely fails for another unrelated reason, I get "element is undefined
(49 out of range 27)"
This is an error in our console injection code. Firefox assigns the
same URL to dynamic code as to static code, so the error messages for
dynamic code are junk. So the message is weird, but Firebug can't fix
that.
Then I saw that new Firebug version was behaving incorrectly in several
other cases, throwing incoherent errors "element is undefined" for code
working perfectly with previous FB versions.
Is it possible something in the code refactoring went very wrong?
Yes of course it is possible. But the cause of the above error message
is simpler: we use the 'body' tag to support the console and your
example code runs before the body tag is defined:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2<html>
3<head>
4<title>Test Case for Issue #3078</title>
5<script>
6 for (var i = 0; i< 300; ++i)
7 console.log(i); // Firebug tries use the body tag here and it fails
with "element is undefined".
8</script>
9</head>
10<body>
Ok, that makes sense. Issue #3078 was about auto-scrolling when
console.log is used in the <head> section, I use that a lot...
Didn't create a bug report yet because of the scope of this issue - I
wouldn't know where to begin.
Wow I wish every bug report came with a great test case like you
posted here.
Well... I get bug reports for my products too, I know what I like to
receive from my users :-)
Unfortunately some of them are still "this is broken, fix it. NOW!" :-(
All tested in a brand new profile containing no extension beside Firebug.
Thanks!
jjb
Let me know if there's anything else I can provide. I'll be testing this
in the next alpha or beta release.
NH
NH
--
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.
