issues
search
mkruisselbrink
/
navigator-connect
Apache License 2.0
25
stars
8
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Any value in re-open this spec in the wake of foreign-fetch's removal?
#44
rektide
opened
6 years ago
0
Clarify the Status of This Document
#43
anssiko
closed
9 years ago
1
Connect algorithm: fire connect event at navigator.services, not global.
#42
mgiuca
closed
9 years ago
0
navigator.connect should honor content security policy (CSP) "iframe-src" restrictions
#41
bsittler
opened
9 years ago
0
Start work on formalizing the API described in issue #39
#40
mkruisselbrink
closed
9 years ago
0
Proposal for updated and renamed API to avoid near-collision with navigator.connection
#39
bsittler
opened
9 years ago
13
Use ServiceWorkerRegistration and its messaging design as-is option
#38
jungkees
closed
9 years ago
5
How should long lived connections be exposed to service workers.
#37
mkruisselbrink
opened
9 years ago
0
How to detect a connection being closed/going away.
#36
mkruisselbrink
opened
9 years ago
2
Should this API be using MessagePort to represent connections
#35
mkruisselbrink
closed
9 years ago
1
How should messages to long running connections get delivered
#34
mkruisselbrink
opened
9 years ago
0
Add current source for demo for navigator.connect
#33
jpchase
closed
1 year ago
0
Naming guidelines for navigator.connect service "URL"
#32
bsittler
opened
9 years ago
0
Typo
#31
wilsonpage
closed
9 years ago
0
Ports model
#30
jungkees
opened
9 years ago
7
Add an optional property bag to .connect()
#29
jungkees
opened
9 years ago
1
Breaking out fallback request interception
#28
slightlyoff
opened
9 years ago
5
Thoughts on Mozilla's email shared worker use case from n.c's perspective
#27
jungkees
opened
9 years ago
0
Ports
#26
annevk
opened
9 years ago
4
Minimal navigator.connect Demo
#25
reillyeon
opened
9 years ago
1
Add jungkees as a co-editor; Update steps for connect method and Connect...
#24
jungkees
closed
9 years ago
1
Use Case: Offline REST APIs
#23
benfrancis
opened
9 years ago
1
Handle fall through requests
#22
jungkees
opened
9 years ago
2
Add text about the network install headers' maximum scope rule
#21
jungkees
closed
9 years ago
0
Add some examples for the design alternatives.
#20
jyasskin
opened
9 years ago
0
A way to hand off in-scope network requests to a third party's Service Worker
#19
KenjiBaheux
opened
9 years ago
2
Initial draft of design-alternatives.md
#18
jakeleichtling
closed
9 years ago
3
Provide declarative API to specify what origins are allowed to connect to a service.
#17
mkruisselbrink
opened
9 years ago
0
Changed Extending the Platform and moved to new Non-Goals section
#16
jakeleichtling
closed
9 years ago
1
Use cases intro: say that use cases demonstrate why SW - SW comm. is necessary
#15
jakeleichtling
closed
9 years ago
0
Made Service Workers links where the href was missing
#14
jakeleichtling
closed
9 years ago
0
Added link for stale-while-revalidate
#13
jakeleichtling
closed
9 years ago
0
Changed Shared Fonts section to not overstate browser cache disadvantages
#12
jakeleichtling
closed
9 years ago
3
Changed Shared Fonts section to address why browser cache falls short
#11
jakeleichtling
closed
9 years ago
4
Add a Use Cases document to the repository.
#10
jyasskin
closed
9 years ago
0
Add some more links to the document header.
#9
jyasskin
closed
9 years ago
0
Add an explainer document
#8
jyasskin
closed
9 years ago
1
Add a use cases document
#7
jyasskin
opened
9 years ago
0
Add a README for navigator.connect
#6
jyasskin
closed
9 years ago
0
Add CrossOriginConnectEvent and CrossOriginServiceWorkerClient objects.
#5
reillyeon
closed
9 years ago
0
Replace 'foreign' with 'crossorigin' in the polyfill and tests.
#4
reillyeon
closed
9 years ago
0
Update SW scope point to test directory.
#3
reillyeon
closed
9 years ago
1
Registration of the service worker for a third party service
#2
KenjiBaheux
opened
9 years ago
9
Discovery
#1
rektide
opened
9 years ago
4