-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[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
Privacy concerns regarding Reporting API (w3c/reporting#169)
close?
The related issue was closed by the Working Group
open
s:reporting
https://w3c.github.io/reporting/
tracker
PING is following a discussion, but doesn't require resolution.
wg:webperf
https://www.w3.org/groups/wg/webperf
#5
opened Aug 21, 2019 by
pes10k
Reporting API should be opt in (w3c/reporting#168)
open
s:reporting
https://w3c.github.io/reporting/
tracker
PING is following a discussion, but doesn't require resolution.
wg:webperf
https://www.w3.org/groups/wg/webperf
#6
opened Aug 21, 2019 by
pes10k
Move enumerateDevices behind permission (w3c/mediacapture-main#612)
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
#10
opened Aug 21, 2019 by
pes10k
WebAudio API: re-review requested
s:webaudio
https://webaudio.github.io/web-audio-api/
wg:audio
https://www.w3.org/groups/wg/audio
#13
opened Sep 16, 2019 by
svgeesus
getCapabilities
seems to leak hardware capabilities w/o a permission (w3c/webrtc-svc#22)
close?
#14
opened Oct 15, 2019 by
pes10k
WoT Architecture: Document lacks sufficient detail to understand how privacy-sensitive information flows through the system
close?
The related issue was closed by the Working Group
s:wot-architecture
https://w3c.github.io/wot-architecture/
tracker
PING is following a discussion, but doesn't require resolution.
wg:wot
https://www.w3.org/groups/wg/wot
#16
opened Oct 22, 2019 by
samuelweiler
Remove text about non-explicit permissions (w3c/sensors#396)
close?
The related issue was closed by the Working Group
open
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
#17
opened Oct 24, 2019 by
pes10k
Spec should include mandatory mitigations for privacy harms / risks (w3c/sensors#397)
open
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
#18
opened Oct 24, 2019 by
pes10k
Open Window Algorithm and tracking through 1ps (w3c/payment-handler#351)
s:payment-handler
https://w3c.github.io/payment-handler
tracker
PING is following a discussion, but doesn't require resolution.
wg:payments
https://www.w3.org/groups/wg/payments
#20
opened Oct 28, 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
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
Standard creates unique, persistent IDs (w3c/mediacapture-main#607)
close?
The related issue was closed by the Working Group
needs-resolution
PING expects this item to be resolved to their satisfaction.
open
s:mediacapture-streams
https://w3c.github.io/mediacapture-main/
wg:webrtc
https://www.w3.org/groups/wg/webrtc
#2
opened Aug 21, 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
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
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
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
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
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
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/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
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
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
[meta][css-fonts-4] Index of local font issues: fingerprinting, I18n, privacy
pending
Issue created by the tracker tool and may need to be refined
s:css-fonts
https://drafts.csswg.org/css-fonts/
s:meta
missing link
tracker
PING is following a discussion, but doesn't require resolution.
wg:css
https://www.w3.org/groups/wg/css
#495
opened Feb 26, 2025 by
w3cbot
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.