On 2012-06-26 12:14 PM, Jan Honza Odvarko wrote:
On Jun 26, 5:55 pm, Mark Filipak <[email protected]>
-snip-
Included is a getElementById('<clickable-link>') etc. ...very handy.
Not sure what is this feature about...?
My DOM Browser opens in one or more child windows (depending upon how many calls to domBrowse() have been
inserted into the code, and where, and whether the domBrowse instances have been supplied with any
arguments--by object or by reference). Then, in the particular child window associated with an instance
of domBrowse(), one can click on <property-path>.getElementById(), for example, and supply an
argument ("foo", for example) and see it take effect immediately (jump directly to the
id="foo" element in the DOM tree, for example). I have implemented this functionality for all
functions. It is very handy.
Obviously, each domBrowse() generated auxiliary window is communicating with
its parent window (which contains the actual document or a 'higher' level of a
domBrowse() generated child window). Changes made via function arguments in
child windows take effect globally so that the results are acted upon by the
parent window. That's very handy too. If the function alters the DOM tree, the
resulting scope remains rooted to the global object (window), but if the
function provokes an event, the scope is rooted to the event object and the
returned object in the child window is the event object.
- Mark.
--
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
https://groups.google.com/forum/#!forum/firebug
