This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14879 - You should remove named numeric constants from interfaces that don't have legacy constraints yet. These probably include some or all of: HTMLTrackElement, TextTrack, NavigatorUserMediaError, MediaStream, PeerConnection, EventSource.
Summary: You should remove named numeric constants from interfaces that don't have leg...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 19:11 UTC by contributor
Modified: 2012-07-18 18:42 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-11-18 19:11:44 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-websocket-interface
Complete: http://www.whatwg.org/c#the-websocket-interface

Comment:
You should remove named numeric constants from interfaces that don't have
legacy constraints yet.  These probably include some or all of:
HTMLTrackElement, TextTrack, NavigatorUserMediaError, MediaStream,
PeerConnection, EventSource.

Posted from: 68.175.61.233
User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.938.0 Safari/535.8
Comment 1 Ian 'Hixie' Hickson 2011-11-18 19:15:54 UTC 
HTMLTrackElement, TextTrack: Are we sure it's worth the inconsistency with HTMLMediaElement?

NavigatorUserMediaError, MediaStream, PeerConnection: Please report these to the WebRTC group.

EventSource: This one is widely implemented.
Comment 2 Aryeh Gregor 2011-11-18 19:24:38 UTC 
(In reply to comment #1)
> HTMLTrackElement, TextTrack: Are we sure it's worth the inconsistency with
> HTMLMediaElement?

Well, the same could be asked of pretty much any new interface, since usually they're comparable to some existing interface or other.  I think it's probably best to just avoid the numeric constant pattern in all new interfaces, but maybe other people have different opinions.  Anne?

> NavigatorUserMediaError, MediaStream, PeerConnection: Please report these to
> the WebRTC group.

Probably not worth my time, since I don't know if they'll agree that it's a bad pattern.

> EventSource: This one is widely implemented.

Okay.
Comment 3 Ian 'Hixie' Hickson 2011-12-08 00:04:55 UTC 
The media ones are closely related to each other, so I think the consistency argument is stronger than with other cases.

In general for new constants that are not clearly ordered (i.e. where it doesn't make sense to compare them with the > operator), I agree.