This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6252 - Un-enclosed <IMG> tag not detected on direct input
Summary: Un-enclosed <IMG> tag not detected on direct input
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: PC Windows 2000
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2008-11-27 19:00 UTC by Chris Winter
Modified: 2008-12-08 18:09 UTC (History)
1 user (show)

See Also:


Description Chris Winter 2008-11-27 19:00:46 UTC
Recently I began validating HTML 4.0 Strict pages by direct input, as opposed to uploading them and then checking by URI.

Several files were passed as clean on direct input. But the same files, once installed on my Web site, failed validation by URI with a single error: <IMG> tag not enclosed in a block element.

The actual error message is: "document type does not allow element "IMG" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "DIV", "ADDRESS" start-tag."

It seems to me that this is the sort of error that should be picked up by the validator no matter which input method is used.

Searching did not disclose any previous instance of this bug.

I've since fixed the problem in the on-line files. If you need a test case, let me know and I'll re-create it.
Comment 1 Olivier Thereaux 2008-11-27 19:04:50 UTC
A test case would be welcome indeed.

Thank you!
Comment 2 Olivier Thereaux 2008-12-04 16:19:55 UTC
[after receiving a test case by private mail]

passing this page directly to the validator and passing it by copy-pasting the source into the "direct input" validation gives me exactly the same result. 

I'm suspecting the source code you sent to the validator by "direct input" and "by URI" may have been different. Use the "view source" option of the validator to see what the difference may be.
Comment 3 Chris Winter 2008-12-08 18:09:12 UTC
I found the same thing when I tried my test case -- that is, direct input gave the same error as check by URI. I guess this bug is invalid.

But it is puzzling, because the problem arose when I found several other errors in the original HTML file by direct input, fixed those, got it to validate, uploaded it, and then saw the error message I reported here.

Ah, I see I can invalidate the bug myself. I'll do that thing.