> > Re, issue 5650: Well, Sebastian, I clicked on window.a, then window.a.b, > then window.a.b.c, and finally window.a.b.c.d and the property path was not > displayed at any point. So I guess that issue 5650 is not a live demo - > darn it! > If you read carefully, issue 5650 is an enhancement request. Firebug does * not* change the property path just by clicking the property names at the moment.
I'm curious about a couple of other things. > > Why a > b > c > d ? Why not window.a.b.c.d ? Wouldn't that be more > intuitive? > Because that's how ancestor paths are displayed within Firebug. It might make sense to change the delimiter to a dot, though that's not part of that issue. > And, is it possible to open multiple independent Firebug windows so that > multiple properties can be monitored at the same time? No, but you could use the *Watch* side panel<http://getfirebug.com/wiki/index.php/Watch_Side_Panel>for this purpose by adding the properties as watches. Suggestion: As you may know, I wrote my own dom browser in 2003. I made all > of my domBrowser() functions and variables properties of domBrowse() > itself. That way they don't show up in the global scope. That keeps things > tidy. Perhaps you guys might do the same, eh? > Do you see something of Firebug in the global scope, which shouldn't be there? And an OT question: It's been a couple of years since I wrote DOM code. I > don't see constructors for the HTML5 elements like Footer (i.e., I can't > see a HTMLFooterElement() ). If I write: > > document.createDocumentFragment().appendChild(document.createElement("Footer")); > > > > an [object HTMLElement] is returned (i.e., it is the prototype of > HTML<tag>Element, is it not?). I hated when Microsoft did such things. > What's up with HTML5 and FireFox? > That's not a Firefox issue but defined that way in the HTML5 standard. See the DOM interface of http://www.w3.org/TR/2012/WD-html5-20120329/the-footer-element.html#the-footer-element in comparison to e.g. http://www.w3.org/TR/2012/WD-html5-20120329/the-img-element.html#the-img-element So if you want to complain, you should do that at the W3C. > Thanks for preparing the issue. Your service (and Honza's!) is appreciated > here. > You're welcome. If you have any other suggestions how to improve Firebug, feel free to create your own enhancement requests<http://code.google.com/p/fbug/issues/entry?template=User%20enhancement%20request>. But make sure you read our wiki page for making enhancement requests<http://getfirebug.com/wiki/index.php/I_am_missing_a_feature_in_Firebug%21>first. Sebastian -- 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
