Closed
Bug 256437
Opened 20 years ago
Closed 19 years ago
Close Tab and Updates Available are too close to scrollbuttons
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: dunsalen, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040820 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040820 Firefox/0.9.3 The locations of the tab closing and Update gadgets are very poor, being adjacent to the scroll up and down arrows respectively. Just slight mislocation of the cursor, quite common with a touchpad mouse, causes the tab of interest to close, or the Update dialog to come up, in which case the user has to wait for it to finish loading, then see the buttons on it are ghosted out (Why?) and to finally get to the dialog close gadget, all when simply trying to scroll down a page a little. It is horribly inconvenient. Reproducible: Always Steps to Reproduce: 1.Open a page that is larger than the window 2.Notice how carefully you must position the mouse to scroll instead of closing the tab or calling the update dialog (which gadget does not even have a visible icon, poor design) 3. Actual Results: Slight mispositioning will close the tab of interest or call up the update dialog Expected Results: Slight mispositioning of the mouse should not cause large delays in browsing, like reloading the page or messing with a poorly designed update dialog
Updated•20 years ago
|
Summary: Locations of the tab closing and Update gadgets are very poor → Close Tab and Updates Available are too close to scrollbuttons
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•