- From: Anton Vayvod via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Sep 2016 11:00:10 +0000
- To: public-secondscreen@w3.org
And last but not least, the events that can fire. The rule of thumb is whether the corresponding attributes like `readyState` and `networkState` are supported and can take the corresponding values. `loadstart` MAY be supported. `progress` MAY be supported. `suspend` MAY be supported. `abort` MAY be supported. `error` MUST be supported. `emptied` MAY be supported. `loadedmetadata` MAY be supported. `loadeddata` MAY be supported. `canplay` MAY be supported. `canplaythrough` MAY be supported. `playing` MUST be supported. `waiting` MAY be supported. `seeking` MUST be supported. `seeked` MUST be supported. `ended` MUST be supported. `durationchange` MUST be implemented. `timeupdate` MUST be implemented. `play` MUST be implemented. `pause` MUST be implemented. `ratechange` MAY be implemented. `resize` MAY be implemented. `volumechange` MAY be implemented. -- GitHub Notification of comment by avayvod Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/41#issuecomment-248870416 using your GitHub account
Received on Thursday, 22 September 2016 11:00:24 UTC