We want to expose decoding errors to the users, and encourage them to report these errors as site issues to webcompat.com. While (we hope) most of these issues will come from invalid resources that site owners should fix, we may also catch genuine issues in Firefox code or its dependent platform-specific libraries. The implementation will be done in dependent bugs. Some side-features will also be added to help with media-playback work, e.g.: Report issues due to demuxing/decoding mismatch between C++ and Rust code.

https://github.com/webcompat/webcompat.com/issues/1356 tracks the changes to webcompat.com, which will allow our code to provide extra information to the website.

Note: The current "Report Site Issue" feature (bug 1306114) is only available on the Nightly channel, and just about to be enabled on Dev Edition (see bug 1341438). There are some privacy issues to be considered (as well as volume of reports to webcompat), that may not make this feature suitable for the release channel, unless we get legal green light (e.g.: Proper mentions in the official Mozilla privacy policy). So I will look at how the "Report Site Issue" feature is constrained (probably by build configuration and/or preferences) and follow the same practices.

(In reply to Gerald Squelart [:gerald] from comment #2) > Note: The current "Report Site Issue" feature (bug 1306114) is only > available on the Nightly channel, and just about to be enabled on Dev > Edition (see bug 1341438). > > There are some privacy issues to be considered (as well as volume of reports > to webcompat), that may not make this feature suitable for the release > channel, unless we get legal green light (e.g.: Proper mentions in the > official Mozilla privacy policy). I think this is a great feature for pre-release channels, but I'm dubious about exposing it to Release users in its current form... I just had this notification bar randomly pop up in Slack, with no obvious ill-effect. Which makes me wonder if this is prone to triggering in cases that don't really matter. We should have a suitably high bar when interrupting the user and asking them to perform some action. Do we expect this to be a very rare condition by the time it would be available on Release? The UX of the current webpage for submitting an issue should also be improved before considering exposing this to Release users -- it's too technical, asks for a lot of choices/input, and steering such users to "Report via Github" (which then either prompts for authentication or permissions) is pretty bad.