{"action":"created","issue":{"url":"https://api.github.com/repos/google/shaka-player/issues/627","repository_url":"https://api.github.com/repos/google/shaka-player","labels_url":"https://api.github.com/repos/google/shaka-player/issues/627/labels{/name}","comments_url":"https://api.github.com/repos/google/shaka-player/issues/627/comments","events_url":"https://api.github.com/repos/google/shaka-player/issues/627/events","html_url":"https://github.com/google/shaka-player/issues/627","id":194601389,"number":627,"title":"Shaka v1.6.4 problem in playing in FireFox","user":{"login":"MegaLabs1","id":2102317,"avatar_url":"https://avatars.githubusercontent.com/u/2102317?v=3","gravatar_id":"","url":"https://api.github.com/users/MegaLabs1","html_url":"https://github.com/MegaLabs1","followers_url":"https://api.github.com/users/MegaLabs1/followers","following_url":"https://api.github.com/users/MegaLabs1/following{/other_user}","gists_url":"https://api.github.com/users/MegaLabs1/gists{/gist_id}","starred_url":"https://api.github.com/users/MegaLabs1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MegaLabs1/subscriptions","organizations_url":"https://api.github.com/users/MegaLabs1/orgs","repos_url":"https://api.github.com/users/MegaLabs1/repos","events_url":"https://api.github.com/users/MegaLabs1/events{/privacy}","received_events_url":"https://api.github.com/users/MegaLabs1/received_events","type":"User","site_admin":false},"labels":[{"id":500271770,"url":"https://api.github.com/repos/google/shaka-player/labels/bad%20content","name":"bad content","color":"666666","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-12-09T13:51:35Z","updated_at":"2016-12-22T20:53:35Z","closed_at":null,"body":"Hi, colleagues.\r\nWe're testing Shaka v.1.6.4 playing encrypted live content in FireFox 50. We faced a problem: several HD manifests are not playing in FireFox browser in shaka. Browser devtools show, that networking stops after receiving init-chanks. Looks like shaka receives init-chanks and stops. The same manifest is playing in Chrome without problems. Also we have manifests with identical parameters, which are playing in both Chrome and Firefox without problems. Do you have any ideas about this issue?"},"comment":{"url":"https://api.github.com/repos/google/shaka-player/issues/comments/268888273","html_url":"https://github.com/google/shaka-player/issues/627#issuecomment-268888273","issue_url":"https://api.github.com/repos/google/shaka-player/issues/627","id":268888273,"user":{"login":"joeyparrish","id":6843156,"avatar_url":"https://avatars.githubusercontent.com/u/6843156?v=3","gravatar_id":"","url":"https://api.github.com/users/joeyparrish","html_url":"https://github.com/joeyparrish","followers_url":"https://api.github.com/users/joeyparrish/followers","following_url":"https://api.github.com/users/joeyparrish/following{/other_user}","gists_url":"https://api.github.com/users/joeyparrish/gists{/gist_id}","starred_url":"https://api.github.com/users/joeyparrish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joeyparrish/subscriptions","organizations_url":"https://api.github.com/users/joeyparrish/orgs","repos_url":"https://api.github.com/users/joeyparrish/repos","events_url":"https://api.github.com/users/joeyparrish/events{/privacy}","received_events_url":"https://api.github.com/users/joeyparrish/received_events","type":"User","site_admin":false},"created_at":"2016-12-22T20:53:35Z","updated_at":"2016-12-22T20:53:35Z","body":"Changing availabilityStartTime is not valid, therefore this is broken content.  Shaka v1 went through a lot of effort to fix certain bad content.  This is why your other manifest works in v1.6.4.\r\n\r\nWe no longer try to guess what the manifest *should* say.  Now, we play based on what it *does* say.\r\n\r\nWe are a very small team.  We do not have the resources to support broken content, and we will not be putting any more effort into Shaka v1.\r\n\r\nCheck to see if your encoder has an update.  Perhaps they have already fixed that bug.  If not, please file a ticket with the encoder vendor.  Feel free to reference this discussion or add me to the conversation to help explain to the encoder vendor why this is broken."}}
{"actor":{"display_login":"joeyparrish"}}