W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2017

[webrtc-pc] RTCTrackEvent's type parameter

From: Rick Waldron via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Jul 2017 15:44:13 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-241303696-1499442251-sysbot+gh@w3.org>
rwaldron has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCTrackEvent's type parameter ==
I'm trying to understand what the role of the RTCTrackEvent's `type` parameter is, as it's defined: 

Parameter | Type | Nullable | Optional | Description
-- | -- | -- | -- | --
type | DOMString | ✘ | ✘ |  
eventInitDict | RTCTrackEventInit | ✘ | ✘



Questions: 

1. What are the valid values for this parameter? As far as I can tell, there are none. 
    - Run the following in Safari Technology Preview (the only browser I have that supports everything below): 
        ```js
        var pc = new RTCPeerConnection();
        var transceiver = pc.addTransceiver('audio');
        var { receiver, receiver: { track } } = transceiver;

        var trackEvent = new RTCTrackEvent('this is obviously bogus', {
          receiver, track, transceiver
        });

        console.log(trackEvent.type); // 'this is obviously bogus'
        ```    

2. If there are no explicitly defined valid values, or such a thing is not really necessary: can the specification define a default, which also overrides any user input?


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1467 using your GitHub account
Received on Friday, 7 July 2017 15:44:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC