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 22023 - Cryptic paragraph about marking privacy issues
Summary: Cryptic paragraph about marking privacy issues
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: CR
Depends on:
Blocks:
 
Reported: 2013-05-13 20:04 UTC by Jukka K. Korpela
Modified: 2013-08-08 21:36 UTC (History)
4 users (show)

See Also:


Attachments

Description Jukka K. Korpela 2013-05-13 20:04:59 UTC
In 1.8 Privacy concerns, there is the following paragraph near the end: “Features in this specification which can be used to fingerprint the user are marked as this paragraph is.” However, that paragraph has no special styling or marker.

In the corresponding clause (1.10) in the WHATWG HTML document, the paragraph contains an image at the end, floated to the right, with the odd alt attribute value "(This is a fingerprinting vector.)" ("This is a privacy issue" would seem more adequate.) Apparently, the image has been dropped in HTML5 CR, making the paragraph pointless.

It is unclear whether the WHATWG HTML document actually uses the image somewhere. It might be just an idea that was not implemented.

The minimal change is to remove the paragraph. But for informativeness, and to make section 1.8 more meaningful, it would be desirable to link to those items in the specification where privacy (or “fingerprinting”) is an issue and/or mark those items somehow and link to section 1.8.
Comment 1 Robin Berjon 2013-07-15 12:14:58 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: Fixed a problem with the publication toolchain that wasn't interpolating variables in spec body.
Rationale: It was simply a software bug.

https://github.com/w3c/html-tools/commit/7c833451b29206a74506e3dae66835cf6e18fc2f
Comment 2 Jukka K. Korpela 2013-07-21 11:45:33 UTC
As far as I can see, the bug has not been fixed in the July 15 version of HTML 5.1 Nightly.
Comment 3 Michael[tm] Smith 2013-07-21 12:59:09 UTC
(In reply to comment #2)
> As far as I can see, the bug has not been fixed in the July 15 version of
> HTML 5.1 Nightly.

The script that generates the Nightly is failing right now for some reason. I'll try to get it fixed in the next couple of days.
Comment 4 Travis Leithead [MSFT] 2013-08-08 21:36:18 UTC
I've verified the latest Nightly and recently re-published CR of HTML5.0, and the fingerprinting marker appears to be working properly on the sections for which it is annotated.

Example in latest CR: http://www.w3.org/TR/html5/webappapis.html#enabling-and-disabling-scripting

Example in 5.1 Nightly: http://www.w3.org/html/wg/drafts/html/master/introduction.html#fingerprint

Thanks!