The internal model of the autocomplete system may cause issue, simply
because it evals statements. I understand this is a handy way to get the
properties of an object, but if the statement being typed is, for
instance, a function call which itself does a xmlHttpRequest to the
server, repeatedly eval'ing the statement could have very undesirable
effects.
Example. I have in my code a function doing a xmlHTTPRequest and
returning the result in the form of a "rendered" JSON object. If I
decide to test the call in the console, like this:
> MyXmlFunctionCall("MyRequest")
everything is Ok.
But if I want to test the result of the call directly, like that:
MyXmlFunctionCall("MyRequest").someProperty
The 'MyXmlFunctionCall("MyRequest")' part is called between 2 and 13
times by the internal eval(), one time for the dot and the first letter,
then one time for each of the letters I decide to type instead of using
autocomplete.
I'm not sure I have a solution for this. It's probably impossible for
Firebug to guess what type of function will be called with those eval().
Maybe Firebug should eval only objects and native function calls, and
not try to autocomplete the result of a user function. That would be a
start...
Nicolas
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to fire...@googlegroups.com.
To unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
