Add [SecureContext] to derived interfaces

[anssiko]

[This is a meta issue to track changes to the interfaces that inherit from Sensor.]

All concrete sensors https://www.w3.org/2009/dap/#sensors that inherit from Sensor are only available within a secure context, since they implement https://w3c.github.io/sensors/#mitigation-strategies.

However, the WebIDL spec states the following:

An interface without the [SecureContext] extended attribute must not inherit from another interface that does specify [SecureContext].

To fix this, the [SecureContext] extended attribute must be added to the following derived interfaces:

• AmbientLightSensor
• ProximitySensor
• Accelerometer LinearAccelerationSensor GravitySensor
• Magnetometer UncalibratedMagnetometer
• Gyroscope
• OrientationSensor AbsoluteOrientationSensor RelativeOrientationSensor
• GeolocationSensor

The IDL guidance to concrete spec authors https://w3c.github.io/sensors/#example-webidl does include the [SecureContext] extended attribute already, so we're covered on that part. Perhaps worth looking that the prose in that section is aligned.

Raised by @foolip in https://github.com/WICG/geolocation-sensor/issues/8

[anssiko]

All changes to the derived interfaces have been landed. Thanks everyone who contributed and @foolip for bringing this issue to our attention.

In addition to the IDL changes to the derived interfaces, I revisited the Generic Sensor API prose that talks about secure context and concluded no change are needed. Per WebIDL any derived interface must use [SecureContext] and the example IDL in https://w3c.github.io/sensors/#example-webidl makes that clear. The informative section https://w3c.github.io/sensors/#secure-context gives further context.

We can now close this meta issue.

[foolip]

That was quick, thanks!

[rakuco]

Somewhat related: https://w3c.github.io/sensors/#construct-sensor-object says

If the current settings object is not a secure context, then:

• Throw a SecurityError DOMException.

Is that still necessary, given Sensor and its derived interfaces all have the [SecureContext] extended attribute? IOW, there should be no situation where we'd reach the point where we're constructing a sensor object outside a secure context.

[pozdnyakov]

@rakuco pls see #314

[rakuco]

@rakuco pls see #314

Awesome, thanks!