348661 - When a new search engine is available for addition to the search box the padding for "Add "Technorati Search"" is missing a few pixels

Status: RESOLVED WORKSFORME

(Firefox :: Search, defect)

Description

[Bryan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060814 BonEcho/2.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060814 BonEcho/2.0b1

When a new search engine is available for addition to the search box the padding for "Add "New Search Engine Search"" is not aligned with the search engines above the separator or "Manage Search Engines" below the separator.

Reproducible: Always

Steps to Reproduce:
1) Launch FF (and ensure Technorati hasn't been added a search engine)
2) Navigate to http://www.technorati.com/
3) Observe the search box drop down "glow"
4) Click the search box drop down and observe that the padding for "Add "Technorati Search"" is out of alignment with the items above and below it

Actual Results:  
The padding for "Add "Technorati Search"" is out of alignment with the items above and below it

Expected Results:  
The padding for "Add "Technorati Search"" is in alignment with the items above and below it

Comment 1

[mozilla]

(In reply to comment #0)

WFM: http://cgi.tolien.co.uk/pics/ffsearch.png

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060814 BonEcho/2.0b1 ID:2006081413

Comment 2

[Bryan]

> (In reply to comment #0)
> 
> WFM: http://cgi.tolien.co.uk/pics/ffsearch.png
> 
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060814
> BonEcho/2.0b1 ID:2006081413
> 
Yours works as designed because you have Favicons enabled.  I do not.  I have mine disabled via User.js as shown in the screen shot attached.

~B

Comment 3

[Bryan]

Attachment: With favicons disabled padding is wrong for "Add "Technorati Search""...

Comment 4

[Bryan]

Attachment: With favicons disabled padding is wrong for "Add "Technorati Search""...

Comment 5

[Bryan]

This is no longer an issue in current trunk builds!

~B