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 18111 - Its great you introduced a new interface for the TextMetrics, however it would be useful to get a list of fonts that is available to use with .font property. Including web fonts and available system fonts. naming for such property could be availableFonts
Summary: Its great you introduced a new interface for the TextMetrics, however it woul...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:18 UTC by contributor
Modified: 2013-02-22 21:12 UTC (History)
8 users (show)

See Also:

Attachments

Description contributor 2012-07-18 17:18:54 UTC 
This was was cloned from bug 16645 as part of operation convergence.
Originally filed: 2012-04-05 22:54:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-04-05 22:54:51 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#dom-context-2d-font
Multipage: http://www.whatwg.org/C#text-styles
Complete: http://www.whatwg.org/c#text-styles

Comment:
Its great you introduced a new interface for the TextMetrics, however it would
be useful to get a list of fonts that is available to use with .font property.
Including web fonts and available system fonts. naming for such property could
be availableFonts and the array value return could be read only. Such
interface would be useful for providing font pickers in graphical applications
etc. Currently the only existing walk around to this issue is using flash
which isn't very help full when not all devices support it. 

Posted from: 78.73.13.15
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/534.55.3 (KHTML, like Gecko) Version/5.1.5 Safari/534.55.3
================================================================================
Comment 1 Erika Doyle Navara 2012-08-15 23:53:31 UTC 
Moved to HTML Canvas 2D Context.
Comment 2 Jay Munro 2012-08-20 17:20:21 UTC 
This could be very useful. Currently there are also workarounds that instantiate a font for a specific string, checks the TextMetrics measureText, and then decides whether the font exists (http://www.lalit.org/lab/javascript-css-font-detect/) 

assigned to HTML.Next for consideration.
Comment 3 Robin Berjon 2012-09-05 12:36:55 UTC 
Please keep in mind that there are substantial fingerprinting issues with listing system fonts (see http://panopticlick.eff.org/). While I agree that useful ways of manipulating font information would often be great, we have to be careful that this does not make users uniquely identifiable without cookies.
Comment 4 Robin Berjon 2013-01-21 15:57:57 UTC 
Mass move to "HTML WG"
Comment 5 Robin Berjon 2013-01-21 16:00:41 UTC 
Mass move to "HTML WG"
Comment 6 Edward O'Connor 2013-02-22 21:12: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: Rejected
Change Description: No spec change.
Rationale: The fingerprinting costs are substantial, and appear to
outweigh the stated benefits. Please feel free to reopen this bug if you
can provide a method for mitigating the fingerprinting risk.