Closed Bug 640975 Opened 14 years ago Closed 12 years ago

(a) formatting problem (b) bug in generated HTML

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: cjw, Unassigned)

Details

(Whiteboard: dupme)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 Build Identifier: Thunderbird 3.1.9 (en0GB) (a) Blockquote seems to reduce font size. The font size is not restored at the end of the blockquote. See (b) (b) See validation report below From - Fri Mar 11 10:45:14 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: FCC: mailbox://nobody@Local%20Folders/Sent X-Identity-Key: id4 Message-ID: <4D7A438A.5040507@ncf.ca> Date: Fri, 11 Mar 2011 10:45:14 -0500 From: "Colin J. Williams" <cjw@ncf.ca> X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 Subject: ugh Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#ffffff"> <font size="+1">Now is the time, to come to the aid<br> of the party<br> </font> <blockquote>The quick brown<br> fox<br> </blockquote> jumos <br> </body> </html> W3C Markup Validation Service Check the markup (HTML, XHTML, …) of Web documents * Jump To: * Notes and Potential Issues * Validation Output Error found while checking this document as HTML 4.01 Transitional! Result: 1 Error, 1 warning(s) Source: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#ffffff"> <font size="+1">Now is the time, to come to the aid<br> of the party<br> </font> <blockquote>The quick brown<br> fox<br> </blockquote> jumos <br> </body> </html> Encoding: utf-8 Doctype: HTML 4.01 Transitional Root Element: HTML HP LogoThe W3C validators are hosted on server technology donated by HP, and supported by community donations. Donate and help us build better tools for a better web. Options Show Source Show Outline List Messages Sequentially Group Error Messages by Type Validate error pages Verbose Output Clean up Markup with HTML-Tidy Help on the options is available. Notes and Potential Issues The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document. 1. Info Using Direct Input mode: UTF-8 character encoding assumed Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified. If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document. ↑ Top Validation Output: 1 Error 1. Error Line 7, Column 9: end tag for "HEAD" which is not finished </head> ✉ Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p> Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on. ↑ Top * Home | * About... | * News | * Docs | * Help & FAQ | * Feedback | * Contribute | W3COpen-Source I heart Validator logo This service runs the W3C Markup Validator, v1.2. Copyright © 1994-2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. Reproducible: Always Steps to Reproduce: 1.Compose nonsense message 2.Save it 3.View the source for nonsense. Actual Results: Reported above.
Whiteboard: dupme
cjw, please keep your bug report and testcases etc. apart. Testcases etc. please attach them with "Add an attachment" link at top of bug. Comment 0 is more than hard to read and understand, because of entangled mixture of testcases, logfiles, and your report.
Component: General → Untriaged
cjw, thanks for filing your issue. However, we can't handle your bug report because it has the wrong structure and mixed content. Fwiw, bug format requires: - one issue per report - detailed STR, actual result, expected result No response anyway, and comment 0 is hopeless for disentangling, so whatever the issue might be here, needs new bugs which observe the correct structure.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
(In reply to Thomas D. from comment #2) > cjw, thanks for filing your issue. However, we can't handle your bug report > because it has the wrong structure and mixed content. > > Fwiw, bug format requires: > - one issue per report > - detailed STR, actual result, expected result - and logfiles, testcases, etc. filed separately as attachments to this bug > > No response anyway, and comment 0 is hopeless for disentangling, so whatever > the issue might be here, needs new bugs which observe the correct structure.
You need to log in before you can comment on or make changes to this bug.