Re: MSE V1Editorial issues

PR #132 (for #98) is ready for review.
I'll update VPQ details (#69), then begin work on #99 and triaging #124.

That leaves:

   - #110: IMHO, not blocking V1. Ok by me if not fixed in V1. Mark/Jerry:
   agreed?
   - #104: IMHO, not blocking V1. Ok by me if not fixed in V1. Mark/Jerry:
   agreed?
   - Mark's PR#127 (for #83) needs review comments addressed. Mark, can you
   please provide an ETA?
   - #74 (Pending Phillippe). Is this required prior to PR CfC on Aug 2?
   This seems at risk, if so.
   - #48 (Assigned to Jerry): Jerry, can you please provide an ETA?
   - #45 (Assigned to Jerry): Jerry, can you please provide an ETA?

Matt





On Wed, Jul 27, 2016 at 12:02 PM, Matt Wolenetz <wolenetz@google.com> wrote:

> Update:
>
> With Mark's clarification, #128 (for #93) LGTM (% merging and regenerating
> index.html).
>
> I just did a quick (with no review) merge of #131 (for #130) since it
> seems benign.
>
> Mark's PR #127 (for #83) will need potentially significant work. To let
> him focus on that, and to help Jerry, too, I'll take a look at fixing #99
> and #98 shortly.
>
> On Tue, Jul 26, 2016 at 4:42 PM, Matt Wolenetz <wolenetz@google.com>
> wrote:
>
>> PR#128 (for issue #93): I posted a question since this bit of HTML5->5.1
>> is unclear to me and I want to make sure that we don't leak cross-origin
>> MediaSource stuff (e.g. a malicious canvas origin shouldn't be able to
>> scrape media from an MSE HTMLMediaElement from a different origin).
>>
>> On Tue, Jul 26, 2016 at 4:08 PM, Matt Wolenetz <wolenetz@google.com>
>> wrote:
>>
>>> PR#127 (for issue #83) needs some fixing. I've commented on the PR (type
>>> links are missing where they had been included previously)
>>>
>>> On Tue, Jul 26, 2016 at 2:33 PM, Paul Cotton <Paul.Cotton@microsoft.com>
>>> wrote:
>>>
>>>> I am not sure about Philippe’s availability.  I included his item for
>>>> completeness.
>>>>
>>>>
>>>>
>>>> Sent from my Windows 10 phone
>>>>
>>>>
>>>>
>>>> *From: *Matt Wolenetz <wolenetz@google.com>
>>>> *Sent: *July 26, 2016 14:26
>>>> *To: *Jerry Smith (WPT) <jdsmith@microsoft.com>
>>>> *Cc: *Paul Cotton <Paul.Cotton@microsoft.com>;
>>>> public-hme-editors@w3.org
>>>>
>>>> *Subject: *Re: MSE V1Editorial issues
>>>>
>>>>
>>>> Regarding Philippe's issue #74, is he available this week to work on it?
>>>>
>>>> On Tue, Jul 26, 2016 at 2:25 PM, Matt Wolenetz <wolenetz@google.com>
>>>> wrote:
>>>>
>>>>> I've just produced a PR to fix #126, and will review mwatson's PRs
>>>>> shortly (and report VPQ details in that V1 issue, too).
>>>>>
>>>>> On Tue, Jul 26, 2016 at 10:45 AM, Jerry Smith (WPT) <
>>>>> jdsmith@microsoft.com> wrote:
>>>>>
>>>>>> Also, PR #127 is technically fine, but would benefit from some manual
>>>>>> cleanup around the IDL entries.  They render fine, but aren’t very readable
>>>>>> when editing (or reviewing changes).
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jerry
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Jerry Smith (WPT)
>>>>>> *Sent:* Tuesday, July 26, 2016 10:42 AM
>>>>>> *To:* Paul Cotton <Paul.Cotton@microsoft.com>; Matthew Wolenetz <
>>>>>> wolenetz@google.com> (wolenetz@google.com) <wolenetz@google.com>
>>>>>> *Cc:* public-hme-editors@w3.org
>>>>>> *Subject:* RE: MSE V1Editorial issues
>>>>>>
>>>>>>
>>>>>>
>>>>>> PR #128 LGTM, but lacks a revision history entry.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Issue #126 (https://github.com/w3c/media-source/issues/126) from
>>>>>> Matt asks if we should continue to maintain the history.  Most W3C specs do
>>>>>> not seem to do so.  Web Audio has a link to a log from GitHub and I think
>>>>>> Mercurial.  That seems useful, though I’m not sure how much we want to
>>>>>> invest in recovering the old history.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jerry
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Paul Cotton
>>>>>> *Sent:* Tuesday, July 26, 2016 8:14 AM
>>>>>> *To:* Jerry Smith (WPT) <jdsmith@microsoft.com>; Matthew Wolenetz <
>>>>>> wolenetz@google.com> (wolenetz@google.com) <wolenetz@google.com>
>>>>>> *Cc:* public-hme-editors@w3.org
>>>>>> *Subject:* RE: MSE V1Editorial issues
>>>>>>
>>>>>>
>>>>>>
>>>>>> > I believe I still have outstanding PRs on the spec which require
>>>>>> review. I'll return to editing when those two things are done.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jerry, Matt:  Can you please check on Mark’s two PRs ASAP?
>>>>>>
>>>>>> https://github.com/w3c/media-source/pull/128 for ISSUE-93
>>>>>>
>>>>>> https://github.com/w3c/media-source/pull/127 for ISSUE-83
>>>>>>
>>>>>>
>>>>>>
>>>>>> /paulc
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Mark Watson [mailto:watsonm@netflix.com <watsonm@netflix.com>]
>>>>>>
>>>>>> *Sent:* Tuesday, July 26, 2016 11:12 AM
>>>>>> *To:* Paul Cotton <Paul.Cotton@microsoft.com>
>>>>>> *Cc:* Jerry Smith (WPT) <jdsmith@microsoft.com>; Philippe Le Hegaret
>>>>>> (plh@w3.org) <plh@w3.org>; public-hme-editors@w3.org
>>>>>> *Subject:* Re: MSE V1Editorial issues
>>>>>>
>>>>>>
>>>>>>
>>>>>> I am prioritizing work on the tests. I believe I still have
>>>>>> outstanding PRs on the spec which require review. I'll return to editing
>>>>>> when those two things are done.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ...Mark
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>
>>>>>> On Jul 26, 2016, at 8:03 AM, Paul Cotton <Paul.Cotton@microsoft.com>
>>>>>> wrote:
>>>>>>
>>>>>> We still have 7 V1Editorial issues to resolve.  Are these issues
>>>>>> going to be dealt with THIS week?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Mark:
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/99
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/93
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/83
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jerry:
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/98
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/48
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/45
>>>>>>
>>>>>>
>>>>>>
>>>>>> Philippe:
>>>>>>
>>>>>> https://github.com/w3c/media-source/issues/74
>>>>>>
>>>>>>
>>>>>>
>>>>>> /paulc
>>>>>>
>>>>>>
>>>>>>
>>>>>> Paul Cotton, Microsoft Canada
>>>>>>
>>>>>> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>>>>>>
>>>>>> Tel: (425) 705-9596 Fax: (425) 936-7329
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>