W3C home > Mailing lists > Public > www-style@w3.org > April 2014

[css-font-loading] RE: Discussion about font-loading

From: Greg Whitworth <gwhit@microsoft.com>
Date: Tue, 1 Apr 2014 17:00:00 +0000
To: John Daggett <jdaggett@mozilla.com>
CC: Tab Atkins Jr. <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <44785e72a39545a68f8f750a0ba53569@DM2PR03MB400.namprd03.prod.outlook.com>
> Hi Greg,
> Did you get a chance to discuss this with others on the IE team? Are there issues you want to raise or questions?
> Cheers,
> John

Hi John!

Sorry, I got some clarification on the DOM access piece and I should have been more specific about the worker's access. We all agree that the spec isn't about giving DOM access, just fonts for the purpose of working with canvas, however, the previous point still stands: there's still debate about the architecture and method for sharing canvas contexts with workers, Ian mentions competing proposals awaiting implementation here<http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/0971.html>. The proposals can be found here<http://wiki.whatwg.org/wiki/CanvasInWorkers> and here<http://wiki.whatwg.org/wiki/WorkerCanvas>.

Given the current state-of-flux we don't think it's a good idea to marry the font-loading spec so closely with canvas & workers. There's value in font loading APIs for font foundries and apps today. We feel it would make more sense to provide that value sooner and follow up with workers in an L2 spec.
If we have any other feedback we'll let you know; otherwise we'll likely wait to invest heavily in this area until the canvas and worker issue is resolved in the HTML WG.

Thanks,

Greg

Received on Tuesday, 1 April 2014 17:00:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:20 UTC