cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mrblue6
New member
Status: In development

I usually use firefox to develop my website and then move it over to chrome.
I noticed this issue with Firefox.
It does not give a detailed enough error message to properly debug the issue.

Most websites will have quite a few script/link tags, so it is very tedious to manually check the hash of each one.

In chrome, it simply gives you the URL for the resource that failed the hash check.
Firefox should update this to give some more details (ie. the path).

In firefox:
" None of the “sha512” hashes in the integrity attribute match the content of the subresource. The computed hash is “..."      app_name"

In chrome:
Failed to find a valid digest in the 'integrity' attribute for resource 'url_to_file' with computed SHA-512 integrity '...'. The resource has been blocked.      app_name

4 Comments
Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

Honza
Employee
Employee

Sorry for the delay. I like the idea and I reported this as an enhancement request in our bug tracker
https://bugzilla.mozilla.org/show_bug.cgi?id=1938307

Thank you!

Honza

freddyb
Employee
Employee

...and we have an approved patch (see bugzilla issue above). This change will hopefully land in Firefox 136 (to be released early March 2025).

Thanks for reaching out to us @mrblue6 (and thank you for relaying this to the team to @Honza  and for fixing the bug to Tom Schuster!)

Status changed to: In development
Jon
Community Manager
Community Manager

Good news...

This is being worked on, and we're aiming to deliver it in Firefox 136—see @freddyb's recent comment in the thread for more details. 

As always, thanks for your role in pushing this work forward 🙌