As long as both extensions are installed and Firefox is set to show a
blank page at startup, the browser ignores the
browser.urlbar.hideGoButton about:config directive (the go button is
always shown).
In addition, with both extensions installed and the startup page set to
blank, the find as you type feature will take over when typing into any
text box. This will continue to happen until the browser window loses
and regains focus.
Eliminating any of these conditions fixes both issues. I've temporarily
chosen to use a default homepage rather than about:blank.
I know there are more than a few bugzilla entries concerning the find
as you type feature and text input boxes, but it's strange that this
combination causes the behaviour 100% of the time.
Thanks for all your hard (and smart) work, Joe. As soon as Christmas is
over and I can survey the damages, I'll gladly consider donating.
John Hansen
http://yellow5.us
Apart from all that, many many thanks, Joe, for a fantastic extension.
Tadhg
Yes, i to on FF2.0
And i can't copy adresses from Sites and then paste this in the
adressbar :(
The adress is also not click and mark the all content of the adress,
all in the adressbar. I must mark all over hold mouse clicked and than
move!
The newest beta is installed
That's a thing that buggers me too (Fx 2 @ OSX 10.4.8). I cannot enter
any search terms in the Firefox startpage, because FAYT takes over. If
I 'disable validation in the browser' in HTML Validator it works as
supposed. But that's not what I want.
I don't know if it has anything to do with this issue, but I know that
the 'Tamper data' extension also does not like HTML Validator. You'll
get an explicit warning to turn HTML Validator off. That's far from a
perfect solution, but somewhat workable.
The common thing in Tamper data en the new Firebug is that they both
intercept network traffic and http-headers (with the new Net-tab). Hope
it helps... although I think Marc Gueury from the HTML Validator may
want to look at this issue too.
Joe, if you're reading this. :-) See:
http://users.skynet.be/mgueury/mozilla/
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
I was able to prevent the focus bug from happening by either
preventing HTML Validator from
inserting XUL image elements into its tooltip, or by preventing
Firebug from loading the HTML
files into the iframes. So, I suppose that either one of those
actions has some effect on Gecko's
focus infrastructure and causes it to go off the rails.
There's really no lesson to be learned here for extension developers,
other than to expect
Firefox to have bugs every now again and don't go insane when you run
into them :)
- Joe
- Joe