Open
Bug 637149
Opened 13 years ago
Updated 2 years ago
Window resize gripper should always be the right-most element.
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: mark, Unassigned)
Details
Attachments
(1 file)
1.35 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b12) Gecko/20100101 Firefox/4.0b12 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b12) Gecko/20100101 Firefox/4.0b12 The add-on bar, when having icons placed in it by add-ons, shows the window resize gripper in an arbitrary location, while it should always remain the right-most element in the add-on bar (corner of the window). Since the gripper and add-on icons cannot be positioned in the "customize" mode for toolbars either in b12, it can't be corrected. Reproducible: Always Steps to Reproduce: 1. enable the add-on bar 2. install an add-on that places an icon in the add-on bar (e.g. adblockplus) Actual Results: The gripper is put to the left of the add-on icon in the add-on bar Expected Results: The gripper should be in the corner of the window, always.
Reporter | ||
Comment 1•13 years ago
|
||
This image shows the problem on my Windows XP installation, after installing adblockplus. (beta12)
Updated•13 years ago
|
Version: unspecified → Trunk
Comment 2•13 years ago
|
||
This is not reproducible by simply following your STR on Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b13pre) Gecko/20110227 Firefox/4.0b13pre. It is reproducible if you first install the Status-4-Evar addon, as in Bug 637154
OS: Windows XP → All
Reporter | ||
Comment 3•13 years ago
|
||
@Alex: you are right! Apparently if you had status-4-evar installed once upon a time, even if completely removed before installing anything else, it is broken. A factory-profile doesn't display this behavior. Since I didn't have anything else installed add-on wise when I wrote this bug, the STR didn't include this. The fact that it can end up in any location but the end of the bar is, IMO, a problem; it should probably be forced in it's correct spot at all times.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•