Should office-addin-dev-certs work for browsers?

The stackoverflow tag linked on https://github.com/OfficeDev/Office-Addin-Scripts is completely empty, so please allow me to ask a question here:

Should the certificate that gets created by office-addin-dev-certs be accepted by browsers, so that I can use it for general web app development?
Or is it only suitable for the specific use case of outlook loading its add-in?

I tried to use it as certificate when starting my app with parcel and when trying to open https://localhost:3000/ Firefox says SSL_ERROR_RX_RECORD_TOO_LONG while Chrome and Edge report ERR_SSL_PROTOCOL_ERROR :-(
As far as I understood the certificate is issued for "localhost" and "127.0.0.1" and should not be restricted to a specific port, right?

Would be so cool to have locally created certificates automatically be accepted in the browser while developing!

Start with the office-addin-dev-certs behavior described in the issue and compare it with the Parcel setup at https://localhost:3000. Reproduce the Firefox SSL_ERROR_RX_RECORD_TOO_LONG and Chrome/Edge ERR_SSL_PROTOCOL_ERROR reports, then determine whether the generated certificate is intended for general browser use or only Outlook add-ins.