Hi,

I have tried to do a small test case for this issue, as I am also 
affected by this bug.

I put the test case on publicly available site, and guess what?
It works like a charm.

Here is the test case:
http://tsalarioth.art.pl/~sw/firebug_test/firebug.xhtml

It includes prototype.js, a slightly modified 1.6.0.2 version, which 
is one of the files not showing its source in our intranet.

If I change the <script src=...> from that public site, so the 
prototype is downloaded from our intranet, then I get the bug. If the 
prototype is loaded from public server, then bug seems to be fixed.

So, I think this might be related to some HTTP response headers sent 
by server, or other server configuration differences, and NOT to the 
CONTENT or LENGTH of the javascript files.

I will try to post some details of the differences in configuration
and try to reproduce exact behavior of our intranet server in that 
public site later today.

-- 
Regards,
SWilk

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to