W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > January to March 2013

RFC: error code strings

From: Simon Stewart <simon.m.stewart@gmail.com>
Date: Thu, 17 Jan 2013 14:56:00 +0000
Message-ID: <CAOrAhYFnyd1tY2XopEk+t+ZEDQ6hwD1F0RHPKJV_Gjs2FKSruQ@mail.gmail.com>
To: public-browser-tools-testing <public-browser-tools-testing@w3.org>

Based on feedback from early drafts, we're moving from status codes being
reported as integers to using strings. I'd appreciate early feedback on the
proposed change to the spec. Notably, I'd like to know whether people
prefer the "lower case with spaces" approach or would prefer "EALLSHOUTY"
or "CamelCasedWithNoSpaces"?



Received on Thursday, 17 January 2013 14:56:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:09:48 UTC