Closed
Bug 184368
Opened 23 years ago
Closed 21 years ago
dirty rectangles should not be shown when not necessary
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: tuxracer, Assigned: jag+mozilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Dirty rectangles around buttons and links should not be shown when not
necessary. By dirty rectangles I mean the dotted outline around text to show
that that particular element is in focus. This is useful if you are using the
keyboard to navigate the GUI, however when the mouse is in use it just makes
things look ugly.
Since the indroduction of Windows 2000, Windows only shows dirty rectangles when
the keyboard is being used to navigate the GUI. This is the default behavior of
Windows 2000/XP apps. Mozilla should behave in the same manner. I think that it
looks much nicer not showing the dirty rectangles when they are not necessary.
Reproducible: Always
Steps to Reproduce:
Comment 1•23 years ago
|
||
Well, going by what happens in IE 6.0 on win2k, yes, it does not show a "focus
ring" (dirty rectangle) in the 'Tools->Internet Options' dialog if you are
using a mouse. It does show focus ring, when you tab-navigate that dialog.
However, as soon as you have done any keyboard navigation, then changing focus
with the mouse will now cause it to show a focus ring. Bug or feecher.
-> fyuchher.
Target Milestone: --- → Future
| Reporter | ||
Comment 2•23 years ago
|
||
I think that is the way it is meant. Because after you use tab to navigate the
GUI the app assumes that you are trying to use the keyboard to navigate the GUI
and then you need the dirty rectangles. But after you start using the mouse, if
you unfocus on that window, then refocus, all using the mouse, they will
disapear again.
I'm using Moz 1.7.3 on WinXP and I don't see unnecessary "dirty rectangles"...
Reporter, do you still see this problem with the latest nightly (or even 1.7.3)?
If not, this bug can be closed. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•