I have a Raspberry Pi and I want it to auto launch Chromium in fullscreen when it boots up. I also want to auto launch the Rotisserie URL Rotator as soon as Chromium loads so it will start rotating through my default tabs automatically.
I've looked into the extension's manifest.json and there is the section for "background" but I am not sure what I'm supposed to do in order to get the extension to auto launch.
Related
I would like to have default launching of a browser to be different when launching from different programs.
For instance:
when I open a link from Discord I'd like it to be launched in
Firefox.
When I run npm run dev, I want my development app to
launch in Brave.
As for the second example, the issue I run into is that the browser window gets hi-jacked every time the code is updated. So I'd like the default launch from the npm application to launch a different browser than the one I'm using for research.
I have an electron app in which i am using Auto Hot key.I want to disable ALT+F4 for that i have written following script
!F4::Return
After execution of this script i am still able to close my electron app using Alt+F4 but for other application like for Notepad,folder etc script is working fine.
For reference: https://www.autohotkey.com/docs/AutoHotkey.htm
This disabled Alt+F4 for all windows with "- Notepad" in the title
SetTitleMatchMode 2 ; All #If statements match anywhere in title
#IfWinActive - Notepad
!F4::return
#IfWinActive
Replace - Notepad with the title of your Electron app's window
I think your probably better off setting closable: false in your browser window options so that the electron window won't close and the other windows won't close.
All browser window options
Once a node.js program has run to completion in the context of an --inspect session (i.e. via the Chrome dev tools debugger) is it possible to re-start it without having to re-issue the --inspect command from the command-line?
The issue with re-issuing an --inspect command is that it generates a different chrome url every time and one has to then copy-paste this into Chrome each time. Ideally I want to be able to push F5 to re-start the chrome debug session.
So two issues:
I cannot restart the debug session without killing the current (i.e. no way to just refresh).
I have to copy paste the url into chrome each time I start a new session. (not as bad as issue 1.)
Here's a couple of options for you, though neither will provide you with a simple F5 refresh, both are significantly better than copy/pasting the new URL generated by the --inspect flag.
The most optimal solution is installing this extension for Chrome or Opera: https://chrome.google.com/webstore/detail/nim-node-inspector-manage/gnhhdgbaldcilmgcpfddgdbkhjohddkj
This will manage the node inspector for you. Just click the resulting toolbar icon and select "Auto" from the toggle switch. Your browser will then open the Chrome DevTools in inspection mode whenever your node server generates an inspection URL.
If you want to go the low-tech (and more manual) route, or don't want to install a Chrome extension, just open your Chrome to "chrome://inspect", wait a moment, and you'll get a list under Remote Target that will include your Node server. Just click the "inspect" link there, and the DevTools will open with the current URL. The downside of this method is you'll need to reclick that "inspect" link every time your server restarts. It avoids copy/pasting URLs, but still involves manual labor.
It's also significant to note that if you simply update the url of your inspector with the new ID, it will also work.
When you restart node, you'll get something like this:
Debugger listening on ws://127.0.0.1:9222/72c791b7-178f-47e8-93b1-d1be4d5ffe1e
The bit after the port/ is what you want. Replace that code in your inspector's url and it will connect to the latest session.
We have an Chrome Background Extension that loads on the windows startup.
the plugin create an iframe element and load Java Applet that will be used later
(techniqe to keep the JVM loaded and reduce the applet loading time).
the problem is that the first instance of the chrome.exe is running without any custom flags like --disable-web-security and --allow-outdated-plugins .
so the background task cannot perfrom well.
is there any setting we can use in the registry or chrome plugin API that can be used.
we deploying this Extension in the internal ENV , and the browser dont have any direct internet access.
10x
elad.
found it :-) [HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome] "AdditionalLaunchParameters"="--enable-media-stream --enable-media-source"
I am running tests from phpunit using selenium. Since the tests take a couple of minutes proceed, I would like to switch to another desktop and do some tasks while the tests are running in the background.
However, since every test calls a new browser via selenium remote server, and a new test management window and a application window are started, these new windows do not appear in the desktop which I started the php tests from, but in my current desktop taking the focus away from the window I am working in.
How can I control that the browsers are always opens in the desktop that is in the background (where I start phpunit)? I am using Kubuntu i.e. the KDE Desktop.
Thanks for any suggestions!
This is probably a bit late, but for anyone reading this: When you launch your selenium RC server, you could try exporting to a specific display using the command:
export DISPLAY="somedisplay" && java -jar /path/to/selenium-server.jar
Using this, you could also export it to for instance an X virtual frame buffer (Xvfb), effectively running it in the background.