W3C home > Mailing lists > Public > www-style@w3.org > May 2015

Re: [css-font-loading] load, check and testing for character coverage

From: Florian Rivoal <florian@rivoal.net>
Date: Thu, 28 May 2015 11:41:17 +0200
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-Id: <DDF267CF-4132-44EF-B75C-6FBE084E8E0C@rivoal.net>
To: John Daggett <jdaggett@mozilla.com>

> On 28 May 2015, at 09:49, John Daggett <jdaggett@mozilla.com> wrote:
> 
> I feel like we're playing a rerun of XML vs. HTML error handling. Your
> view is the XML view, "this is not right, bad you", errors should be
> returned. What I'm saying is the HTML view, "this is not right but we'll
> deal with it", no errors other than maybe a warning in the dev console
> if that's appropriate.

Except you can't catch the exception when XML parsing fails, but in js you
can, so I don't think parse errors for declarative languages should be used
as a model for API design.

 - Florian
Received on Thursday, 28 May 2015 09:41:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:54 UTC