Bug 1597207 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I took a closer look at this issue, and here is what I've found,

Given the link `https://yttest.prod.mozaws.net/2019/main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&muted=true#1573735176237`,

1. In Chrome version 78.0.3904.97 (Official Build) (64-bit), all test videos failed to play, and the errors are similar. Take test 3 as an example, the error is in https://bugzilla.mozilla.org/attachment.cgi?id=9110152.

2. In Firefox version 70.0.1 (64-bit), the same error isn't reproducible and most videos can play.

Because the first error says,

```
/2019/main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&muted=true#1574223651753:1 Refused to load media from 'blob:https://yttest.prod.mozaws.net/006bfaa7-c0fc-42a8-aa6a-01c55228cbae' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'media-src' was not explicitly set, so 'default-src' is used as a fallback.
```

I suspect maybe Chrome and Firefox treats "media-src" differently in certain cases. We can set "media-src self;" and see it fixes the issue.

```


```
I took a closer look at this issue, and here is what I've found,

Given the link `https://yttest.prod.mozaws.net/2019/main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&muted=true#1573735176237`,

1. In Chrome version 78.0.3904.97 (Official Build) (64-bit), all test videos failed to play, and the errors are similar. Take test 3 as an example, the error is in https://bugzilla.mozilla.org/attachment.cgi?id=9110152.
2. In Firefox version 70.0.1 (64-bit), the same error isn't reproducible and most videos can play.

Because the first error says,

```
/2019/main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&muted=true#1574223651753:1 Refused to load media from 'blob:https://yttest.prod.mozaws.net/006bfaa7-c0fc-42a8-aa6a-01c55228cbae' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'media-src' was not explicitly set, so 'default-src' is used as a fallback.
```

I suspect maybe Chrome and Firefox treats "media-src" differently in certain cases. We can set "media-src self;" and see it fixes the issue.

Back to Bug 1597207 Comment 1