Open
Bug 133475
Opened 23 years ago
Updated 15 years ago
Implement html tidy in composer
Categories
(SeaMonkey :: Composer, enhancement)
SeaMonkey
Composer
Tracking
(Not tracked)
NEW
People
(Reporter: neo-8ba, Unassigned)
References
Details
(Keywords: helpwanted, testcase)
Attachments
(1 file)
|
245 bytes,
text/html
|
Details |
When you import a page in composer, it produces invalid html code. Could it be
possible to implement html tidy in composer so that we could "tidify" it before
publishing ?
Comment 1•23 years ago
|
||
Unless I'm mistaken, you can already do this by setting 'Reformat HTML source'
in Edit > Preferences > Composer.
| Reporter | ||
Comment 2•23 years ago
|
||
It hasn't all the features of tidy (convert to xhtml....), and it DOESN'T
produce valid html or xhtml code.
Comment 3•23 years ago
|
||
jjlapin--can you please file individual bugs or explain here what tags are being
mangled for html? The only bug I know of is for tbody in unsupported dtds.
| Reporter | ||
Comment 4•23 years ago
|
||
When using composer to edit a page with xhtml dtd, composer doesn't replace the
dtd with html 4.01 dtd, but add html 4.01 code, so producing invalid code.
Testcase provided: open the testcase in composer, save it as charset utf-8 (or
what you want) and go validate it @ w3c---> xhtml generated is invalid.
| Reporter | ||
Comment 5•23 years ago
|
||
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Comment 6•23 years ago
|
||
*** Bug 154140 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
Keywords: helpwanted
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•17 years ago
|
Assignee: composer → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
Comment 8•16 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
Comment 9•15 years ago
|
||
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in
before you can comment on or make changes to this bug.
Description
•