Bug#393837: More informations..

Mike Hommey mh at glandium.org
Tue Oct 28 09:05:04 UTC 2008

On Tue, Oct 28, 2008 at 09:44:49AM +0100, Josselin Mouette <joss at debian.org> wrote:
> Le mardi 28 octobre 2008 à 10:17 +0200, Romain Beauxis a écrit :
> > 	Hi all !
> > 
> > The issue can be isolated in this line:
> >   window.openDialog('chrome://pippki/content/deletecert.xul', "",
> >                     'chrome,centerscreen,modal', params);
> > 
> > in certManager.js.
> > 
> > If you remove this line, and comment the next if, then you simply remove the 
> > confirmation box. Could be a workaround perhaps if nothing better can be 
> > find ?
> > 
> > If you remove from the file delecert.js everything related to gParams, then it 
> > works, but does nothing.
> > 
> > I'm strongly suspecting some sort of javascript failure, related to the 
> > gParams variable, but, as usual, it really lacks a good damn javascript 
> > debugging console.
> Yes, the params are correctly passed to the chrome dialog, but they are
> removed by some later call in the stack. The window is probably missing
> permissions to obtain them but I don’t know how it should get them. As
> this happens for all gtkmozembed applications I suspect this is
> something gtkmozembed should do.

It's either a gtkmozembed bug or a embedding bug, where the js context
for the windows doesn't do the right thing. The problem is: we don't know,
upstream doesn't know, and mozilla doesn't (seem to) care.

I'd say the best thing to do for epiphany would be to *not* use the
xul cert manager, but have its own native one, calling the proper
components. But this doesn't look like a solution that can be ready for

So maybe all we can do in the end is probably to use the workaround.
The problem with doing the workaround on xulrunner's end is that it will
also change behaviour in iceweasel, which is not really expected...


More information about the pkg-gnome-maintainers mailing list