W3C home > Mailing lists > Public > public-html@w3.org > April 2013

Re: Week 14/15: Staged WHATWG patches for HTML5.1

From: Glenn Adams <glenn@skynav.com>
Date: Wed, 17 Apr 2013 23:24:01 -0600
Message-ID: <CACQ=j+cNU-mAi9U3ts7UVDFde3AgVKazKb-CvO7Ak_YE11TTLA@mail.gmail.com>
To: Rik Cabanier <cabanier@adobe.com>
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, public-html <public-html@w3.org>
Historically speaking, there has been a trend away from using enumerated
types, e.g., DOMError, to using DOMString. This change looks like it's
headed in the other direction, which I find surprising.

In general, it has been my experience that use of enums in standards APIs
is harder to evolve than using string arguments.


On Wed, Apr 17, 2013 at 10:32 PM, Rik Cabanier <cabanier@adobe.com> wrote:

> There’s trend to use enumerations now that Web IDL is getting better
> support.****
>
> Browsers can simply write IDL and the validation is done automatically. In
> the past, they had to write string compare routines which is more work and
> prone to bugs.****
>
> ** **
>
> What is your issue with them? Enums can always be extended or deprecated.*
> ***
>
> ** **
>
> Rik****
>
> ** **
>
> *From:* Glenn Adams [mailto:glenn@skynav.com]
> *Sent:* Wednesday, April 17, 2013 7:37 PM
> *To:* Silvia Pfeiffer
> *Cc:* public-html
> *Subject:* Re: Week 14/15: Staged WHATWG patches for HTML5.1****
>
> ** **
>
> ** **
>
> On Wed, Apr 17, 2013 at 8:24 PM, Silvia Pfeiffer <
> silviapfeiffer1@gmail.com> wrote:****
>
> * Introduce TextTrackKind and add more IDL support to TextTrack API. (7808)
> ****
>
> https://github.com/w3c/html/commit/9683aedef55f016ff5ebe44fe5c942604774c840
> ****
>
> ** **
>
> What is the motivation for changing text track kind from a DOMString to an
> enumerated type? Enumerated types are much harder to evolve/maintain. This
> seems like a bad idea.****
>
> ** **
>
Received on Thursday, 18 April 2013 05:24:48 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:32 UTC