412497 - Google is not prefilled in the dropdown for suspected forgeries

Status: VERIFIED FIXED

(Firefox :: Settings UI, defect)

Description

[Marcia Knous [:marcia]]

Attachment: Screenshot of security option in preferences

Seen using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2008011504 Minefield/3.0b3pre. Seen on Mac as well.

STR:
1. Go to Tools | Options and click on the Security Tab.
2. The Check box for "Tell me if the site I'm visiting is a suspected forgery is checked, but the radio button "Check by asking XXXX about each site I visit used to have Google prefilled, but it seems now you have to arrow down to get Google.

Expected: Google should appear in the list like it used to.
Actual: You have to arrow down to get Google to appear.

Comment 1

[Johnathan Nightingale [:johnath]]

Hmm - so this looks like the manifestation of bug 388652 not being done.  It's marked blocking+, but P4, so it might not make it.  On the other hand, it's silly for us to have preferences that users can't select, so we need to at very least remove the UI, if not just escalate 388652.

Dave - what do you think?  Hiding the pref UI is simple, but I suspect that without the rest of 388652, users could still stumble on to it (e.g. about:config).

Comment 2

[Dave Camp (:dcamp)]

We should probably just bump the priority of 388652, it should be an easy fix...

Comment 3

[Florian Quèze [:florian]]

I think this became visible when I landed bug 408940 yesterday.

Comment 4

[Reed Loden [:reed]]

Bug 412541 shows the same issue but with a different menu.

Comment 5

[Jesse Ruderman]

Is this fixed now?  On 2008-01-17, Florian checked in with the message

"Bug 408940 - Setting the value property of a menulist to null should remove the old value. Followup patch to fix regressions (bug 412497, 412534 and 412541) r=Mano, a1.9=schrep"

Comment 6

[Florian Quèze [:florian]]

(In reply to comment #5)
> Is this fixed now?

Yes.  Seems like the issue discussed in comments 1 and 2 is taken care of in bug 388652 so I guess I can resolve this bug.

Comment 7

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED using:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre)
Gecko/2008012304 Minefield/3.0b3pre

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2008012304
Minefield/3.0b3pre

-and-

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008012304
Minefield/3.0b3pre