Public SourceMage Discussion List

[Jeremy Blosser <jblosser-smgl AT firinn.org>]

Oh, I built this against gtk1, that may be related to the chrome error, I
don't know.

On Mar 01, Jeremy Blosser [jblosser-smgl AT firinn.org] wrote:
> Ok, so I've been doing some research on Firefox's "find in page" not
> working.  Basically the mozilla team claims that this is not a bug and will
> Just Work if you Just Build Firefox Correctly, You Stupid Heathens.  See 
> here:
> https://bugzilla.mozilla.org/show_bug.cgi?id=251543
> 
> Anyway, taking them at their word, I tried a completely clean build:
> ==============================
> rm -rf ~/.firefox
> rm -f ~/.mozilla/firefox/*/compreg.dat
> 
> lftpget 
> ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.0.1/source/firefox-1.0.1-source.tar.bz2
> tar -xjvf firefox-1.0.1-source.tar.bz2
> cd mozilla
> cp browser/config/mozconfig .mozconfig
> ./configure --enable-xft --disable-freetype2 # it won't compile without 
> these on my box
> make
> cd dist/bin
> LD_LIBRARY_PATH=. firefox-bin
> ==============================
> 
> This did it, find in page worked.  Looking at our build compared to the
> distributed browser/config/mozconfig, I decided the most likely culprit was
> our use of a bare --enable-extensions.  I suspect this attempts to include
> either all or a predefined set of extensions, including the forbidden
> typeaheadfind extension.  I tried using the explicit list from mozconfig,
> and it does work.
> 
> The patch is attached; if you apply this, cast -c, and then
> 'rm -f ~/.mozilla/firefox/*/compreg.dat', and you should get a firefox with
> working find in page.
> 
> I didn't apply this to devel yet because there are issues:
> 
> 1) How would we codify the compreg.dat removal in the spell?
> 'rm -f /home/*/.mozilla/firefox/*/compreg.dat' would do it, but do we do 
> that
> kind of thing to people?  I think this is just a cache, so it should be
> safe, anyway.
> 
> 2) The first few times I run firefox after casting this, I get the error:
> "*** Failed to load overlay 
> chrome://layoutdebug/content/layoutdebug-overlay.xul"
> And it doesn't work, I have to ctrl-c it.  After I try to run it a few
> times it starts working.  I don't know what this is, maybe some kind of
> initialization race condition.  'rm -rf ~/.mozilla' didn't fix this, it
> actually seemed to make it work (more restarts til it would work).  Ideas
> anyone?

> diff -dupr /home/jblosser/p4/smgl/devel/http/firefox/BUILD firefox/BUILD
> --- /home/jblosser/p4/smgl/devel/http/firefox/BUILD   2005-02-26 
> 19:05:34.000000000 -0600
> +++ firefox/BUILD     2005-03-01 00:18:41.290230384 -0600
> @@ -35,7 +35,7 @@ fi &&
>    --disable-mailnews                              \
>    --disable-composer                              \
>    --enable-crypto                                 \
> -  --enable-extensions                             \
> +  
> --enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth
>  \
>    --enable-single-profile                         \
>    $OPTS                                           &&
>  make

Attachment: pgpScU355mpEa.pgp
Description: PGP signature