On Sun, Apr 16, 2006 at 09:39:49AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 15, 2006 at 11:19:31PM -0700, Russ Allbery <[EMAIL PROTECTED]>
> wrote:
> > Justin Pryzby <[EMAIL PROTECTED]> writes:
> > > On Sat, Apr 15, 2006 at 10:39:11PM -0700, Russ Allbery wrote:
> >
> > >> object[classid$=":D27CDB6E-AE6D-11cf-96B8-444553540000"],
> > >> object[codebase*="swflash.cab"],
> > >> object[codebase*="sw.cab"],
> > >> object[type="application/x-shockwave-flash"],
> > >> embed[type="application/x-shockwave-flash"],
> > >> object[type="application/x-director"],
> > >> embed[type="application/x-director"]
> > >> { -moz-binding: url("chrome://flashblock/content/flash.xml#obj"); }
> >
> (...)
> > I expect it's probably an upstream bug, yes.
> >
> > I saw a few other segfault bugs in the BTS; I wonder how many of them are
> > due to lingering old XPIs from previous versions that were supposedly
> > disabled but weren't properly.
>
> Your problem is that the extensions WAS properly disabled. But your
> userContent.css file still contained a reference to it. Now the question
> is, what the hell does this do in your userContent.css ? Did you add it
> yourself ? Did the extension add it itself ? If it is the latter, then
> there's a serious issue with flashblocker. It shouldn't touch anything
> like this.
>
> So the real crash bug seems to be that if you bind some inexisting stuff
> to an element, firefox crashes. I must say I'm not surprised. Firefox is
> full of shi^H^Htuff like this.
Except that it's not that... I tried here and it doesn't crash...
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
