[Tracking Requested - why for this release]: Not too late to fix these events before they hit 65. (In reply to Boris Zbarsky [:bzbarsky, bz on IRC] from comment #2) > Anyway, the right thing here is to actually implement the spec. If the spec > is going to change too, we can track that change, but that's just going to > affect when the state change happens, not when the events are fired. (as discussed on irc) I don't think we should change when the state changes at this point, to avoid webcompat breakage. I'll write a PR for https://github.com/w3c/mediacapture-record/issues/123 to fix the spec (change state sync but fire the event async).
Bug 1514016 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
[Tracking Requested - why for this release]: Not too late to fix these events before 65 hits release. (In reply to Boris Zbarsky [:bzbarsky, bz on IRC] from comment #2) > Anyway, the right thing here is to actually implement the spec. If the spec > is going to change too, we can track that change, but that's just going to > affect when the state change happens, not when the events are fired. (as discussed on irc) I don't think we should change when the state changes at this point, to avoid webcompat breakage. I'll write a PR for https://github.com/w3c/mediacapture-record/issues/123 to fix the spec (change state sync but fire the event async).