Closed Bug 120176 Opened 23 years ago Closed 23 years ago

Active Accessibility: tweaks to STATE_OFFSCREEN calculation

Categories

(SeaMonkey :: General, defect, P2)

x86
Windows 2000
defect

Tracking

(Not tracked)

RESOLVED FIXED
mozilla0.9.8

People

(Reporter: aaronlev, Assigned: aaronlev)

Details

(Keywords: access)

Attachments

(1 file)

It's been requested that we consider an item that has at least 5 pixel rows and
5 pixel columns visible as on screen.

Right now, if any part of an object is offscreen we have flagged it with
STATE_OFFSCREEN.

Most objects have a little bit of whitespace around them. After a little trial
and error, I found that requiring 12 pixels on screen is a good number.
Keywords: access, fcc508
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9.8
Whiteboard: seeking r=, sr=
Comment on attachment 65117 [details] [diff] [review]
Changes IsRectVisible to take aMinPixels argument, to require a minimum number of pixel rows/cols to be visible

Note: There isn't any need to make modifications to nsViewManager2.h and
nsViewManager2.cpp. They are obsolete and no longer part of the build.

r=kmcclusk@netscape.com
Attachment #65117 - Flags: review+
Looks fine to me. sr=waterson.
checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: seeking r=, sr=
Someone should remove nsViewManager2.*.

"I know what I must do, but I am afraid to do it"
What is it viewmgr2 still doing in there? Is it an old experiment or something?
Whoever left both of them in there in the first place should remove it.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: