It was just pointed out lately <https://bugzilla.mozilla.org/show_bug.cgi?id=1335853>, that this issue is related to the *Inspect Element with Firebug* option. Issue 8077 <https://github.com/firebug/firebug/issues/8077> was created to fix this (by removing the option).
Please use the *Inspect Element* option instead! Sebastian On Sunday, January 8, 2017 at 5:02:51 PM UTC+1, Sebastian Zartner wrote: > > On Friday, January 6, 2017 at 12:38:28 AM UTC+1, San wrote: >> >> A few other differences in how the Inspect feature works: >> >> In Firebug (on a Mac, anyway) I was able to put a separate "Inspect" >> button in the Mac's Dock (similar to Windows Taskbar). >> > > Outside of the browser? I didn't see that yet. I just know custom toolbar > buttons. > > >> There doesn't seem to be any separate Inspect button in DevTools. >> > > You're right. That's currently missing. There's bug 1302363 > <https://bugzilla.mozilla.org/show_bug.cgi?id=1302363> to add an Inspect > button. > > Another difference -- not sure I remember this correctly because I haven't >> used Firebug in a while -- but I seem to recall that the effect of clicking >> Firebug's Inspect tool on something in my main web page (not in the HTML >> code) was quite persistent. In other words, I could click something on the >> web page, and then cruise around in the panel/code views and get different >> kinds of information about the selected object. In DevTools, the >> Inspector-selected object seems to deselect itself quickly so I have to >> frequently re-select it, which is annoying. It's not "persistent" enough. >> > > Not sure I understand this. You can get all the info for the selected > element and the selection persists panel switches and page reloads. Can you > provide an example where that's not the case? > > Finally... correct me if I'm wrong, but I don't recall Inspect in Firebug >> being a separate mode. I recall it being just a tool that could work across >> more than one panel mode. However, in DevTools, Inspect seems to be a >> completely separate panel (with HTML and CSS sub-panels). This makes no >> sense to me -- why is Inspect a separate panel? You might want to Inspect a >> page element for HTML, or CSS, or any other panel, and these are panels >> that already exist (often in more powerful form) separately. Why duplicate >> them? Why isn't the DevTools Inspect tool universal? >> > > The Inspector in Firebug worked within the *HTML* and the *DOM* panel and > allowed to be used by Firebug extensions. The Inspector in the DevTools is > bound to the *Inspector* panel (which is the equivalent to Firebug's > *HTML* panel). I don't know if it can be reused by DevTools extensions. > > In sum, like other people here, I found the Firebug Inspector much more >> usable. >> > > Currently, the bugs filed as gaps related to Firebug are here: > > https://bugzilla.mozilla.org/buglist.cgi?bug_id=1328641%2C815464%2C1061823%2C1067318%2C1243045%2C773510%2C987877%2C994559%2C1005825%2C1006508%2C1067323%2C1150498%2C1150499%2C1173504%2C1226637%2C1226640%2C1227054%2C1270025%2C1277828%2C1302363%2C1316528%2C1323700%2C1323746%2C704094&list_id=13382251&bug_id_type=anyexact&resolution=---&query_format=advanced > If you see bugs not listed there, please file them and mark them as > blockers for bug 991806 > <https://bugzilla.mozilla.org/show_bug.cgi?id=991806>. That would help a > lot. > > 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 firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. 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/ec36df98-cbdd-4cc2-8f5c-05bfd8b8e845%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
