Skip to content

Issues: w3cping/tracking-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
114 Open 51 Closed
114 Open 51 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Integration with permissions API needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vibration https://w3c.github.io/vibration/ wg:das https://www.w3.org/groups/wg/das
#471 opened Jul 19, 2024 by w3cbot
Clarify that null is never exposed to the page close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:device-posture https://w3c.github.io/device-posture/ wg:das https://www.w3.org/groups/wg/das
#470 opened Jul 19, 2024 by w3cbot
Require user activation to use API needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:geolocation https://w3c.github.io/geolocation-api/ wg:das https://www.w3.org/groups/wg/das
#463 opened Jun 15, 2024 by w3cbot
Fingerprinting section could be improved needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:webcodecs https://w3c.github.io/webcodecs/ wg:media https://www.w3.org/groups/wg/media
#455 opened May 9, 2024 by w3cbot
status list index is a persistent cross-origin identifier close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#450 opened Mar 7, 2024 by w3cbot
mitigations for risk of unique status lists close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#449 opened Mar 7, 2024 by w3cbot
caching status lists as a mitigation for identifying when the holder visited a verifier close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#448 opened Mar 7, 2024 by w3cbot
anonymizing proxy rather than CDN as a privacy mitigation close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#447 opened Mar 7, 2024 by w3cbot
information revealed by status updates close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#446 opened Mar 7, 2024 by w3cbot
when revocation status is and isn't appropriate to present close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#445 opened Mar 7, 2024 by w3cbot
status list index randomization requirement close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#443 opened Mar 7, 2024 by w3cbot
describe dummy or decoy entries as a privacy mitigation close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#442 opened Mar 7, 2024 by w3cbot
MediaRecorder specification expects to synchronously know the list of supported mime types needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:mediastream-recording https://w3c.github.io/mediacapture-record/ wg:webrtc https://www.w3.org/groups/wg/webrtc
#438 opened Feb 1, 2024 by w3cbot
RTC capabillity negotiation needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:media-capabilities https://w3c.github.io/media-capabilities/ wg:media https://www.w3.org/groups/wg/media
#437 opened Jan 16, 2024 by w3cbot
Point Privacy and Security Considerations section back to Data Integrity close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-di-ecdsa https://w3c.github.io/vc-di-ecdsa/ wg:vc https://www.w3.org/groups/wg/vc
#410 opened Aug 19, 2023 by w3cbot
Highlight security/privacy trade-offs between RDF-CANON and JCS close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-data-integrity https://w3c.github.io/vc-data-integrity/ wg:vc https://www.w3.org/groups/wg/vc
#409 opened Aug 19, 2023 by w3cbot
Add guidance on inclusion of unique tracking identifiers close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-json-schema https://w3c.github.io/vc-json-schema/ wg:vc https://www.w3.org/groups/wg/vc
#408 opened Aug 18, 2023 by w3cbot
Add guidance for wallets when using JsonSchemaCredential and selected disclosure close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-json-schema https://w3c.github.io/vc-json-schema/ wg:vc https://www.w3.org/groups/wg/vc
#407 opened Aug 18, 2023 by w3cbot
Encourage usage of OHTTP during schema resolution close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-json-schema https://w3c.github.io/vc-json-schema/ wg:vc https://www.w3.org/groups/wg/vc
#406 opened Aug 18, 2023 by w3cbot
Align exposing scalabilityMode with the WebRTC "hardware capabilities" check needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:webrtc-svc https://w3c.github.io/webrtc-svc/ wg:webrtc https://www.w3.org/groups/wg/webrtc
#386 opened May 5, 2023 by w3cbot
[PING] Only allow triggering authentication from a foreground tab close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:secure-payment-confirmation https://w3c.github.io/secure-payment-confirmation wg:payments https://www.w3.org/groups/wg/payments
#381 opened Apr 7, 2023 by w3cbot
Specify what kind of attacks are considered and addressed close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:compute-pressure https://w3c.github.io/compute-pressure/ wg:das https://www.w3.org/groups/wg/das
#377 opened Mar 29, 2023 by w3cbot
"no side channels" subsection issues close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:compute-pressure https://w3c.github.io/compute-pressure/ wg:das https://www.w3.org/groups/wg/das
#376 opened Mar 29, 2023 by w3cbot
"first party context" section concerns close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:compute-pressure https://w3c.github.io/compute-pressure/ wg:das https://www.w3.org/groups/wg/das
#375 opened Mar 29, 2023 by w3cbot
"power-supply" is a fingerprinting vector close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:compute-pressure https://w3c.github.io/compute-pressure/ wg:das https://www.w3.org/groups/wg/das
#369 opened Mar 21, 2023 by w3cbot
ProTip! Follow long discussions with comments:>50.