Closed
Bug 116795
Opened 24 years ago
Closed 23 years ago
Include TalkBack with Mozilla for Mac OS X
Categories
(Core Graveyard :: Talkback Client, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.3final
People
(Reporter: cross, Assigned: jj.enser)
References
Details
Attachments
(2 files)
|
6.69 KB,
text/plain
|
Details | |
|
477 bytes,
patch
|
leaf
:
review+
sfraser_bugs
:
superreview+
|
Details | Diff | Splinter Review |
Despite both 0.9.6 and 0.9.7 release text at www.mozilla.org implying that
the MacOS X build had talkback code, none of the releases I've run on my
MacOS X machine (starting just before 0.9.6, through the 21-Dec-2001 release
of 0.9.7) actually ever do any talking back that I can see. The old MacOS
9 images I used to run would ask me questions when it crashed. The MacOS X
one does not.
Please either add talkback support to the MacOS X build, or remove it from
the gray block of links and description that indicate it does have talkback
support.
Comment 1•24 years ago
|
||
I've removed the mac osx entry from the "try these' box on the releases page.
thanks for pointing out that it does not have talkback.
Until talkback is enabled in OS X, you can work around this by enabling
mac console logging. I'm not a mac osx user, but i think it works like this:
- Open the macintosh applications folder
- open the utilities sub-folder
- start the console application.
- open prefs menu
- choose crashes tab.
- check "log crashes", and "automatically display logs"
- Quit the console app.
The next time any mac app crashes it will throw up a text editor containing
the crash log. When mozilla crashes, attach this crash log to a bugzilla
bug.
If you crash several times at the same place, you'll probably get the same
crash log for each crash. Try and pay attemtion to this and file only one
bug for each unique crash log.
Comment 2•24 years ago
|
||
*** Bug 121364 has been marked as a duplicate of this bug. ***
Comment 3•24 years ago
|
||
Could the #1 comment be posted somewhere else on mozilla.org's web site, or in a
file which would be in the disk image ?
Blocks: 121367
Updated•24 years ago
|
Severity: normal → major
Summary: No talkback support for MacOS X? → No talkback support for MacOS X
| Reporter | ||
Comment 4•24 years ago
|
||
Changing to be an RFE, since as noteded in comment #1, this is a known missing
feature, and it's not longer presented in a way that makes you think it's
supposed to work. It would be very good for this to be added, but I have no
sense of how hard that will be.
Severity: major → normal
Summary: No talkback support for MacOS X → RFE: Add talkback support for MacOS X
The main problem with the lack of Talkback is that manually posting console logs
to bugzilla is a pain. Most users don't want to do it. Heck, they don't know HOW
to do it, or even that they SHOULD do it at all. Consequently, the project never
sees most of the crash data for Macs.
Comment 6•24 years ago
|
||
we are getting closer on licencing terms with support.com...
hoepfulling we can get going on this by the end of this
month or the beginning of next.
Comment 7•24 years ago
|
||
no updates on this bug for two months - what is the status of talkback-enabled
OS X builds?
This would be a useful feature.
I've been experiencing random crashes (posted as seperate bug) with the latest
RC and 1.0 releases, but hadn't thought to check the console... urg.
If the support.com stuff doesn't work out, how about a feature to create a new
mail message on launch with the file ~/Library/Logs/Mozilla.crash.log as the
body, addressed to somewhere that a script could parse it? Rename the file to
Mozilla.crash.sent.log so it doesn't get triggered next time, and developers
don't get their file whacked.
The user would have to turn on CrashReporter once.
Comment 11•23 years ago
|
||
Talkback porting to Mac OS X is a Netscape-internal issue. I opened an internal
(bugscape) bug on it: http://bugscape.mcom.com/show_bug.cgi?id=18165.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Comment 12•23 years ago
|
||
*** Bug 160202 has been marked as a duplicate of this bug. ***
Comment 13•23 years ago
|
||
How did Talkback for Chimera happen before Mozilla?
Comment 14•23 years ago
|
||
We're using chimera as a testbed for talkback on Mac OS X. It will show up in
Mozilla soon enough.
Comment 15•23 years ago
|
||
Can we get an open Bugzilla bug on Talkback in Mozilla OS X Proper... if nothing
more then for tracking/ETA? Or just reopen this one?
I moved to chimera myself in the last month or so due to an increased rate of
crashing with recent OS X Mozilla releases... a problem I don't anticipate
changing unless those crashes get reported... and no, I don't have the time to
futz with the console every time i crash... infact because I crashed I have to
redo whatever work I was in the middle of and have *less* time.
Comment 16•23 years ago
|
||
*** Bug 190647 has been marked as a duplicate of this bug. ***
Comment 17•23 years ago
|
||
*** Bug 190662 has been marked as a duplicate of this bug. ***
Comment 18•23 years ago
|
||
Reopening since TalkBack exists for OS X now.
Severity: normal → enhancement
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: RFE: Add talkback support for MacOS X → Include TalkBack with Mozilla for Mac OS X
Comment 19•23 years ago
|
||
-> jj, this is just waiting on nightly build automation to include talkback in
the mozilla package
Assignee: sfraser → jj
Status: REOPENED → NEW
Updated•23 years ago
|
Target Milestone: --- → mozilla1.3final
| Assignee | ||
Comment 20•23 years ago
|
||
| Assignee | ||
Comment 21•23 years ago
|
||
Comment 22•23 years ago
|
||
Comment on attachment 114070 [details] [diff] [review]
Patch to ns/fullsoft/Makefile.in to use heatware instead of twister for MacOSX
r=leaf
Attachment #114070 -
Flags: review+
Comment 23•23 years ago
|
||
I assume we got the right symbols onto the talkback server for 1.3b?
Updated•23 years ago
|
Attachment #114070 -
Flags: superreview+
| Assignee | ||
Comment 24•23 years ago
|
||
patch to ns/fullsoft/Makefile.in checked in.
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•