Last builds of firefox/mac don't have DOM Inspector menu item in the tools menu. (The dom inpector itself still exists in the app bundle)

I have this problem as well, using Firefox 0.9.1 for Mac: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040628 Firefox/0.9.1 I have found that if I uninstall and then reinstall Firefox, the DOM Inspector does show up in the menu the first time that I run it. On subsequent runs, it is missing (my menu looks exactly like the reporter's screenshot). I'm quite confident that I didn't have this problem with 0.9.

confirming myself for now :-) as i see it in more than one machine...

Interesting: I've just done my own build (based on source updated just a couple of hours ago), and the DOM Inspector menu item seems to be there reliably again. I have no idea whether this was actually fixed or if the difference has something to do with my build parameters (I think I followed the default Firefox build instructions; I was trying out a minor patch for bug 252176 / bug 227344, but it shouldn't be relevant to this at all).

I saw this problem in the AVIARY build, i haven't checked on trunk. Did you build an AVIARY build or a trunk one?

To be honest, I have no idea. I followed the build instructions at http://www.mozilla.org/projects/firefox/build.html pretty much to the letter. (I set MOZILLA_OFFICIAL=1 in my environment, and I didn't add any options to my .mozconfig file.) I've spent so little time with the Mozilla source thus far that I have no idea whether that defaults to an AVIARY or trunk build. Based on my very sketchy impression of what AVIARY is, I would be rather surprised if that wasn't the default at this point (and if it's not, I'd love to know how to select it, and why it _isn't_ the default).

default is trunk

I've just compiled again after changing to the AVIARY branch (it took rather a lot of hunting before I figured out how to specify that!) and updating via CVS, and I still have the DOM Inspector menu entry available every time I run the resulting Firefox.app. Do the new nightly builds work for you now as well?

(In reply to comment #8) Do the new nightly builds work for you now as well? I don't have access to my mac right now, can you download this: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.9/Firefox-mac.dmg.gz and check with a new *and* an exist profile?

Weird. The official nightly build that you linked to still seems to have this bug, but my self-compiled version works perfectly fine. I tried the nightly with both a new profile and an old one, as you asked; neither of those ever showed me a DOM Inspector option at all.

So you probably compiled a trunk build

I guess it's possible that I inadvertently compiled a trunk build again (or some strange hybrid) since I updated the source on top of my earlier (trunk) directory to save bandwidth, but CVS certainly did a lot of updating between the two builds. And the current User-agent string from the about: page on my compiled browser is: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040727 Firefox/0.9.1+ If this were a trunk build, I'd expect to see "rv:1.8a3" or something to that effect, right? Just to be clear, the same browser window that gave me the above User-agent string has the DOM Inspector menu item visible and functional. I'm not eager to pull a whole new copy of the source tree to test this (particularly since I mostly trust CVS), so I hope that someone else who has a copy of the AVIARY branch that they trust completely can check this out. Again, I compiled this version by following the instructions on the web page I linked to earlier, modified only by adding a "-r AVIARY_..._BRANCH" when pulling the initial configuration files.

Oh, it is a duplicate...weird that we so this only with last nighlies. *** This bug has been marked as a duplicate of 244479 ***

v