An outline mode would be beneficial. Hierarchical outlining using headings (like MS Word outline mode) will help editing of large documents. Promote, Demote, Up, Down, Expand, Collapse, functionality will be basic requirements.
See also bug 127030, same bug for the browser (!)
It seems that outlining is a "plus" both for editing and browsing... Should browser and and editor teams collabrate on this issue? Please see http://bugzilla.mozilla.org/show_bug.cgi?id=127030
I'd mark it a dup.
Well, it's not an exact dupe. But the bugs are closely related.
OS: Windows 2000 → All
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Future
reassign to new account
Assignee: syd → composer
Status: ASSIGNED → NEW
This is almost impossible because of the flat model of HTML. Explain me how you are going to promote the h2 in this doc: <h3>foobar</h3> <div> <p>sdfsdfsdf</p> <h2>ffff</h2> </div> I know it is semantically badly formed, but it is a valid HTML document. So tell me...
> Explain me how you are going to promote the h2 in this doc: In the editor? Treat is as error in the document, so that the human editor fixes it. Maybe even reformat it to normal style. In the outline, I'd either ignore the h2 or the div, probably the former. > I know it is semantically badly formed, but it is a valid HTML document. I'd argue that it's syntactically valid, but semantically invalid and thus *not* a valid HTML document. BTW: HTML4 specs explicitly says: "Heading information may be used by user agents, for example, to construct a table of contents for a document automatically." <http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.5>
> I'd argue that it's syntactically valid, but semantically invalid and thus *not* > a valid HTML document. As a former member of the HTML Working Group that released the HTML 4 spec, I can only object to that. That's HTML, and that's valid HTML.
Why are we trying to prove that "this can't be done" using extreme examples? Outline mode may require that there should be no heading within a heading. If such case occurs it can simply refuse to promote, demote.
Assignee: composer → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
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
You need to log in before you can comment on or make changes to this bug.