How do you get rid of security alerts?

I am working on two browsers, both utilizing the Mozilla core, although differently. However, it gets annoying for me to constantly click the security alerts everytime I enter the browser. How do you save these settings? Or better yet, how do you disable them? -- Timothy J. Warren, of timshomepage.

Gtkmozembed in Windows

Is it possible (AND EASY) to embed mozilla in Gtk applications running in windows, just as we would do with Gtk applications running in Linux? Thanks ___ mozilla-embedding mailing list mozilla-embedding@mozilla.org http://mail.mozilla.org/listinfo/mozill

Re: Running event handlers

Ben Hutchings wrote: I assume you mean PL_ProcessPendingEvents? Yes. That is not being called. Does it usually get called when you spin the GTK event loop? I wonder whether there's something wrong with the way I'm dispatching the event, that can cause further events to be blocked? DOM e

Re: Running event handlers

Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Ben Hutchings wrote: >> As it is, the loop never exits. My actual code for >> on_net_state_change includes some output statments which report its >> arguments. They show that it is never called with the REQUEST and >> STOP flags. If I remove the loop, i

Re: Running event handlers

I wrote: > As it is, the loop never exits. My actual code for > on_net_state_change includes some output statments which report its > arguments. They show that it is never called with the REQUEST and > STOP flags. To be clear, I mean it is never called with the REQUEST and STOP flags once this l

Re: Running event handlers

Ben Hutchings wrote: As it is, the loop never exits. My actual code for on_net_state_change includes some output statments which report its arguments. They show that it is never called with the REQUEST and STOP flags. If I remove the loop, it is called with these flags during the next call to

Re: Running event handlers

Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Ben Hutchings wrote: >> Surely I'd need to find the document first, and that's not possible >> until it has at least started loading, which I would detect in the >> same way. > > Fair enough. You can actually set the load handler on the window, but given

Re: Running event handlers

Ben Hutchings wrote: Surely I'd need to find the document first, and that's not possible until it has at least started loading, which I would detect in the same way. Fair enough. You can actually set the load handler on the window, but given that you're doing things after onload that doesn't

Re: Running event handlers

Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Ben Hutchings wrote: >> I'm using GtkMozEmbed and handling net_state_all signals (I think >> those correspond to nsIWebProgressListener::OnStateChange) in order to >> tell when pages have finished loading. > > This is on 1.7 branch, right? Right. > Is th

Re: Running event handlers

Ben Hutchings wrote: I'm using GtkMozEmbed and handling net_state_all signals (I think those correspond to nsIWebProgressListener::OnStateChange) in order to tell when pages have finished loading. This is on 1.7 branch, right? Is there a reason not to just use the page's onload event here? O

Re: Running event handlers

Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Ben Hutchings wrote: >> Then I guess the problem I'm having is that changes to images (which >> are what I'm hoping to trigger) are asynchronous... > > Yes, changes to images are typically asynchronous. In fact, depending on > what > the change is, they

Re: Running event handlers

Ben Hutchings wrote: Then I guess the problem I'm having is that changes to images (which are what I'm hoping to trigger) are asynchronous... Yes, changes to images are typically asynchronous. In fact, depending on what the change is, they might have to hit the network, right? -Boris __

Re: Running event handlers

Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Ben Hutchings wrote: >> I'm faking up mouse events and dispatching them through the DOM. So >> far as I can tell, calling dispatchEvent on a node causes the event >> handlers to run asynchronously > > dispatchEvent is synchronous. Then I guess the proble

Re: Running event handlers

Ben Hutchings wrote: I'm faking up mouse events and dispatching them through the DOM. So far as I can tell, calling dispatchEvent on a node causes the event handlers to run asynchronously dispatchEvent is synchronous. -Boris ___ mozilla-embedding ma

Running event handlers

I'm faking up mouse events and dispatching them through the DOM. So far as I can tell, calling dispatchEvent on a node causes the event handlers to run asynchronously (presumably the event is queued for running by the event loop?). How can I wait for an event to be handled, or run the event loop