Permissions-Policy features are incomplete

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

some features are supported in browser implement but its bcd item not added yet

Feature	Chrome
ch-device-memory
ch-downlink
ch-dpr
ch-ect
ch-prefers-color-scheme
ch-prefers-reduced-motion
ch-prefers-reduced-transparency
ch-rtt
ch-save-data
ch-ua
ch-ua-arch
ch-ua-bitness
ch-ua-form-factors
ch-ua-full-version
ch-ua-full-version-list
ch-ua-mobile
ch-ua-model
ch-ua-platform
ch-ua-platform-version
ch-ua-wow64
ch-viewport-height
ch-viewport-width
ch-width
clipboard-read
clipboard-write
interest-cohort
join-ad-interest-group
keyboard-map	97
private-aggregation
private-state-token-issuance
private-state-token-redemption
run-ad-auction
shared-storage
shared-storage-select-url
sync-xhr	65
unload	107? 120?

some features only have partially support

[!Note]

• web-share may not be supported, see https://github.com/mdn/browser-compat-data/issues/20380
• deferred-fetch, deferred-fetch-minimal and gamepad are in BCD of Permissions-Policy but not in BCD of <iframe>
• speaker-selection are in BCD of <iframe> but not in BCD of Permissions-Policy

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Safari

What did you expect to see?

add those data

Did you test this? If so, how?

test in browser console (windows 11 desktop)

test environment:

chrome M135

test code:

document.featurePolicy.features()

test result:

// chrome M135
accelerometer,
attribution-reporting,
autoplay,
bluetooth,
browsing-topics,
camera,
ch-device-memory,
ch-downlink,
ch-dpr,
ch-ect,
ch-prefers-color-scheme,
ch-prefers-reduced-motion,
ch-prefers-reduced-transparency,
ch-rtt,
ch-save-data,
ch-ua,
ch-ua-arch,
ch-ua-bitness,
ch-ua-form-factors,
ch-ua-full-version,
ch-ua-full-version-list,
ch-ua-mobile,
ch-ua-model,
ch-ua-platform,
ch-ua-platform-version,
ch-ua-wow64,
ch-viewport-height,
ch-viewport-width,
ch-width,
clipboard-read,
clipboard-write,
compute-pressure,
cross-origin-isolated,
deferred-fetch,
deferred-fetch-minimal,
display-capture,
encrypted-media,
fullscreen,
gamepad,
geolocation,
gyroscope,
hid,
identity-credentials-get,
idle-detection,
interest-cohort,
join-ad-interest-group,
keyboard-map,
local-fonts,
magnetometer,
microphone,
midi,
otp-credentials,
payment,
picture-in-picture,
private-aggregation,
private-state-token-issuance,
private-state-token-redemption,
publickey-credentials-create,
publickey-credentials-get,
run-ad-auction,
screen-wake-lock,
serial,
shared-storage,
shared-storage-select-url,
storage-access,
sync-xhr,
unload,
usb,
window-management,
xr-spatial-tracking,

// firefox M136
camera,
display-capture,
fullscreen,
gamepad,
geolocation,
microphone,
publickey-credentials-create,
publickey-credentials-get,
screen-wake-lock,
speaker-selection,
storage-access,
web-share,

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md
https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/iframe

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

Start with the Permissions Policy feature list and the linked MDN Permissions-Policy and iframe pages, then inspect the existing BCD entries for those features. Verify each browser and version independently rather than treating featurePolicy.features() as support data. Done means the applicable BCD entries are added or corrected, including the noted differences between Permissions-Policy and iframe data.