Open
Bug 264997
Opened 20 years ago
Updated 14 years ago
Help Viewer contains inconsistent HTML
Categories
(SeaMonkey :: Help Documentation, defect)
SeaMonkey
Help Documentation
Tracking
(Not tracked)
NEW
People
(Reporter: rjkeller, Assigned: neil)
References
(Depends on 1 open bug)
Details
In mail_help (my main inspiration for filing this bug), there are <h1> tags when they should be <h2>, etc. These need to be fixed, because the CSS isn't designed to work this way. There are other docs with this problem too. Should be a simple Find and Replace. I got a quick script I'm going to run through the docs to perfect the layout. Got this on my to-do list. Should be done after bug 232794.
Reporter | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → mozilla1.8alpha5
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: rjkeller → neil
Status: ASSIGNED → NEW
Target Milestone: mozilla1.8alpha5 → ---
Comment 1•15 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Fixing h1 and h2 tags in mail_help could be done as part of splitting it up in bug 246405, so marking as a dependency (just in case it is still an issue).
You need to log in
before you can comment on or make changes to this bug.
Description
•