When developing web extensions, I test them with (for example) web-ext run --bc -u https://stackoverflow.com/. With Firefox 56.0 (and web-ext 2.2.2), this:
opens a window "Browser Console",
opens another window and starts to load https://stackoverflow.com/ there, and
opens another tab in that window to display the Firefox Privacy Notice.
The last part is not only annoying in itself, but also distracting as (AFAICT) it fills the browser console with warnings related to that page's scripts.
How can I prevent Firefox from opening the Firefox Privacy Notice when called from web-ext, perhaps by setting some preference with --pref?
According to https://github.com/mozilla/web-ext/issues/1114 you can use this:
web-ext run --pref='datareporting.policy.firstRunURL='
Related
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.
My application sometimes opens URLs in a browser. I do this with Process.Start("http://www.example.com").
My default browser is Firefox. I notice that if the above code runs when no Firefox window is active, each URL (I open several URLs in one go) is opened in its own window.
However, if a Firefox window is already open, the URLs all get opened as new tabs.
How can I make it always open as tabs? Always as windows? Open a single new window and make everything a tab in that?
Because command-line arguments differ between browsers, to do this successfully you would need to launch Firefox explicitly and pass in the appropriate parameters. You would have to create a similar solution for each additional browser you wanted to drive.
If this is something you're doing just for yourself or in an environment where you have some control over what's installed on user machines, then it may be solvable. But if it's a general purpose program meant to work on any Windows PC, then it probably isn't practical.
For firefox, the command line arguments are:
-new-tab URL
Opens URL in a new tab.
-new-window URL
Opens URL in a new window.
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.
So every time I run a debug from my development IDE and Firefox is called to display my app, I get my app displayed in a new Firefox tab. That means one new tab every time I start a debug session and before long I've got 10-20 Firefox tabs open.
Can I have it so it reuses the existing tab open?
I could only find Firefox command line options to open new windows etc, not to use the current window/tab.
Just in case the above link disappears, it details going to the about:config screen in Firefox (just enter about:config in address bar) and changing the value of 'browser.link.open_newwindow' from 3 to 1.
I have a Windows application that works with Firefox. If Firefox is already open, I'd like to have it open a given URL in the current tab+window as is currently showing. Our application tends to open a lot of URLs and reusing the same browser window makes the most sense. I already have a COM application that works with Internet Explorer, but haven't been able to find something similar for an external application to work with Firefox.
The only way I know of to do this in Firefox is to set the browser.link.open_newwindow preference to 1. Unfortunately this also stops all in-page links from opening a new tab or window.
If you use SeaMonkey as your default browser then you can use the Preferences window under Tabbed Browsing or Link Behaviour to make links from external applications open in the current tab.