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

336 Open 132 Closed
336 Open 132 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

Add explicit description on what should be done in incognito/private browsing mode close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:webauthn https://w3c.github.io/webauthn/ tracker PING is following a discussion, but doesn't require resolution. wg:webauthn https://www.w3.org/groups/wg/webauthn
#48 opened Feb 20, 2020 by plehegar
Make getGamepads API asyncronous to support permission request close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:gamepad https://w3c.github.io/gamepad/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#47 opened Feb 20, 2020 by plehegar
How do connection/disconnection events interact with 'device has been interacted with by the user'? pending Issue created by the tracker tool and may need to be refined s:gamepad https://w3c.github.io/gamepad/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#46 opened Feb 20, 2020 by plehegar
Clarifications for getGamepads pending Issue created by the tracker tool and may need to be refined s:gamepad https://w3c.github.io/gamepad/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#45 opened Feb 20, 2020 by plehegar
are timestamps a potential tracking/fingerprinting vector? pending Issue created by the tracker tool and may need to be refined s:gamepad https://w3c.github.io/gamepad/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#44 opened Feb 20, 2020 by plehegar
Access to magnetometer and potential security & privacy issues pending Issue created by the tracker tool and may need to be refined s:generic-sensor https://w3c.github.io/sensors/ tracker PING is following a discussion, but doesn't require resolution. wg:das https://www.w3.org/groups/wg/das
#43 opened Feb 20, 2020 by plehegar
Stats API should require additional permission / user opt-in (w3c/webrtc-stats#550) close? The related issue was closed by the Working Group s:webrtc-stats https://w3c.github.io/webrtc-stats/ tracker PING is following a discussion, but doesn't require resolution. wg:webrtc https://www.w3.org/groups/wg/webrtc
#42 opened Feb 18, 2020 by pes10k
Consider removing wildcard option of the Timing-Allow-Origin header to prevent accidental application state leakage (w3c/resource-timing #223) needs-resolution PING expects this item to be resolved to their satisfaction. s:resource-timing https://w3c.github.io/resource-timing/ wg:webperf https://www.w3.org/groups/wg/webperf
#41 opened Feb 5, 2020 by kdzwinel
@kdzwinel
Consider removing wildcard option of the Timing-Allow-Origin header to prevent browser history leakage (w3c/resource-timing #222) needs-resolution PING expects this item to be resolved to their satisfaction. s:resource-timing https://w3c.github.io/resource-timing/ wg:webperf https://www.w3.org/groups/wg/webperf
#40 opened Feb 5, 2020 by kdzwinel
@kdzwinel
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy (w3c/resource-timing #221) needs-resolution PING expects this item to be resolved to their satisfaction. s:resource-timing https://w3c.github.io/resource-timing/ wg:webperf https://www.w3.org/groups/wg/webperf
#39 opened Feb 5, 2020 by kdzwinel
@kdzwinel
Correct / real URLs should be enforced, to avoid breaking adblockers (WICG/webpackage#551) cg:wicg https://www.w3.org/groups/cg/wicg s:webpackage tracker PING is following a discussion, but doesn't require resolution.
#38 opened Jan 30, 2020 by pes10k
Spec should define how the feature interacts with blocking tools (filterlists etc.) (wicg/web-transport#96) close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. s:webtransport https://w3c.github.io/webtransport/ wg:webtransport https://www.w3.org/groups/wg/webtransport
#35 opened Jan 15, 2020 by pes10k
1
timezonechange event could enable cross-origin tracking via simultaneous background event firing (whatwg/html#3047) s:html https://html.spec.whatwg.org/multipage/ tracker PING is following a discussion, but doesn't require resolution. whatwg https://whatwg.org/
#34 opened Jan 13, 2020 by npdoty
3
Should be Opt-In: Creates privacy harm with little to no upside for Web users (WICG/intervention-reporting#1) cg:wicg https://www.w3.org/groups/cg/wicg s:intervention-reporting https://wicg.github.io/intervention-reporting/ tracker PING is following a discussion, but doesn't require resolution.
#33 opened Dec 25, 2019 by pes10k
Should be Opt-In: Creates privacy harm with little to no upside for Web users (WICG/deprecation-reporting#1) cg:wicg https://www.w3.org/groups/cg/wicg s:deprecation-reporting https://wicg.github.io/deprecation-reporting/ tracker PING is following a discussion, but doesn't require resolution.
#32 opened Dec 25, 2019 by pes10k
Should be Opt-In: Creates privacy harm with little to no upside for Web users (WICG/crash-reporting#1) cg:wicg https://www.w3.org/groups/cg/wicg s:crash-reporting https://wicg.github.io/crash-reporting/ tracker PING is following a discussion, but doesn't require resolution.
#31 opened Dec 25, 2019 by pes10k
TTML privacy review close? The related issue was closed by the Working Group s:ttml https://w3c.github.io/ttml2/ tracker PING is following a discussion, but doesn't require resolution. wg:timed-text https://www.w3.org/groups/wg/timed-text
#30 opened Dec 19, 2019 by jyasskin
4 tasks
Need to consider privacy implications of high resolution time (w3c/IntersectionObserver#404) close? The related issue was closed by the Working Group s:intersection-observer https://w3c.github.io/IntersectionObserver/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#29 opened Dec 19, 2019 by brentzundel
1
id field in gamepad might have a persistent identifier (w3c/gamepad#73) s:gamepad https://w3c.github.io/gamepad/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#28 opened Dec 18, 2019 by npdoty
privacy concerns with proposal through inducing network requests (WICG/ScrollToTextFragment#76) cg:wicg https://www.w3.org/groups/cg/wicg pending Issue created by the tracker tool and may need to be refined s:ScrollToTextFragment https://wicg.github.io/scroll-to-text-fragment/ tracker PING is following a discussion, but doesn't require resolution.
#26 opened Dec 16, 2019 by pes10k
IntersectionObserver spec needs privacy considerations section (w3c/IntersectionObserver#403) close? The related issue was closed by the Working Group s:intersection-observer https://w3c.github.io/IntersectionObserver/ tracker PING is following a discussion, but doesn't require resolution. wg:webapps https://www.w3.org/groups/wg/webapps
#25 opened Dec 10, 2019 by brentzundel
2 tasks
[css-fonts] limit local fonts to those selected by users in browser settings (or other browser chrome) (w3c/csswg-drafts#4497) close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. s:css-fonts https://drafts.csswg.org/css-fonts/ wg:css https://www.w3.org/groups/wg/css
#24 opened Nov 11, 2019 by pes10k
Only reveal labels of devices user has given permission to (w3c/mediacapture-main#640) close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. s:mediacapture-streams https://w3c.github.io/mediacapture-main/ wg:webrtc https://www.w3.org/groups/wg/webrtc
#23 opened Nov 4, 2019 by pes10k
1
Exposing RTCIceCandidateStats.networkType might trigger fingerprinting (w3c/webrtc-stats#374) close? The related issue was closed by the Working Group s:webrtc-stats https://w3c.github.io/webrtc-stats/ tracker PING is following a discussion, but doesn't require resolution. wg:webrtc https://www.w3.org/groups/wg/webrtc
#22 opened Nov 4, 2019 by pes10k
always double key device ids (w3c/mediacapture-main#598) close? The related issue was closed by the Working Group s:mediacapture-streams https://w3c.github.io/mediacapture-main/ tracker PING is following a discussion, but doesn't require resolution. wg:webrtc https://www.w3.org/groups/wg/webrtc
#21 opened Nov 4, 2019 by pes10k
ProTip! Updated in the last three days: updated:>2024-07-26.