Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Treat blob: URLs as local in the resource selection algorithm (media elements) #550

Closed
wolenetz opened this issue Aug 2, 2016 · 11 comments
Assignees
Milestone

Comments

@wolenetz
Copy link
Member

wolenetz commented Aug 2, 2016

Please port to w3c HTML5.1 the whatwg version of this fix (tracked in whatwg/html#1037, whatwg/html#295, and whatwg/url#126) to help the w3c MSE spec have less of a monkey-patch around fixing w3c/media-source#99 and to reduce potential implementor interop confusion.

This issue is fairly urgent, given the MSE spec timeline (we'd like to do a CfC for entering PR very very soon.)

@plehegar FYI - please help get this issue triaged and acted upon ASAP.
@foolip @annevk FYI

@travisleithead travisleithead self-assigned this Aug 2, 2016
@travisleithead travisleithead added this to the HTML 5.1 CR exit milestone Aug 2, 2016
@travisleithead
Copy link
Member

This has some urgency, setting CR milestone accordingly.

@paulbrucecotton
Copy link

@travisleithead - Can you give the HME WG some idea of when this item will be processed? We are in the final steps of preparing a CfC to take MSE to Proposed Recommendation and MSE ISSUE-99 is currently blocked on this item? If you are not going to process this item this week, please let us know so that we can mitigate the MSE issue in some other way.

@wolenetz
Copy link
Member Author

MSE issue 99 is no longer blocked on this item, but makes assumption that text like what is in whatwg/html#1037 eventually makes it into the w3c html spec.

@grorg
Copy link

grorg commented Aug 18, 2016

Can someone restore @annevk's deleted comment? Or @annevk, can you post it again?

As an implementor, it's important to get the most accurate information. The W3C community should be providing this, no matter the politics or personal feelings involved.

@adanilo
Copy link

adanilo commented Aug 18, 2016

@grorg I don't believe there was any technical detail in Anne's comment that could affect your implementation

@plehegar
Copy link
Member

For what it's worth, the comment was reading:
[[
@wolenetz FYI, as long as you point folks to W3C HTML fork, there will be confusion and issues since it's in a bad state as explained here: https://annevankesteren.nl/2016/01/film-at-11. And has only gotten worse really.
]]

@grorg
Copy link

grorg commented Aug 18, 2016

hi @adanilo!

Obviously this isn't the right place to discuss the politics (nor do I want to), but I think a comment from one of the HTML specification editors (on the WHAT-WG side) pointing out a potential source of confusion is important, even if it isn't completely technical. Deleting it was bad form.

Also, the originator of the issue tagged him.

@grorg
Copy link

grorg commented Aug 18, 2016

Thanks @plehegar!

@plehegar
Copy link
Member

On a different note: the MSE editors decided not to wait for the HTML editors: see w3c/media-source#143 .

@chaals
Copy link
Collaborator

chaals commented Oct 19, 2016

Hopefully assigning the next milestone. @travisleithead, if that's not going to happen can you please change the milestone

@chaals
Copy link
Collaborator

chaals commented Nov 5, 2016

@travisleithead re-scheduled. Please check.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants