Think in events for this one. When the Dom is parsed, a "onNodeDetected" event could be fired with the information about the node it found.
So <div id=d0> is translated into d0 = HTMLObject. That is also why you should make ID's unique. I am only guessing here though, but i think its done similar. Am 18.09.2014 um 14:42 schrieb Danny Dorfman <[email protected]>: > Suppose an HTML page looks something like this: > > <html> > <body> > <div id="d0">DDDDD</div> > <script> > alert("d0 = " + d0); > </script> > </body> > </html> > > When ran under Chrome the alert box will correctly state: > d0 = [object HTMLDivElement] > > How does V8 know that it needs to resolve the "d0" (as a DIV element), and > not return 'undefined'? > I need similar functionality in my code. > > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
