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 20624 - Should the html in the example not be lowercased, and is it a good idea to mix block-level and inline content such as the h1 and img in the header?
Summary: Should the html in the example not be lowercased, and is it a good idea to mi...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-09 23:44 UTC by contributor
Modified: 2013-03-07 23:07 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-01-09 23:44:44 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-map-element.html
Multipage: http://www.whatwg.org/C#the-map-element
Complete: http://www.whatwg.org/c#the-map-element

Comment:
Should the html in the example not be lowercased, and is it a good idea to mix
block-level and inline content such as the h1 and img in the header?

Posted from: 82.173.180.157
User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 Safari/537.11
Comment 1 Ian 'Hixie' Hickson 2013-03-07 23:07:27 UTC 
(Please file one issue per bug.)

1) Regard the case of the markup, no, uppercase tags are equally valid.

2) HTML doesn't have "block-level" and "inline" content any more. They're both flow content, <img> is also phrasing content. (See http://whatwg.org/html#kinds-of-content for details.) There's nothing wrong with the markup as written as far as this goes. (See http://whatwg.org/html#paragraphs for more details.)