Closed Bug 282094 Opened 20 years ago Closed 17 years ago

First time browsing with Gnpernicus to nytimes.com invoking pop-up ad blocker kills speech

Categories

(SeaMonkey :: General, defect)

1.7 Branch
Sun
Solaris
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: korn, Unassigned)

Details

(Keywords: access)

1. Log into Solaris 10 FCS (on x86/x64 though I rather doubt that matters). 2. Launch Gnopernicus with speech and magnification 3. Launch mozilla for the first time for this user 4. Go to 'www.nytimes.com' (for the first time as this user) 5. A popup ad appears, and Gnopernicus starts to speak about it 6. Press NumPad 7 (thinking it was flat review) - the title bar is read 7. Press NumPad 2 (thinking you are going to continue flat reviewing). Speech is now dead.
please always include what build you're using. a bug report is not useful without it. http://www.mozilla.org/quality/bug-writing-guidelines.html reopen if you can provide needed information
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Please reopen this bug. Reporter specified this information: "Solaris 10 FCS (on x86/x64 though I rather doubt that matters)." That means Sun-patched Mozilla 1.7, the exact source tarball can be obtained from the Beijing Mozilla group.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
ok. it'd help to test with a more recent build (1.8b1). does this happen with any pop-up? An html testcase would help.
Version: Other Branch → 1.7 Branch
BTW a "more recent build" using 1.8 is probably not a good idea, as the accessibility patches are only partially integrated. The 1.7 versions are the ones where gnopernicus can be used reasonably well.
Related to meta bug 163832?
MozillaAS v1.7.x is not supported anymore. Can you reproduce with SeaMonkey v1.1.9 ?
(1 month later) No reply from reporter. (Would have been "Incomplete", now is) R.Invalid Reopen if you can reproduce with SeaMonkey v1.1.9.
Status: REOPENED → RESOLVED
Closed: 20 years ago17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.