The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

However, this is frowned upon by accessibility purists who rightfully say let the user control it. I would agree, but in this case it would appear most people who have this little Google app installed are unaware and/or oblivious to all of the different behaviors it creates in forms.

I wonder who's brilliant idea it was to bundle Google Toolbar with FireFox ??

Google's. Mozilla are happy because Google will pay them for the priveledge. IIRC when you download Firefox from the Mozilla site you don't get the toolbar.

Originally Posted by Shaun(OfTheDead)

I'm not going to resort to using an image for the label so I guess I'll just have to live with it... yaah[/FONT] :S

Make sure you give it appropriate alt text or you've rendered it completely useless to anybody browsing without images. Of course the Google toolbar might pick up on that alt text...

Why don't you let the google toolbar do it's job and let the user see which form elements it can auto-fill for them? If you don't like that, switch it off on your browser, but don't ruin that function for everybody else out there

There's a bit more to it than that. From an accessibility point of view, if you use a change of background colour on :focus to indicate to users where they are in a form, that change will be lost to people with the Google Toolbar (and FF's autofill extension) unless you override it.