Question
I want to start the Firefox web browser as process to visit a specific website, then wait until it is closed.
A special situation is that the browser may already be open and running, as the user may have visited some website already.
In that case, the browser would probably open a new tab in an existing window and the newly launched process will be terminated immediately. This should not confuse my waiting process: Either, I want a new browser window (if that can somehow be enforced, maybe via command line arguments) and wait until that is closed, or keep the existing browser window and wait until all the tabs resulting from my process are closed.
Environment
I think it doesn't matter, but my programming environment is Java
and you can assume that I know the path of the browser.
Example
The only browser for which I can obtain the expected behavior is Internet Explorer (sigh.). Here, I need to basically create a new batch script in a temp folder with something like
start /WAIT "" "C:Program FilesInternet Exploreriexplore.exe" -noframemerging http://www.test.com/
I then run the batch script instead of directly the browser and delete it once I am finished with waiting.
Intended Process
To make the intended process clearer:
- My program starts.
- My program launches the Firefox browser as separate process and provides an URL to visit as argument to that process.
- The Firefox browser runs asynchronously, as a new process, and visits the provided URL. So far, this is easy.
- After launching the new process (the Firefox browser), my own program should wait for the said process to terminate. This is the hard part, as
- Many modern browsers start multiple processes. I would need to wait for all of them.
- Many modern browsers may somehow "detach" themselves from the process that I launched. Sorry, I don't know a better word, what I mean is: I start a process which then starts another process and terminates immediately while the other process keeps running. If I wait for the browser process originally started by my program, the waiting will be finished while the browser is still open.
- A special case of the above is tabbed browsing as realized in many browsers: If the browser is already open (in a separate process started by the user) when I launch it, my newly started browser process may simple communicate the URL to visit to the existing process and terminate. The user is still on my provided URL while my program thinks she has closed the browser. This issue can maybe be forbidden by specifying a special command line argument, like
noframemerging
for the IE.
- Once the browser has terminated or all tabs related to the URL I provide have been closed, my program will cease to wait and instead continue doing its business.
The use case is that I have a web application which can either run locally or on a server. If it is run locally, it launches a web server, then opens the browser to visit the entry page. Once the browser is closed, that web application should shut down as well. This works reliable for Internet Explorer, for all other cases, the user has to close the browser and then, explicitly, the web application. Thus, if I could wait reliably for Firefox to finish, this would make the user experience much better.
Solution Preferences:
Solutions are prefered in the following order
- Anything which ships with the pure Java JRE. This includes special command line arguments to the browser.
- Things that require me to, e.g., create a batch script (such as in the IE case.)
- Anything that requires 3rd party open source libraries.
- Anything that requires 3rth party closed source libraries.
Any platform independent answer (working both Windows and Linux) is prefered over platform-dependent ones.
Reason: In the ideal case, I would like to know what exactly is done and include it into my own code. As I want to support different browsers (see "PS" below), I would like to avoid having to include one library per browser. Finally, I cannot use commercial or closed source libraries, but if no better answer turns up, of course, I will honor any working solution with an accept. I will accept the first (reasonably nice) working answer of type "1". If answers of lower preference turn up, I will wait a few days before accepting the best one among them.
PS
I will launch a couple of similar questions for other browsers. Since I believe that browsers are quite different in the command line arguments they digest, the way the launch threads and sub-processes, I think this makes sense.
See Question&Answers more detail:
os