Consider firing `error` events when blocking mixed content.
https://bugs.webkit.org/show_bug.cgi?id=179116
Summary Consider firing `error` events when blocking mixed content.
Mike West
Reported 2017-11-01 08:46:21 PDT
It appears that WebKit doesn't fire `error` events on media elements (`<audio>`/`<video>`/`<source>`) or `<object>` elements when blocking requests as mixed content. It would be lovely if y'all would consider changing that behavior, as it would bring consistency with Chrome and Firefox, and also make writing regression tests like https://w3c-test.org/mixed-content/ simpler. Thanks!
Attachments
Note You need to log in before you can comment on or make changes to this bug.