disable or change shortcut of fullscreen mode in Firefox 3.6 due to Firebug shortcut conflict - firefox

I am using Firebug with Firefox 3.6 on OSX 10.5.8. Since FF 3.6 there is a shortcut to activate fullscreen mode which is "shift" + "command" + "F". But it is the exact same shortcut of Firebug to launch "Display Element Information".
Since i never and don't really need fullscreen mode and use extensively the "Display Element Information" feature of firebug; i am trying to either change the firebug shortcut or disable the FF shortcut.
I tried finding something when accessing about:config but could not find anything relevant.
Does anybody has a solution or hack?
cheers

Change FireFox Shortcuts:
There is an extension called KeyConfig that allows you to change the keyboard shortcuts in FireFox. You can find it at the following URL:
http://forums.mozillazine.org/viewtopic.php?f=48&t=72994
Change FireBug Shortcuts*:
Open the FireBug Panel
Click the FireBug icon on the top left
Select "Customize Shortcuts"
Change the shortcuts you want then restart FireFox
*Note:
I am using FireBug 1.5
I am not sure if the option you want is in the list of shortcuts you need to change.
Hope this helps.

I think the shortcut you are referring to is actually part of the Web Developer plugin, not Firebug. Firebug has a simliar "Inspect Element" function that uses Ctrl-I.
If you don't want to install yet another plugin, just to change one shortcut, then you will have to change the Web Developer shortcut to something else.
I've tried overriding this behaviour using the OSX System Preferences, creating an Application-only shortcut to the menu item: Tools->Web Developer->CSS->View Style Information, but no dice. This plug-in, while one of the most useful that I've found, has always seemed kind of shoddy. It's rarely updated, and bugs seem to live on forever. It breaks every time FF is updated. etc etc. But I still love it.

Not sure which extension is causing this for you. Just checked Web Developer Toolbar and don't see Cmd-Shift-F anywhere.
One newer feature in Firebug is the Customize Keyboard Shortcuts preferences panel on the Firebug menu. Open Firebug, click on the Firebug bug icon menu in the top left of the panel and select Customize Keyboard Shortcuts from the menu that shows up. You'll likely need a restart for these changes to take effect.

Well, now i feel very stupid !!!!
Indeed it is a shortcut from the Web Dev Toolbar and not firebug. I used these 2 so much during a day of work that i forgot they are 2 separate add-ons.
I was able to change the shortcut via the "Options" menu of the Web Dev Toolbar.
And just in case someone changes a shortcut, remember to restart FF for the changes to take effect.
mea culpa.
But thank you every one for helping.
Case closed !

Related

Inspecting a browser's Developer Tools [duplicate]

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.

Firebug shortcut {Ctrl + Shift + C} toggles Firefox Developer Tools instead of Firebug Inspect Element

Since Firefox updated itself to version 28 (running on Windows 7), I can not get the Firebug shortcut for element inspection to work (Ctrl+Shift+C). When I press this key combination, the default Developer Tools window pops up. In earlier versions of Firefox this problem could be tackled by simply unchecking/disabling the Inspector tool in the settings of Firefox' Development Tools. However, this checkbox is no longer there:
I tried the following:
Reinstalled Firefox and Firebug.
In about:config, I searched for devtools.*.enabled, and set all values to false.
I downloaded an addon called Customizable Shortcuts, but changing any of the shortcuts did not solve my problem, the new shortcuts do not get recognized.
In the default Firebug Shortcut Bindings window, changing any of the shortcuts does not affect anything, similarly, the new shortcuts do not get recognized.
Even when I bind the Firebug inspector to a shortcut that isn't in use (i.e., Ctrl+Shift+Alt+6) it still does not get recognized:
It looks like Firebug is prevented from assigning any key combination, or maybe there something else going on.
Any help would be appreciated!
I fixed that in issue 6991, which is included in Firebug 2.0 alpha 1. Let me know if it works for you.

What is the use of F12 key in Mozilla Firefox?

I think it is used to check the coding but when I tried it didn't respond. I mean it doesn't give any response and showing the data of current website.
F12 opens the built in Firefox Developer Tools in recent versions of Firefox. Press F12 again to close it. There is an extension to turn off the shortcut: https://addons.mozilla.org/en-US/firefox/addon/disable-f12-shortcut/
The f12 is a shortcut to Open up firebug in firefox. To open up firebug you must firstly have it installed
F12 is a standard Firefox shortcut that toggles the 'Firefox Developer Tools' on and off.
When you hit F12, Firefox's bottom half opens to show/reveal it's 'Developer Tools,' a Web Console (toolbox?), which
Logs information associated with a web page: network requests, JavaScript, CSS, security errors and warnings as well as error, warning and informational messages logged by JavaScript code running in the page.
Enables you to interact with a web page by executing JavaScript expressions in the context of the page.
It also has an inspector, a debugger, style editor, a profiler and more.
Again, F12 toggles it on and off.
Go to ≡ > Web Developer and you can see the menu of all it does and their shortcuts.
(Firebug was a free open-source web extension for Firefox that facilitated the live debugging, editing, and monitoring of any website's CSS, HTML, DOM, XHR, and JavaScript.
It was deprecated (replaced by something better) in favor of the integrated developer tools (F12) added to Firefox itself. As Firefox 57 no longer supports XUL add-ons, Firebug is no longer compatible.)
F12 is not bound to anything in Firefox - see Keyboard shortcuts. You are probably thinking of the Firebug addon which opens with that key.
The built-in Page Inspector in Firefox (v10 onwards) is accessed with Ctrl+Shift+I and then Alt+M.
In newer versions of Firefox (I have 91.12.0esr), there is an
"experimental" setting in the about:config configuration page that can disable the F12 hotkey (https://bugzilla.mozilla.org/show_bug.cgi?id=1630228)
Setting the devtools.experiment.f12.shortcut_disabled key to true causes the F12 key to bring up a temporary text box that says "To use the F12 shortcut, first open DevTools via the Web Developer menu." but thankfully no longer opens the DevTools bar.
This should be the default behavior, IMHO, since only a small fraction of users will know or care about viewing the HTML source of the page.

Designer Popup Editor Issue

In a custom toolset I have installed for Visual Studio, there is a popup window that should appear to me so that I can manipulate one of the lists (an in-built editor). The component is Telerik, but I don't think that has anything to do with it (maybe).
The popup window is no longer popping up to me. I wonder if it got minimized or it's a z-index thing, where the window is behind VS? But this locks up VS, and I can't do anything within it until I cancel the window. But I can't cancel the window because I can't see it... and so that is really slowing me down and is really frustrating.
Is there a way to get around this? A key press to bring this to the front or give it the focus?
Thanks.
You should be able to cancel it with ESC. You can also test if you can find the window with CTRL-TAB. If this not help then an uninstall, boot and reinstall seems the only possible solution.
This might be a z-index issue indeed. Try using FireBug or IE dev toolbar to get a hold on the popup and its container and check their styles and z-indices.
Dick

How to dock Firebug in browser window?

How to dock Firebug in browser window after I opened in a new window? With Firefox 3.0.8 and Firebug 1.3 on Mac OS X 10.5 I can't get it docked in the browser window back. :(
How to fix the problem
Background: firefox 10.0.10
Steps:
Close Firebug if you have it open -> Go to Firefox menu -> select the "Web developer" option -> select "Firebug" from all the options listed -> Select "Firebug UI location" from all the options -> Choose Top, Button, Left or Right depending on your preference.
This should fix your problem. The "Firebug UI location" in the detached Firebug window doesn't work.
Normally you just close the window. When you open Firebug again, it will be docked.
While I was trying to figure this out, I clicked on the bug in the top left corner, while Firebug was open and docked, and selected "Always Open In New Window." Then I had the same problem.
To disable that option while Firebug is open as a Window, select View (in the OS X menu at the top of the screen while the Firebug window is in the foreground) > Options > Always Open In New Window.
Click on the Firebug icon , Choose Firebug UI Location and then choose bottom , it worked for me
I had the same problem. Resolved by following this:
Right click firebug icon in status bar. Select "On for all web pages"
I Couldn’t dock the firebug window back to the Browser-window. Neither via buttons, nor via menu.
Reseting the firebug-settings solved the problem for me. Luckily, I didn’t changed them ever.
Just close the firebug window and click the firebug icon again. It will once again be "docked".
None of these solutions worked for me. Somehow, one of my firebug settings was being stored in my Firefox profile, and I couldn't figure out how to revert it. So, I took the nuclear option and deleted and then recreated my Firebug profile, following these instructions from Mozilla: http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile
WARNING: This should only be a last resort, as it will remove all of your previous saved settings, add-ons etc. This was not a big deal for me, because I use Chrome as my default browser and only user Firefox for debugging websites using Firebug. But for others, I suspect this might be throwing the baby out with the bathwater, so just wanted to make it clear that there are tradeoffs.
You can click on the small superimposed double rectangle icon on the far right of the firebug window, and dock and undock the firebug widget.
You can click on the small superimposed double rectangle icon on the far right of the firebug window, and dock and undock the firebug widget.
It worked for me in Windows

Resources