When I restart firefox using the developer console, i press shift+F2 and then I write
restart
in the command line that comes up at the bottom and press ENTER.
This is of course a very useful feature, every window dissapears and comes back, but each restarted window will also have the developer console opened as if I was pressing shift+F2 on everyone of them.
Why?
The Developer Toolbar is a global thing, just like any other toolbar (e.g. Nav Bar or Bookmarks Bar). Firefox will remember the visiblity state and will restore it when opening new windows, either the usual way, or after a restart.
Just close the toolbar in one window, and it will be closed in every other window as well.
Related
As soon as I open Firefox console it starts printing every mouse move or click I do into console. I never enabled such feature, maybe I might have pressed some shortcut since this is a fresh install.
This starts on any website I visit. Even if I try with Private window same issue happens, even with all add-ons turned off.
F12 > Debugger > Untick LOG
According to Google this can be accomplished by visiting "chrome-devtools://devtools/devtools.html" in Chrome but now visiting that page in the stable version of Chrome (or Canary), just shows a 99% stripped version of the inspector.
To reiterate my "title" this is in reference to "inspecting" the inspector. Not just inspecting a normal webpage.
And while I don't think it's necessary to know to resolve the issue, I"m inspecting the inspector so I can style it as discussed by Paul Irish and here: https://darcyclarke.me/articles/development/skin-your-chrome-inspector/
Follow these easy steps!
Press Command+Option+i (Ctrl+Shift+i on Windows) to open DevTools.
Make sure that the developer tools are undocked into a new window. You may have to undock from the menu:
Press Command+Option+i again on this new window.
That will open the DevTools on the DevTools.
You can redock the page's DevTools if you want.
If it's not already, select Elements — it's the first icon at the top of the inspector.
A little beyond the scope of your question, but still valid in understanding why you're experiencing your problem can be found by understanding how Chrome Developer Tools: Remote Debugging works.
Open chrome://inspect
Open the inspector on that page (cmd + alt + i)
Scroll to the bottom of the page, under the Other section click the inspect link
The URL in the Other section should look something like this:
chrome-devtools://devtools/devtools.html?docked=true&dockSide=bottom&toolbarColor=rgba(230,230,230,1…
EDIT: they've fancied up the chrome:inspect page so you have to click the Other header on the left to get this to work now.
I just got this to work. The key is that you have to start up chrome in 'Remote Debugging' mode.
on OSX, open an terminal window and execute the following:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
On windows, Its
chrome.exe --remote-debugging-port=9222
(better windows instructions can be found here: https://developers.google.com/chrome-developer-tools/docs/remote-debugging#remote)
This will start up an instance of chrome, that will send debugging messages to a local webserver on port 9222.
If you access that web service, it will give you the ability to use the inspector to inspect any chrome window that is running. Since we want to inspect the inspector, we need to start an inspector window first (As above Use the shortcut keys; for Mac it's Command+option+i.)
Now, go ahead and navigate to
http://localhost:9222
It will present you with a list of windows to display in the debugger. Select the window that starts with "Developer Tools" and you'll be able to inspect the css for the inspector.
Its hard to see in the image below, but on the left I have my chrome window pointing at the remote debugger, highlighting one of the toolbar labels. On the right you see it lit up with the tooltip just as if we were debugging a web page.
A few weeks ago somebody pointed this out in stackoverflow's "javscript" chatroom. First, and very importantly, make sure the inspector is undocked from your browser window. Then it's just a matter of opening a inspector window and then inspecting that window. In windows it's CtrlShiftI (Edit: I said, CtrlShiftI but that brings up the console inspecting the console... you should be able to navigate back and forth.) for the keyboard shortcut. (Other keyboard combos for other options and OSes here and here.) Just do that twice and you're good.
Edit: ok, you're probably confused as to undock the window. This is what you'd click if it's docked..
Edit II: I'm not quite sure why you can't inspect. JDavis's answer is consistent with the Google Docs for Apple computers. If you're using Linux it appears to be the same as Windows. You supposed to hit the inspector key combination while the focus is over the inspector window.
How do I dock the Browser Console window in Firefox?
The Browser Console currently opens in a separate window. I'd prefer for it to be docked to the bottom of the main window.
There's a similar question for Firebug.
There is no stock way to dock the Browser Console to a specific window. The Browser Console is for the entirety of the Firefox browser. What it shows is not limited to a single window. Thus, from a user interface point of view, it does not make sense to have it be docked to a single window.
It might be possible to create an add-on which opens an equivalent page that is in a bottom bar.
The best I could do was manually to dock Browser Console window and Firefox window in my desktop environment (Gnome on Fedora) so that they are both visible when debugging.
I don't know of any way with the built-in console. However, the 'Web Developer Extension' add-on console has toggles to dock to a window, but also several additional useful layouts.
Is it possible to detach the console/log window in Xcode 4?
Even better, how?
Go to Xcode preferences, and open the Behavior tab.
Tell Xcode to open a tab called "Debugger" when "Run Pauses" or "Run Starts". Then run it, and break that Debugging tab out into another window (drag it off the tab bar into its own window by just letting it drop outside the current window). Now reform it to your hearts content; it will stay that way. Also don't forget the little controls at the top right of the console window that slide the local variable display out of the way so you can have a full-width console on demand. I am not sure about keyboard shortcuts for that yet.
I usually keep the Debugging tab and one other tab in a separate window, for debugging tasks, and all my other editing tabs in a different window (and the debugging window on a separate monitor with the simulator). With the settings above it also means that, while editing a debugger reaching a breakpoint, it will not interrupt my editing by suddenly bringing forth the console.
Sure, create a new tab, drag it off the original window, and expand the debugger area to be the whole tab. Now, whether Xcode will remember that tab and its placement is another matter. File a bug with Apple to let them know your displeasure.
Taking jshier's advice a step further, you can do File -> New Window, and expand the debug window to take up the entire window. But you have to manually expand it every time you open it. Ugh.
I am using Visual Studio 2005 with Team Foundation Server.
When I right click a file under the source control and choose "compare" VS appears to freeze until I hit escape. My guess is that the window that is supposed to be popping up is somewhere I can't get to. I tried minimizing all the windows that I can and it is nowhere to be found.
Try the keyboard shortcut to get to the window's main menu () then hit 'M' for move and hit an arrow key to attach the window to the mouse - then at the next move of the mouse it should jump to it.
Experiment with a window you can see first.
i had the same problem when trying to check in to TFS - no dialog and ESC escape key undid the freeze.
I had recently, before the problem, changed my Laptop + Monitor configuration as follows:
from Primary screen being the laptop and secondary screen being the monitor
to primary screen being the monitor and secondary being laptop.
I got rid of my secondary screen and tried again. SUre enough the invisible dialog was no longer invisible.
I had to disable my Second Screen as well. Now the check-in screen where you can add a comment IS visible.