Skip to content

Issues: WICG/crash-reporting

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

9 Open 4 Closed
9 Open 4 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

Additional signal: is_top_level
#20 opened Nov 1, 2024 by clelland
Expose a JS API to programmatically add additional client context
#15 opened Jun 10, 2024 by nicholaschen
1
Adding support for additional context / dimensions in the crash report
#14 opened Jun 10, 2024 by nicholaschen
3
Has this stalled?
#13 opened Feb 9, 2023 by marcoscaceres
3
Call stacks in crash reports from unresponsive web pages
#12 opened Jan 20, 2023 by sethbrenith
1
Spec should define a processing model
#11 opened Dec 17, 2020 by clelland
1
2
Set up auto-publish-on-commit
#9 opened Jun 25, 2020 by clelland
1
Expose more qualitative data
#7 opened Apr 24, 2020 by annevk
4
Should be Opt-In: Creates privacy harm with little to no upside for Web users privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
#1 opened Dec 25, 2019 by pes10k
23
ProTip! no:milestone will show everything without a milestone.