On Oct 15, 1:28 am, Andrew Dupont <[EMAIL PROTECTED]> wrote:
>
> This doesn't mean it's your duty to investigate, of course. Curtis,
> can you try to remove the non-Ajax-related stuff from the copy of
> Prototype that this SOAP library depends on? Specifically, you should
> be able to remove everything relating to arrays, plus everything that
> occurs after the Ajax section of the file. If those parts are removed,
> it'd help diagnose whether for..in on arrays is the true problem.
>

While I haven't tried to remove the non-Ajax-related stuff from
Prototype I have found a change to Prototype that seems to fix the
issue.

Looking at the block at line 1554-1569 of Prototype.js (v1.6.0) there
are three lines -- 1555, 1556, 1568 -- that reference "this.Element".
When "this.Element" is changed to "this.element" (casing change)
Firebug appears to work correctly. I don't fully understand this
change though; is it really a valid Prototype bug (a question for the
Prototype folks maybe) or is this just an anomoly.
--~--~---------~--~----~------------~-------~--~----~
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