- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Wed, 26 May 2010 16:16:42 +0000
- To: Gustavo Ferreira <gustavo.ferreira@hipertipo.net>, www-font <www-font@w3.org>
> -----Original Message----- > From: www-font-request@w3.org [mailto:www-font-request@w3.org] On > Behalf Of Gustavo Ferreira > > (Just trying to understand how this would work.) First, they can't do this today for any type of font today without either doing a view-source or using developer add-ons. Second, browsers do expose add-on APIs allowing anyone to offer this kind of capability for font or other resource types. Thus font vendors could build it today if they so wish. The kind of people who want this info are imo unlikely to be bothered by downloading an add-on or a Firebug plug-in to do this. They are also unlikely to be bothered by a choice of options. If a strictly informational read-only feature is both useful to a tiny fraction of the user population some of the time, and if that feature can already be implemented without the help or involvement of browser vendors, it's unclear to me why this standard or any other needs to mandate it in any normative way.
Received on Wednesday, 26 May 2010 16:18:29 UTC