- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 1 Apr 2014 10:16:44 -0700
- To: Greg Whitworth <gwhit@microsoft.com>
- Cc: John Daggett <jdaggett@mozilla.com>, "www-style@w3.org" <www-style@w3.org>
On Tue, Apr 1, 2014 at 10:00 AM, Greg Whitworth <gwhit@microsoft.com> wrote: >> 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. The proposals can > be found here and here. > > 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. Until you implement canvas-in-workers, a worker's .fonts property doesn't do anything useful anyway, so you can just skip implementing that part until later. ~TJ
Received on Tuesday, 1 April 2014 17:17:31 UTC