On Thursday, November 24, 2016 at 8:42:30 AM UTC+1, teo venier wrote: > > I know that there is already bug 704094, but I have not seen any comment > about the lack of the DOM tab inside the Inspect Element panel, along with > the tabs: rules, computed, animations and so on. > So I decided to post this message to remind them of this feature. >
Good point! The bug was obviously assigned to someone a month ago, so hopefully that will be implemented soon. Though note you can actually already inspect the DOM properties of the selected element in the current versions of the DevTools - though with a suboptimal UI. To do that, right-click the element and choose *Show DOM Properties* from the context menu. > PS: Sorry my english. > Your English is perfectly readable. (Though I'm also not a native English speaker. :-) ) On Thursday, November 24, 2016 at 8:42:32 AM UTC+1, Matthew McRae wrote: > > One thing that seems to be missing is the autocomplete when making CSS > changes. > > When I would begin typing a CSS rule - Firebug would auto complete it > depending on the page I was on (E.G. On Wordpress, it was able to detect > the fill in the page-id) > Now it doesn't complete at all - making it more cumbersome. > Oh yes! That is really, really annoying! I wonder why I forgot to mention that so far. I could have sworn I already filed bugs related to that, though I can't find any. :-/ So, I'll file them now and put this on the list. I remember this was fixed for one or two properties in the past, but it requires to be fixed for each property individually. I have to say I HATE the Firefox dev tools, they are shite compared to > Firebug. Please bring Firebug back, sir. > That won't happen - at least not as long as nobody stands up to revive the Firebug project. On Thursday, November 24, 2016 at 1:50:57 PM UTC+1, Denis Chenu wrote: > > Hi, > > I start vote for some feature in bugzilla. But currently, my big issue is > the speed difference between Firbug VS DevTool in DOM Inspector. > > With Firebug, it take me less than 1/2 second to select an element in DOM > and review classname/id etc .... > With DevTool : it's really more slow, i think it's due (in part) by the > updated windows : show padding/margin/horizont bar/vertical bar/tooltip > with information. > > I think we need all this part only after click on element (or if select > element via the inspector, but not via the HTML window). > > Hope you understand what i mean :) > I guess you mean that it takes longer until the display of the Inspector panel updated, right? Though, because you mention DOM, there is also a DOM panel, which is really slow. Though that slowness is already tracked in bug 1264908 <https://bugzilla.mozilla.org/show_bug.cgi?id=1264908>. Having said that, the display of the DevTools is generally a bit slow. I assume this is due to the asynchronous structure of their UI. And I agree that this needs to be improved, though I wonder if that can be seen as "Firebug gap". Sebastian -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/90c402a0-a9f8-4074-a635-4c4b041d2e7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
