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 15176 - section.html: "equivalence" of two snippets in example
Summary: section.html: "equivalence" of two snippets in example
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-14 03:28 UTC by Peter Moulder
Modified: 2012-01-28 18:20 UTC (History)
4 users (show)

See Also:


Attachments

Description Peter Moulder 2011-12-14 03:28:51 UTC
[Severity: Only concerns an example rather than normative text.]

Section 4.4.6 (The h1, h2, ... h6 elements):

# These two snippets are equivalent:
#
# [version using only <h1>, <h2> etc. and no <section>]
#
# [version using <section>]

I would not consider the two snippets to be equivalent if they produce different rendering or other behaviour affected by the DOM tree.

If by chance the two snippets, when rendered with a stylesheet h1{color:blue} h2{color:purple} are to result in the same rendering, or if the two snippets are to give the same DOM tree, then I suggest saying so explicitly, as I would find either of those behaviours surprising.

If neither is the case, then I believe the text should be corrected, perhaps changed to "have the same semantics" or "are semantically identical" (which is the language used in section 4.4.11).

Consider also adding (either here or in section 4.4.11) something that reminds authors that the two are not entirely equivalent, e.g. mentioning that stylesheet considerations might favour one of the two over the other, or adding parenthetically that the two snippets might nevertheless be rendered differently with some stylesheets.  Such a hint might be most valuable in author view, but it has some use even to casual implementors given that people treat a spec as a reference and read it out of context.  (Out of context of the HTML spec, the "semantics" of a piece of input to a program might be taken to encompass all of the functional effects of that input on the program, which would include rendering in the case of an HTML-rendering program.)
Comment 1 Ian 'Hixie' Hickson 2012-01-28 18:18:56 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 2 contributor 2012-01-28 18:20:49 UTC
Checked in as WHATWG revision r6927.
Check-in comment: Clarify example text.
http://html5.org/tools/web-apps-tracker?from=6926&to=6927