Skip to content
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

Jump to bottom

Expose sensors to workers #12

Open
2 tasks
tobie opened this issue Nov 17, 2014 · 3 comments
Open
2 tasks

Expose sensors to workers #12

tobie opened this issue Nov 17, 2014 · 3 comments
Labels
permissions privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. proposed-resolution security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Milestone
Level 2

Comments

@tobie
Copy link
Member

tobie commented Nov 17, 2014 •
edited by alexshalamov
Loading

Expose sensors to workers for perf reasons (avoid blocking main thread).

Actions:

  • Figure out the permissioning story.

Certain use cases require sensors to have background access.
Using a more complex {{PermissionDescriptor}}.
(e.g. with a boolean allowBackgroundUsage = false; [=dictionary member=]),
might be the solution to relax this restriction.

  • Amend IDL
@tobie tobie modified the milestone: FPWD May 8, 2015
@tobie tobie added the action label May 9, 2015
@tobie tobie modified the milestones: Post-FPWD, FPWD May 10, 2015
@tobie tobie removed the action label May 28, 2015
@mkruisselbrink mkruisselbrink mentioned this issue Jan 15, 2016
Open
@tobie tobie modified the milestones: Level 2, Level 1 Jan 19, 2016
@tobie tobie mentioned this issue Apr 1, 2016
Closed
@tobie
Copy link
Member Author

tobie commented May 10, 2016

Splitting that issue up into workers here and service workers in #106.

@tobie tobie changed the title Exposing sensors in workers and service workers Exposing sensors in workers and shared workers May 10, 2016
@anssiko anssiko modified the milestones: Level 1, Level 2 Sep 20, 2016
@tobie tobie added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Oct 28, 2016
@tobie
Copy link
Member Author

tobie commented Oct 28, 2016

We need to figure out the permission story here too.

@tobie tobie changed the title Exposing sensors in workers and shared workers Expose sensors to workers Oct 28, 2016
@tobie tobie self-assigned this Oct 28, 2016
@tobie tobie added the security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. label Dec 2, 2016
@lknik
Copy link
Contributor

lknik commented Feb 7, 2017

That's definitely a thing that begs for a clear display. I.e. UA must clearly show when a sensor is being accessed.

@alexshalamov alexshalamov modified the milestones: Level 2, Level 1 Jun 29, 2017
alexshalamov pushed a commit to alexshalamov/sensors that referenced this issue Sep 26, 2017
Remove duplicate Service Worker inline issue
92a1d6f 
There is a dedicated issue in w3c#12
@alexshalamov alexshalamov mentioned this issue Sep 26, 2017
Merged
@robman robman mentioned this issue Jul 30, 2019
Open
5 tasks
@plehegar plehegar mentioned this issue Feb 18, 2020
Open
@plehegar plehegar mentioned this issue Mar 23, 2020
Open
@w3cbot w3cbot added privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. and removed privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. labels Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
permissions privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. proposed-resolution security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Projects
None yet
Milestone
Level 2
Development

No branches or pull requests
5 participants
@tobie @anssiko @alexshalamov @lknik @w3cbot