I've got Dom Inspector installed on Fennec on my desktop, and sometimes the cmd+shift+i hotkey works and sometimes it doesn't (or maybe I'm forgetting it?).. so I"m wondering if anyone knows if there is a command line flag that I can use to open the dom inspector when Fennec opens?
Using the same argument as works with Firefox works for me:
fennec -inspector <URL>
Related
I want to change where live-server opens, for example, I like using safari as my default browser, but every time I type live-server in the terminal it will open a window on safari. I know I can type live-server --browser='google chrome' but now I don't want to be typing that whole code to open in Chrome. I want to change it so that when I type live-sever it will open on chrome instead, I know I have to change that in the .json file but I'm not sure where it's located, or how to access it in the terminal. Thank you in advance.
I have found the solution after searching on the internet and it' straightforward. You just have to change your selected browser from you pc settings. It worked for me I hope it will work for you too!
I know there is the openPopup API to open a browserAction popup.
However, when it is open and a user e.g. selected something, can I somehow close it?
The same applies for a pageAction.
Cross-posted at Mozilla Discourse.
Actually, as for any other website a simple window.close(); works totally fine!
This was too simple.
Only tested in Firefox though.
Edit: As #juraj.masiar made me aware this won't work for Firefox for Android though:
You will have to use browser.tabs.getCurrent().then(tab => browser.tabs.remove(tab.id)). Plus you need to detect that you are running Android using browser.runtime.getPlatformInfo() function.
Above is the image from netbeans terminal window. I want to use it to check the version of nodeJS.
Problem is when i click on the computer icon(single) to use the terminal so I can type it just refresh.
It becomes like above then after 1 sec returns to original state. I cant type anything on it
You must cgwin in order to resolve your issue here is link cgwin
To debug extensions, Chrome used to have a "Inspect popup" menu option available when right clicking the extension icon (top right in the browser). I believe this options was recently removed (possibly with the latest Chrome version 20, which I am using) .
The debug console can still be activated by right clicking any element in the extension popup and selecting "Inspect element". The problem I am experiencing however is that whenever I now have the debug console open, typing into form elements in the popup does not work. Even though the form element seems to have the focus (it has a blinking cursor active), all input typed goes straight to the debug console.
Update: It seems focus is not specifically to the debug console, but to whichever window is below. It's like the extension window is a "stay on top" window, without capturing any input.
Update: 2012-07-24: Updated to 22.0.1215.0 (Official Build 147830) dev and the bug is still there. But yay, Youtube full screen now suddenly works on my dual screen system!
Update 2012-05-09: Upgraded from 20.0.1123 to 20.0.1130.1 dev on Linux x64 (Ubuntu 12.04). Problem still there, and makes debugging extensions a lot harder than needs be. Also confirmed behaviour on older Chrome release (20.0.1105.0). Oh well, maybe it's just me...
Update 2012-05-09 2: Assuming this is a bug, consider adding a background page to your popup and log to that page's console instead until bug gets fixed. At least that makes my life easier for now.
Update: 2012-10-19: As omri writes (and points to), the Inspect Popup option is on it's way to be put back into Chrome, which will hopefully solve this problem (finally).
Could anybody confirm/deny this behavior, and/or suggest possible workarounds?
Open the popup
Right click the popup window and inspect.
Its going to be re-added to chrome
http://code.google.com/p/chromium/issues/detail?id=143349
Update: Un-accepting answer as another user confirmed this behaviour for OSX, so at least it will appear as unsolved on the radar, although there's probably a bug tracker somewhere where this needs to be posted.
This bug is still present on google-chrome-beta (Version 20.0.1132.34 beta). I'm guessing that this has to do with window and popup handling on X11 generally, and is obviously not a high priority bug since it's remained this way for quite a few releases. Closing question.
I am seeing the missing "Inspect Popup" option on right click but, I can edit/enter text in the form fields.
I am wondering if you are having an unrelated problem? If you are using or updating to the new 2.0 Extension Manifest you can encounter issues where inline javascript in the popup fails to fire any longer because of the addition of the content_security_policy defaults. Basically this prevents script injection but also seems to kill all JS in your popup. There are ways around this by changing the way events are handeled in your popup or by changing the default policy. Here's a link to the doc on this: http://code.google.com/chrome/extensions/contentSecurityPolicy.html
This is just a guess because I don't know what's going on in your code but I saw similar things while upgrading my extension recently.
Just upgraded to 22.0.1221.1 (Official Build 149058) dev and the problem seems to have been solved, albeit with a workaround. The old way of right clicking in the popup window and selecting "Inspect Element" to start up the console still grabs all input as originally reported.
However, it seems by right clicking the popup icon, the old "Inspect Popup" seems to be back, and when this is used it does not seem to grab input from the open popup window itself.
Google Chrome is set as the default browser. However, it opens links in Firefox, which is undesired.
How can I make Org-mode to open links in Google Chrome?
Emacs 23.2 doesn't directly support Google Chrome, but it does support a "generic" browser, and something like this should work:
(setq browse-url-browser-function 'browse-url-generic
browse-url-generic-program "chromium-browser")
You don't mention your OS, but if it's Windows or Mac, you can try:
(setq browse-url-browser-function 'browse-url-default-windows-browser)
(setq browse-url-browser-function 'browse-url-default-macosx-browser)
And, if that doesn't work, there are other folks who have implemented 'browse-url-chrome. Google turned up the following link:
http://code.ohloh.net/search?s=browse-url-chrome&browser=Default
As Trey suggests, you can set it to a generic browser, but instead of "chromium-browser" use "google-chrome", like this:
(setq browse-url-browser-function 'browse-url-generic
browse-url-generic-program "google-chrome")
That worked for me with Emacs 23.2 and Chrome 12.
I have a similar problem (although the other way around: I wanted Emacs to open Firefox, but it opened Chromium).
I'm using Ubuntu 12.04 (Precise Pangolin), but already had the problem with Ubuntu 11.10 (Oneiric Ocelot). The solution below applies to Linux, maybe macOS (?), and probably not Windows.
Setting browse-url-generic-program as suggested in other answers didn't work for me. Note also that my default browser is generally Firefox: that's what most other applications are using to open a URL, including xdg-open. So I was surprised that Emacs would do otherwise.
I finally figured out that Emacs is using the sensible-browser (1) script. Looking at that script, I noticed that:
it first looks at the BROWSER environment variable;
else, it tries several other generic scripts, starting with gnome-www-browser
It so happens that, on my machine, BROWSER is not set, but gnome-www-browser is a script apparently put there by Chromium, and (naturally) running Chromium.
So, long story short: putting the following line
export BROWSER=firefox # Or any browser of your choice
in your .profile may help if Emacs is not using the correct browser.
Setting the browser function is very easy using the GUI:
In the menu, click Options > Customize Emacs > Top-level customization Group
Click on the link External (Interfacing to external utilities.)
Click on the link Browse Url (Use a web browser to look at a URL.)
Click on the small triangle to the left of Browse Url Browser Function, this reveals a Value Menu button and some help text
Click the Value Menu button
Choose your preference from the displayed menu
Move to the top of the buffer, click the button Apply and Save to save the change to your ~/.emacs file
Done :-)
I also had this problem when exporting org files to HTML. It would use Firefox instead of a Chromium browser. I fixed it by customizing org-file-apps (which for some reason had been set to open XHTML and HTML files with Firefox).
I now have an entry for extension \.x?html?\' with command set to the Lisp form: (browse-url file)
I was on macOS and the browse-url-default-macos-browser did not work for me.
My solution was:
(setq browse-url-browser-function 'browse-url-chrome)
(setq browse-url-chrome-program "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"))
For ChrUbuntu, the google-chrome incantation as given by Alan Turing works with Emacs 23.3.1, the default as of today. I suspect the chrubuntu configuration even when tickled to use chromium uses the wrong binary name.
In emacs 28 (Fedora Linux) I just needed this
(setq browse-url-browser-function 'browse-url-chrome)