Closed
Bug 153061
Opened 23 years ago
Closed 21 years ago
Help glossary for Talkback links wrong (and Gecko not mentioned)
Categories
(Documentation Graveyard :: Help Viewer, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: hauser, Assigned: rjkeller)
References
()
Details
As per error http://bugzilla.mozilla.org/show_bug.cgi?id=153046, I am having
troubles with gecko. Unfortunately searching mozilla help for "gecko" doesn't
return any results. Also the Gecko help refers only to a link that is
unreachable richt now
(http://www.fullcirclesoftware.com/?D=NetscapeGecko1%2E0Win322002053015).
Similarly, searching mozilla help for "talkback" yields nothing - talkback
(v2.2) is apparently the name of the "call home feature" of gecko (at least
until 1999 - the date their (c) statement refers to). Any hints?
Build 2002053012
Comment 1•23 years ago
|
||
Do you search in the Mozilla help or in the talkback help ?
Reporter | ||
Comment 2•23 years ago
|
||
Mozilla help - there is no talkback help, only a URL to an unreachable server.
Tracing route to www.fullcirclesoftware.com [216.35.135.170]
over a maximum of 30 hops:
8 20 ms 30 ms 30 ms zcr1-so-6-0-3.Frankfurtfri.cw.net [166.63.202.6]
9 30 ms 30 ms 40 ms bcr2-so-2-0-0.Frankfurt.cw.net [166.63.193.205]
10 130 ms 130 ms 130 ms dcr1-loopback.NewYork.cw.net [206.24.194.99]
11 130 ms 130 ms 130 ms 206.24.207.82
12 131 ms 130 ms 130 ms 64.15.224.17
13 130 ms 130 ms 140 ms bbr02-p3-0.stng02.exodus.net [216.32.132.209]
14 210 ms 210 ms 211 ms bbr01-p0-0.sntc05.exodus.net [216.32.132.18]
15 211 ms 210 ms 210 ms bbr01-p1-1.sntc04.exodus.net [209.1.169.137]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
...
Fullsoft was bought out by another company and is now defunct. They were the
orignal manufacturers of the "Talkback" product. It is a third-party product
that is no longer supported. So you won't be getting any help from them,
unfortunately.
![]() |
||
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•22 years ago
|
||
-> documentation
Updated•22 years ago
|
Summary: Gecko not mentioned in Mozilla Help → Help glossary for Talkback links wrong (and Gecko not mentioned)
Comment 5•22 years ago
|
||
The glossary entry for Talkback needs added to the glossary pane. It is in the
gloassary file.
Comment 6•22 years ago
|
||
I've removed the talkback item and the reference to the NS Talkback stuff from
the glossary.
Someone want to paste a short Gecko glossary item in here? I'll add it and then
check in this update (with a bunch of other small Netscape cleansing fixes).
Status: NEW → ASSIGNED
Keywords: helpwanted
Comment 7•22 years ago
|
||
FIXED. removed talkback talk
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 8•22 years ago
|
||
Ian, I don't like Talkback being removed from glossary. A better sol'n would be
to post something about talkback in moz-org and then link to it.
oh, by the way, you didn't remove talkback from search index, so either fix that
or unfix this bug
Comment 9•21 years ago
|
||
Reopen. search index needs fixing.
R.J. Keller, care to re-add talkback in now that there is
http://www.mozilla.org/quality/qfa.html ?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•21 years ago
|
||
.
Assignee: oeschger → rlk
Status: REOPENED → NEW
Keywords: helpwanted
QA Contact: tpreston → stolenclover
Assignee | ||
Comment 11•21 years ago
|
||
sounds good to me. Mozilla does use talkback, so users should be able to know
what it does, but is the glossary the most appropriate place?
I'm not sure where else it would go.
Assignee | ||
Comment 12•21 years ago
|
||
Mozilla Help is not really the place to describe Talkback.
Daniel, As you said in bug 89814, the glossary should not turn into a book. This
is more appropriate for the Mozilla Website.
Talkback has it's own help anyway. I agree with oeschger in marking this FIXED.
The search problem was also fixed when search-db.rdf was removed.
Status: NEW → RESOLVED
Closed: 22 years ago → 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•