172583 - - checked and - unchecked are insulting me, and I don't believe i'm running a screen reader

Status: RESOLVED INCOMPLETE

(SeaMonkey :: Installer, defect)

Description

[timeless]

Bug 104477 If screen reader is present, actively append word "checked" or
"unchecked" to checkboxes in components list.

This bug is driving me nuts.

Here's the checkin comment:
1.72 <[e-mail]> 24 Jun 2002 22:36
Support in the listbox for Screen Readers
(Bug 10477, r=ssu, sr=dveditz, mozilla1.0.1+)

curt: in the future, please copy the bug number from the bug instead of typing
it from memory.

I'm not sure if I'm running a screen reader. If you think I am, please indicate
which of the following is my screen reader:
Idle
System
smss
csrss
winlogon
services
lsass
svchost
spoolsv
tcpsvcs
svchost
llssrv
sfmprint
regsvc
MSTask
snmp
termsrv
lserver
WinMgmt
wins
dns
Dfssvc
sfmsvc
csrss
winlogon
svchost
Explorer
internat
regedit
mshta
taskmgr
WINZIP32
Explorer
cmd
rdpclip
Explorer
internat
Explorer
cmd
taskmgr
regedit
cmd
java
notepad
mdm
netdde
clipsrv
cmd
WINZIP32
mozilla
mozilla
notepad
netmon
csrss
winlogon
scrnsave.sc
csrss
winlogon
talkback
notepad
notepad
csrss
winlogon
rdpclip
Explorer
internat
Explorer
FILEMON
taskmgr
ttermpro
PSLIST

I don't mind being told that a checkbox is checked. But I can't stand seeing
that text.

--
Configuration:
w2k adv svr, terminal services. in a terminal session (on my laptop)
ran mozilla-win32-installer.exe - 213 KB (218,320 bytes) - October 03, 2002,
7:43:06 PM
(ie the latest trunk stub installer)

Please fix the installer so that it does *not* show the text unless it has a
really good reason. the fact that i have narrator installed doesn't qualify,
it's not running, and it's certainly not running on my terminal session (w2k
sessions don't support sound)

Here's what happens when i try to run narrator in the terminal session:

Narrator Installation error

Narrator was unable to find a sound card on the computer. Check that a sound
card is installed and working properly.

OK

(it quits)

I'm frequently available on irc. If you need me to run a test app so that you
can find out what flag you should have been checking.

Comment 1

[Aaron Leventhal]

Somehow your SPI_SCREENREADER flag is probably being set by one of the apps you
use. Can you think of which that might be?

Comment 2

[Henrik Gemal]

not really a mozilla issue. some program is telling the system that it's a
screenreader.

Comment 3

[timeless]

i provided an application list and i'll run any test app you give me. Please
provide some guidance.

Comment 4

[Henrik Gemal]

I'm just saying it's not a mozilla issue. I cant tell which application it is
from the task list. Sorry...

Comment 5

[timeless]

until someone proves that the api is correct i'm accusing the code of being
wrong, read the stupid list of apps, none of them are remotely reasonable
candidates for that flag (which i can't even find useful documentation for using
google/msdn)

Comment 6

[Henrik Gemal]

try shutting down applications until the error goes away. Then you know the
"bad" app.

I've never seen/heard this bug before, and no one else has reported it.

Comment 7

[Daniel Veditz [:dveditz]]

We should check the return value of SystemParametersInfo and make sure
bScreenReader is initialized to false, but since you're using Win2K where the
SPI_GETSCREENREADER parameter is supported I doubt that will solve the problem
for you.

http://lxr.mozilla.org/mozilla/source/xpinstall/wizard/windows/setup/extra.c#681

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

old XPFE installer is dead.