- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jun 2017 16:14:01 +0000
- To: public-media-capture-logs@w3.org
Well, the most web compatible would of course be changing the spec to match Chrome and Firefox. Clearly some code would break from this, the question is how much code would break. For instance, my own [fiddle](http://jsfiddle.net/jib1/tmwLxjLy/) should work, except I apparently do this for debug reasons: ```js rec.start(); log(rec.state + " for "+ (ms / 1000) +" seconds..."); // recording for 5 seconds ``` which would now say "inactive for 5 seconds" 😜 Sure that's probably unusual, but why did I do this? Probably a form of defensive programming, to get feedback and catch bugs early. I could see others writing JS defensively, not exactly like this, but using assert-like throws to catch the runtime deviating at all from the expectations the developer clung to when the wrote their code. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/123#issuecomment-308790842 using your GitHub account
Received on Thursday, 15 June 2017 16:14:08 UTC