Mozilla documentation should list Talkback's port numbers

RESOLVED WORKSFORME

Status

Core Graveyard
Talkback Client
--
trivial
RESOLVED WORKSFORME
17 years ago
9 years ago

People

(Reporter: raccettura, Assigned: Shiva Thirumazhusai)

Tracking

({relnote})

Trunk
relnote

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
I haven't been able to use talkback since I installed my firewall.. how about
listing which ports talkback needs in the readme so that a network admin can
enable those ports if needed?
Confirming. Marking All/All. 

Old summary:
"Port Number"

New summary:
"Mozilla documentation should list Talkback's port numbers"

Reporter: For future reference, please include your BuildID in your bug reports.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac System 9.x → All
Hardware: Macintosh → All
Summary: Port Number → Mozilla documentation should list Talkback's port numbers
Adding block: bug 100230.
Blocks: 100230

Comment 3

16 years ago
I think the relnote keyword applies here.
Ok, keyword added.
Keywords: relnote

Comment 5

16 years ago
What should the release note say? (Specifically, what port numbers should be
listed?)
(Reporter)

Comment 6

16 years ago
This bug itself is in regards to me being unable to get Talkback working when
behind my firewall...

If someone here could reveal what I (and others) should be doing to ensure
talkback works... Quote them!

I would love to submit more talkback reports than I do... But when I'm home with
my laptop behind the firewall, I can't.

At school with it, I do.  I catch up...

But what about those who don't have another network to use?

Comment 7

15 years ago
http://mozilla.org/releases/mozilla1.2/#qfa which has been in the release notes
isn't sufficient?

Comment 8

15 years ago
wfm
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME

Updated

9 years ago
Component: Talkback Client → Talkback Client
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.