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 16937 - Several missing references
Summary: Several missing references
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P4 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: editorial
Depends on:
Blocks:
 
Reported: 2012-05-04 19:48 UTC by Mark Vickers
Modified: 2012-11-02 10:38 UTC (History)
6 users (show)

See Also:


Attachments

Description Mark Vickers 2012-05-04 19:48:30 UTC
(1) Spec mentions GIF, JPEG and PNG, but only has  [PNG] and [JPEG] references. Add a reference to:
	[GIF] Graphics Interchange Format, Version 89a, 1990, Compuserve, http://www.w3.org/Graphics/GIF/spec-gif89a.txt

(2) Section 4.8.11 The canvas element has a direct link to http://dev.w3.org/html5/2dcontext/ in the sentence:
	"The most commonly used primary context is the HTML Canvas 2D Context."

Add a reference to Canvas 2D Context:
	[CANVAS2D] HTML Canvas 2D Context, http://www.w3.org/TR/2dcontext/

(3) Section 4.8.11 The canvas element has two examples mentioning "webgl" context.

Add a reference to WebGL:
	[WEBGL] WebGL Specification, Final Draft (1.0), 27 January 2011, Khronos Group, https://www.khronos.org/registry/webgl/specs/1.0/

(4) Section 2.7.2 Encrypted HTTP and related security concerns mentions HTTP-over-TLS

Add a reference to HTTP-over-TLS:
	[RFC2818] HTTP over TLS, RFC 2818 Informational May 2000

(5) Section 11.3.2 The marquee element says:
	 "The marquee element is a presentational element that animates content. CSS transitions and animations are a more appropriate mechanism."
Ii this is a reference to CSS Animations and CSS Transitions, add references to:
	[CSSANIMATIONS] CSS Animations Module Level 3, http://www.w3.org/TR/css3-animations/
	[CSSTRANSITIONS] CSS Transitions Module Level 3 http://www.w3.org/TR/css3-transitions/
Comment 1 contributor 2012-07-18 07:03:26 UTC
This bug was cloned to create bug 17850 as part of operation convergence.
Comment 2 Silvia Pfeiffer 2012-10-14 12:35:39 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-v2.html

Status: Accepted
Change Description:
https://github.com/w3c/html/commit/dce5cebcbf472f18a024c0a8af602c9b8ffa5361
Rationale: accepted WHATWG change
Comment 3 Mark Vickers 2012-10-16 01:33:05 UTC
(In reply to comment #2)
> Status: Accepted
> Change Description:
> https://github.com/w3c/html/commit/dce5cebcbf472f18a024c0a8af602c9b8ffa5361
> Rationale: accepted WHATWG change

Thanks for making the changes. Accepting the WHATWG change works for all the missing references except for item (2) on the Canvas 2D Context. I am reopening the bug to suggest also adding [CANVAS2D].

In the WHATWG change (bug 17850), the editor rejected adding an external reference to Canvas 2D Context because "This is all one spec." While it is correct that the WHATWG HTML spec includes the Canvas 2d Context in section 4.8.11.1, in the W3C HTML5 spec, Canvas 2d Context is an external spec, so this part of the WHATWG change doesn't work for the W3C spec. The several references to "2D" and "2D Context" in code snippets and text are dangling references.

I suggest that the W3C HTML5 spec needs to add a [CANVAS2D] external reference.

I leave it to the editor to decide where that should go, but one place would be to add and modify a missing sentence from the WHATWG spec section 4.8.11:

"This specification defines the "2d" context below. There is also a specification that defines a "webgl" context. [WEBGL]"

to be something like:

"A specification defines the "2d" context [CANVAS2D]. There is also a specification that defines a "webgl" context. [WEBGL]"

Then the References section could include:

[CANVAS2D] HTML Canvas 2D Context, http://www.w3.org/TR/2dcontext/
Comment 4 Silvia Pfeiffer 2012-10-16 07:30:40 UTC
You are correct - I totally missed that part. Thanks for checking back.
Comment 5 Silvia Pfeiffer 2012-10-21 13:29:09 UTC
I've staged the following commit:
https://github.com/w3c/html/commit/754879cd4f339016ef711319d5e3a9d4fef1f76c

It will be applied with the feature/whatwg_patches_week41_2012 tomorrow.
Comment 6 Silvia Pfeiffer 2012-10-21 22:33:04 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-v2.html

Status: Accepted

Change Description:
https://github.com/w3c/html/commit/754879cd4f339016ef711319d5e3a9d4fef1f76c

Rationale: W3C spec has a separate Canvas 2D Context spec, which this patch references