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 14748 - inconsistent treatment of transitive dependencies - typed arrays
Summary: inconsistent treatment of transitive dependencies - typed arrays
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 23:37 UTC by Glenn Adams
Modified: 2013-03-08 22:30 UTC (History)
6 users (show)

See Also:


Attachments

Description Glenn Adams 2011-11-09 23:37:45 UTC
In Section 2.2.2 Dependencies [1] there appears:

<blockquote>
Typed Arrays

The ArrayBuffer interface and underlying concepts from the Typed Array Specification are used for several features in this specification. The Uint8ClampedArray interface type is specifically used in the definition of the canvas element's 2D API. [TYPEDARRAY]
</blockquote>

However, the canvas element's 2D API is not specified in the HTML5 specification, and, as a consequence, no normative use of [TYPEDARRAY] applies in the spec.

[1] http://dev.w3.org/html5/spec/Overview.html#dependencies

Given that the editor has previously declined to list 2nd or Nth order dependencies, e.g., see bug 14213 comment 3 [2]), this dependency for [TYPEDARRAY] should be removed. Furthermore, it should be removed from the References section [3], since no other reference is made to [TYPEDARRAY] in the spec.

[2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=14213#c3
[3] http://dev.w3.org/html5/spec/Overview.html#references
Comment 1 Glenn Adams 2011-12-10 00:10:49 UTC
you can't resolve as WONTFIX without some explanation

this bug report is noting that there is a normative reference to [TYPEDARRAY] but there is no use of this this in the body of the text;

it is not appropriate to include a reference to which nothing refers

the correct response is to remove the reference to [TYPEDARRAY] from the references section and also to remove the paragraph cited below under 2.2.2 that refers to the Canvas 2D APIs use of this reference
Comment 2 Travis Leithead [MSFT] 2013-03-08 22:30:13 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: No spec change
Rationale:

Since the time of the publishing of this bug, the spec has since added another dependency on having the [TYPEDARRAY] reference: Transferables (Section 2.7.4.) which notes that ArrayBuffer is one of the supported Transferrable types.

I think this justifies having the reference in the spec. As such, resolving this bug as WorksForMe.