-
Notifications
You must be signed in to change notification settings - Fork 8
Issues: mkruisselbrink/navigator-connect
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
Any value in re-open this spec in the wake of foreign-fetch's removal?
#44
opened Mar 28, 2018 by
rektide
navigator.connect should honor content security policy (CSP) "iframe-src" restrictions
#41
opened Jun 17, 2015 by
bsittler
Proposal for updated and renamed API to avoid near-collision with navigator.connection
#39
opened Jun 9, 2015 by
bsittler
How should long lived connections be exposed to service workers.
#37
opened Jun 3, 2015 by
mkruisselbrink
How should messages to long running connections get delivered
#34
opened Jun 3, 2015 by
mkruisselbrink
Thoughts on Mozilla's email shared worker use case from n.c's perspective
question
#27
opened Apr 16, 2015 by
jungkees
A way to hand off in-scope network requests to a third party's Service Worker
#19
opened Dec 19, 2014 by
KenjiBaheux
Provide declarative API to specify what origins are allowed to connect to a service.
#17
opened Dec 12, 2014 by
mkruisselbrink
ProTip!
no:milestone will show everything without a milestone.