All web platform features requiring a secure context should be so marked in the BCD
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
I recently discovered that service workers BCD does not list the requirements for secure context even though it is required by the spec. Consequently this requirement does not appear on the interface's MDN page or in any of the other clients for this data set.
I'll fix this for service workers, but we should investigate this for all specs. I've generated a list of interfaces from Chrome's IDL. Our interface set is probably larger than other browsers but I don't assume it contains everything.
- AbsoluteOrientationSensor
- Accelerometer
- AmbientLightSensor
- ApplicationCache
- ApplicationCacheErrorEvent
- AudioWorklet
- AuthenticatorAssertionResponse
- AuthenticatorAttestationResponse
- AuthenticatorResponse
- BarcodeDetector
- Bluetooth
- BluetoothAdvertisingEvent
- BluetoothCharacteristicProperties
- BluetoothDevice
- BluetoothLEScan
- BluetoothManufacturerDataMap
- BluetoothRemoteGATTCharacteristic
- BluetoothRemoteGATTDescriptor
- BluetoothRemoteGATTServer
- BluetoothRemoteGATTService
- BluetoothServiceDataMap
- Cache
- CacheStorage
- Clipboard
- ContactsManager
- CookieChangeEvent
- CookieStore
- Credential
- CredentialsContainer
- DetectedBarcode
- DetectedFace
- DetectedText
- DeviceMotionEvent
- DeviceMotionEventAcceleration
- DeviceMotionEventRotationRate
- DeviceOrientationEvent
- FaceDetector
- FederatedCredential
- FileSystemDirectoryHandle
- FileSystemFileHandle
- FileSystemHandle
- FileSystemWriter
- Gyroscope
- HID
- HIDCollectionInfo
- HIDConnectionEvent
- HIDDevice
- HIDInputReportEvent
- HIDReportInfo
- HIDReportItem
- IdleDetector
- IdleState
- Keyboard
- KeyboardLayoutMap
- LinearAccelerationSensor
- Lock
- LockManager
- MIDIAccess
- MIDIConnectionEvent
- MIDIInput
- MIDIInputMap
- MIDIMessageEvent
- MIDIOutput
- MIDIOutputMap
- MIDIPort
- Magnetometer
- MediaDeviceInfo
- MediaDevices
- MediaKeyMessageEvent
- MediaKeySession
- MediaKeyStatusMap
- MediaKeySystemAccess
- MediaKeys
- MerchantValidationEvent
- NDEFMessage
- NDEFRecord
- NFCErrorEvent
- NFCReader
- NFCReadingEvent
- NFCWriter
- NavigationPreloadManager
- OrientationSensor
- PasswordCredential
- PaymentAddress
- PaymentMethodChangeEvent
- PaymentRequest
- PaymentResponse
- Presentation
- PresentationAvailability
- PresentationConnection
- PresentationConnectionAvailableEvent
- PresentationConnectionCloseEvent
- PresentationConnectionList
- PresentationReceiver
- PresentationRequest
- PublicKeyCredential
- RTCIceTransport
- RTCQuicStream
- RTCQuicTransport
- RelativeOrientationSensor
- SMS
- SMSReceiver
- Sensor
- SensorErrorEvent
- Serial
- SerialPort
- ServiceWorker
- ServiceWorkerContainer
- ServiceWorkerRegistration
- StorageManager
- TextDetector
- USB
- USBAlternateInterface
- USBConfiguration
- USBConnectionEvent
- USBDevice
- USBEndpoint
- USBInTransferResult
- USBInterface
- USBIsochronousInTransferPacket
- USBIsochronousInTransferResult
- USBIsochronousOutTransferPacket
- USBIsochronousOutTransferResult
- USBOutTransferResult
- WakeLock
- Window
- WorkerNavigator
- Worklet
- XR
- XRAnchor
- XRAnchorSet
- XRBoundedReferenceSpace
- XRFrame
- XRHitResult
- XRHitTestOptions
- XRHitTestResult
- XRHitTestSource
- XRInputSource
- XRInputSourceArray
- XRInputSourceEvent
- XRInputSourcesChangeEvent
- XRPlane
- XRPlaneDetectionState
- XRPlaneSet
- XRPose
- XRRay
- XRReferenceSpace
- XRReferenceSpaceEvent
- XRRenderState
- XRRigidTransform
- XRSession
- XRSessionEvent
- XRSpace
- XRView
- XRViewerPose
- XRViewport
- XRWebGLLayer
- XRWorldInformation
- XRWorldTrackingState
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with api/ServiceWorker.json and compare its secure-context data with the Service Worker specification. Use the listed interfaces and Chrome's generated IDL list to investigate each applicable specification, then update the corresponding BCD entries so secure-context requirements are represented consistently across the dataset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100