Thanks for the bug report. For what its worth my 1.3b1 shows:
Call: 1
Call: 2
Call: 3
Call: 4
Call: 5
Call: 6
On Oct 21, 10:50 am, JMJimmy <[EMAIL PROTECTED]> wrote:
> Thanks for your reply John, I found the proper place to report this
> after posting here - sorry about that. Included version info there.
> Bug 1219.
>
> I'll give 1.3 a try and let you know in that bug. Please disregard
> this thread.
>
> Thank you,
>
> JMJimmy
>
> On Oct 21, 1:44 pm, John J Barton <[EMAIL PROTECTED]> wrote:
>
> > Please let us know which version of Firebug and Firefox. Please try
> > Firebug 1.3 since this is the version we are fixing.
> > jjb
>
> > On Oct 21, 10:23 am, JMJimmy <[EMAIL PROTECTED]> wrote:
>
> > > I just completed ajax queue system and I ran into a rather serious
> > > problem with Firebug.
>
> > > I run a series of calls onload to get 6 unique files an process them
> > > in the order they were called as a test script.
>
> > > <BODY ONLOAD="ajaxTextGet('hello.txt'); ajaxTextGet('hello2.txt');
> > > ajaxTextGet('hello3.txt'); ajaxTextGet('hello4.txt');
> > > ajaxTextGet('hello5.txt'); ajaxTextGet('hello6.txt');">
>
> > > They contain a one line instruction to do a document.body.innerHTML =
> > > document.body.innerHTML + '<DIV>Call: ' and then JS adds a number and
> > > the closing </DIV>.
>
> > > The result on all browsers (including Firefox with Firebug disabled)
> > > is
>
> > > Call: 1
> > > Call: 2
> > > Call: 3
> > > Call: 4
> > > Call: 5
> > > Call: 6
>
> > > When Firebug is enabled it usually gives me:
>
> > > Call: 2
> > > Call: 1
> > > Call: 3
> > > Call: 4
> > > Call: 5
> > > Call: 6
>
> > > or some other variation.
>
> > > It's manifesting in two ways:
>
> > > 1) The initial onload calls are not in order - ie: executed as 1, 3,
> > > 2, 6, 4, 5 (or some variation)
> > > 2) If the initial calls are called correctly (1, 2, 3, 4, 5, 6) the
> > > resulting DOM updates are not applied in order ie: updated as shown
> > > above, 2,1,3,4,5,6 (or some variation)
>
> > > This only occurs when Firebug is enabled, and it is very consistent
> > > when it's enabled - it almost always happens. In all other browsers
> > > (Windows - Opera, Firefox (-Firebug), IE7, Chrome, Safari; OSX -
> > > Firefox, Safari) it works as expected every time. The second Firebug
> > > is enabled it screws up.
>
> > >http://www.phpdev.ca/canshare/index_1.0.0.php-soyou can see what is
> > > going on. If you look at the DOM portion you'll notice a variable
> > > called 'tracer' - this is the order of events being executed in the
> > > code which should match the result on the page (but does not due to
> > > bug).
>
> > > Details on my Firebug config:
> > > YSlow installed
> > > All 'Show' options are enabled, with the exception of DOM constants.
>
> > > JMJimmy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to firebug@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
