Closed
Bug 122806
Opened 23 years ago
Closed 22 years ago
Update of Help files
Categories
(Documentation Graveyard :: Help Viewer, defect, P3)
Documentation Graveyard
Help Viewer
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cotter, Assigned: cotter)
References
Details
(Whiteboard: [adt1 rtm] [ETA 06/24])
Attachments
(1 file)
(deleted),
text/html
|
Details |
The Help files need updating to track changes in the UI, functionality
changes, and other content changes and additions. The files will be checked in
on an as-needed basis through Mozilla 1.0.
The content files are mostly either HTML or GIF. There are also some RDF files
for the TOC that contain content. We'll check in updates for these content files
on the basis of r=oeschger or r=cotter only, without further approvals, as we
have done in the past.
Other changes to RDF and XML files related to the underlying help system
mechanism (as opposed to content) are also covered by this bug, but require the
usual approval process, including sr.
Assignee | ||
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.0
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•23 years ago
|
||
This bug confuses me as to how to go about filing bugs concerning help content.
For example, i have noticed that the help content concerning Mail/News does not
mention labels. So, should i file a new bug about that or wait until new help
files are checked in? Is there ongoing work being done on the help content, or
is this something that's going all to be written very close to the 1.0 release?
Comment 2•23 years ago
|
||
Leston - I don't think this is a good place to gather those sorts of
updates/issues, as important as they are. This one is being used more as a
marker for routine content updates, and may not get the attention of the authors
who can make the changes you describe. There is 46917, though that's also sort
of tangential. I think it's best to write a new bug for content that's needed.
Or wrong.
Also, Sean, you want to ACCEPT this bug so we can make it official? Or I can.
Status: NEW → ASSIGNED
Added nsbeta1+ (not previously nominated), [adt3].
Sean, I assume your reference to Moz 1.0 in your first comment needs updating.
But what is the correct milestone for this? I'll ask ADT advice.
Keywords: nsbeta1+
Whiteboard: [adt3]
Setting status to rtm, resetting milestone.
Whiteboard: [adt3] → [adt1 rtm]
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 5•23 years ago
|
||
*** Bug 117567 has been marked as a duplicate of this bug. ***
Comment 6•23 years ago
|
||
any thoughts on what to do with bug 117569?
it's hanging in the air at the moment...
I did write the spec to a usable point, and I even implemented my spec locally
for a time.
sorry to see it go to waste...
also making this block the help system tracking bug
Blocks: 67376
Comment 7•22 years ago
|
||
If you're looking for helpfile material, the Mozilla 1.0 startpage FAQ draft,
latest update, is attached after this comment. It at least mentions stuff
like the tab browser, popup blocking, etc.
Jayeth (who does moztips) and I are probably going to end up doing lots of
other helpfile material. Er, after 1.0 is out ;-)
Comment 8•22 years ago
|
||
Comment 9•22 years ago
|
||
*** Bug 135910 has been marked as a duplicate of this bug. ***
Comment 10•22 years ago
|
||
I believe the updated help files were supose to be complete by 06/20. Pls update
the ETA in the Status Whiteboard. thanks!
Whiteboard: [adt1 rtm] → [adt1 rtm] [ETA 06/24]
Assignee | ||
Comment 11•22 years ago
|
||
All final help files for Mach V have been checked in and handed off for translation.
The help files in the Mozilla trees have not yet been updated with the latest
Netscape files or sanitzed for Mozilla. Changing milestone and leaving bug open
for now, but perhaps that Mozilla-side effort should have a different bug with a
different owner, so we can close this one out.
Target Milestone: mozilla1.0.1 → mozilla1.0.2
Comment 12•22 years ago
|
||
We have bug 46917 which tracks the ongoing sanitization work mentioned in
comment 11. Closing this one out.
Comment 13•22 years ago
|
||
Okay, sounds good to me, marking verified
Status: RESOLVED → VERIFIED
Keywords: fixed1.0.1 → verified1.0.1
Comment 14•22 years ago
|
||
reopening for some 1.1 mozilla help content updates, keeping blanket approval.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 15•22 years ago
|
||
Checked in updates to mozilla trunk for search-db.rdf.
Comment 16•22 years ago
|
||
re-resolve as FIXED. Use bug 54561 for further help file changes
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Component: Help → User
Product: Browser → Documentation
Hardware: PC → All
Resolution: --- → FIXED
Target Milestone: mozilla1.0.2 → ---
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•