Closed Bug 403196 Opened 17 years ago Closed 8 years ago

Cannot remove resizer in toolbar.

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: duncanspam, Unassigned)

References

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110703 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110703 Firefox/3.0b1

When customizing the toolbar, the resizer can not be removed.  It can be moved to the bookmark toolbar, but no further.  

Reproducible: Always

Steps to Reproduce:
1.Insert Resizer into toolbar.
2.Open customize toolbar
3.Try to remove it...you can't.
Actual Results:  
At best, move resizer to bookmark bar.  Usually, you end up deleting the object next to the resizer.
It is a regression from Bug 393718. Before Bug 393718 it had 4 drag-sensitive pixels (the first 4, horizontally), now only one (the first pixel); if you try dragging the second pixel it drags the adjacent object away). So it *is* possible to drag the resizer to the customize window, but some padding would be nice.
Blocks: 393718
Keywords: regression
Version: unspecified → Trunk
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-firefox3?
Flags: blocking-firefox3?
Yes, it was an issue on the older version. I double checked it on Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9b1) Gecko/2007110703 Firefox/3.0b1.

But it is no more applicable on the newer versions. Verified on:

Name 	Firefox
Version 	47.0a2
Build ID 	20160401004045
User Agent 	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0

It was a valid defect for older version but no more valid on the newer versions. Closing it as "RESOLVED - WONTFIX". Marked it as "WONTFIX" because it was applicable earlier but no more applicable for the newer versions of Firefox.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.