Closed Bug 430953 Opened 17 years ago Closed 17 years ago

Some toolbar icons hover state are moved 1px

Categories

(Firefox :: Theme, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

()

RESOLVED DUPLICATE of bug 430729

People

(Reporter: adelfino, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008042606 Minefield/3.0pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008042606 Minefield/3.0pre New Window and New Tab icons hover state are moved to the right several pixels. Reproducible: Always Steps to Reproduce: 1. Add new window/tab icon to a toolbar. 2. Watch the new window/tab icon. 3. Move the cursor over it. 4. Watch the new window/tab icon. Actual Results: The hover state icon is moved several pixels to the right. Expected Results: It should be in the same position.
Version: unspecified → Trunk
Flags: blocking-firefox3?
Summary: New Window and New Tab icons hover state are moved to the right → New Window and New Tab icons hover state are moved 1px to the right
Morphing, to add this bugs: The bug explained in comment 0 happens when using normal (ie not small icons). When using small icons, this bugs happen: 1. New Tab icon hover state is moved 1px to the right, and 1px to the bottom. 2. New Window icon hover state is moved 1px to the right, and 1px to the bottom. 3. Print this page icon hover state is moved 1px to the bottom.
Summary: New Window and New Tab icons hover state are moved 1px to the right → Some toolbar icons hover state are moved 1px
Confirmed on Windows XP, latest trunk.
Status: UNCONFIRMED → NEW
Ever confirmed: true
>1. New Tab icon hover state is moved 1px to the right, and 1px to the bottom. >2. New Window icon hover state is moved 1px to the right, and 1px to the >bottom. >3. Print this page icon hover state is moved 1px to the bottom. These three things should be fixed with bug 430759 landing.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Flags: blocking-firefox3?
You need to log in before you can comment on or make changes to this bug.