Hello,
Platforms: Linux, OS X, Windows
Firefox: 2 and 3
We have a test script which runx Firefox to visit a web site and after
a few seconds it stops it.
Right now we use killall firefox but this causes it to behave as if
it crashed the next time it comes up.
I found in
Isnt it ps ( in a terminal) to get the PID for Firefox, then kill PID?
Bill
Still a newbie
[EMAIL PROTECTED] wrote:
Send slug mailing list submissions to
slug@slug.org.au
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.slug.org.au/listinfo/slug
or, via
bill wrote:
Isnt it ps ( in a terminal) to get the PID for Firefox, then kill PID?
Bill
Still a newbie
killall -SIGNAL processname
kill -SIGNAL pid
work the same.
I have tried sending various signals to firefox
-TERM firefox exits unexpectedly; restarts with an error warning
-HUP
It would be nice if there were a command-line arg that disables
the annoying warning on startup after a crash.
This[1] seems to be what you want:
1. Go to about:config
2. Set browser.sessionstore.resume_from_crash to false
Although killing the poor fox seems like an harsh way to do it, so
Henare == Henare Degan [EMAIL PROTECTED] writes:
It would be nice if there were a command-line arg that disables the
annoying warning on startup after a crash.
Henare This[1] seems to be what you want:
Henare 1. Go to about:config 2. Set
Henare browser.sessionstore.resume_from_crash to false
$quoted_author = Amos Shapira ;
We have a test script which runx Firefox to visit a web site and after
a few seconds it stops it.
My first thought was Why use a GUI app to test something automated?...
Surely there are more elegant ways to achieve what you need...
cheers
Marty
--
SLUG -
2008/8/1 Martin Barry [EMAIL PROTECTED]:
$quoted_author = Amos Shapira ;
We have a test script which runx Firefox to visit a web site and after
a few seconds it stops it.
My first thought was Why use a GUI app to test something automated?...
Because it has to run all sorts of JavaScript,
2008/8/1 Henare Degan [EMAIL PROTECTED]:
It would be nice if there were a command-line arg that disables
the annoying warning on startup after a crash.
This[1] seems to be what you want:
1. Go to about:config
2. Set browser.sessionstore.resume_from_crash to false
Thanks. I imagined there
$quoted_author = Amos Shapira ;
Because it has to run all sorts of JavaScript, Flash, pull images etc.
and generally do what a browser does as part of the test.
We need a real browser (multiple browsers types and versions from
multiple platforms, actually) to access that web page, wget and
2008/8/1 Peter Chubb [EMAIL PROTECTED]:
Once upon a time you could do
mozilla -remote xfeDoCommand(exit)
but this seems disabled now.
Thanks. It gives me a direction to keep digging.
Cheers,
--Amos
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and
[EMAIL PROTECTED] wrote on 01/08/2008 02:32:53 PM:
2008/8/1 Peter Chubb [EMAIL PROTECTED]:
Once upon a time you could do
mozilla -remote xfeDoCommand(exit)
but this seems disabled now.
Thanks. It gives me a direction to keep digging.
Hi Amos,
wmctrl -c 'window name'
You need to make
On Wed, Jul 30, 2008 at 03:44:27PM +1000, Daryl Thompson wrote:
[ .. ]
gstreamer-plugins-bad-0.10.7-2.fc9.i386 from installed has depsolving
problems [ .. ]
gstreamer-plugins-bad is not from the standard repos AFAIK.
You're always chancing when you include non standard yum repos.
That said,
2008/8/1 Martin Barry [EMAIL PROTECTED]:
Have you explored tools like Selenium?
I heard a lot about it and even downloaded it but never had time to
investigate it.
Hopefully next week we'll have more resources to look into it.
In the mean time, we have this crude script which *almost* does
13 matches
Mail list logo
