Many WebIDL interfaces define members that must only be accessed from a secure context.
We do not currently support this attribute, and it is ignored.
The IDL generator should be updated to add checks to ensure that these APIs are unavailable in a non-secure context. This likely involves an audit of all [SecureContext] web apis to make sure that we only define_native_accessor (or other define_native_xyz as applicable) for them when the relevant settings object is a secure context.
In order for this to not cause a mess for our in-tree tests, we'll also need an escape hatch in the Internals object to pretend like we're in a secure context for testing purposes.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too