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

Describe what happens when an advertising packet is received. #117

Closed
jyasskin opened this issue May 21, 2015 · 3 comments
Closed

Describe what happens when an advertising packet is received. #117

jyasskin opened this issue May 21, 2015 · 3 comments
Labels
beacons
Milestone
Initial GATT Comm...

Comments

@jyasskin
Copy link
Member

We need to at least update BluetoothDevice.adData.
@jyasskin jyasskin added the v1 label Jun 17, 2015
@jyasskin
Copy link
Member Author

And fire an event.

@beaufortfrancois
Copy link
Member

Should we have a label for all things related to Physical Web?

@beaufortfrancois
Copy link
Member

A related discussion happens at https://code.google.com/p/chromium/issues/detail?id=568137

jyasskin added a commit to jyasskin/web-bluetooth-1 that referenced this issue May 3, 2016
@jyasskin
Have sites explicitly watch for advertisements on paired devices.
fada859 
This removes the enforcement that a site can only see service data for services
from its allowed services list. Since an advertisement is broadcast and
read-only, I think there's neither any private data in the advertisement nor a
need to protect the device from hostile sites.

Fixes WebBluetoothCG#117 and fixes WebBluetoothCG#212.
@jyasskin jyasskin mentioned this issue May 3, 2016
Merged
jyasskin added a commit that referenced this issue May 6, 2016
@jyasskin
Have sites explicitly watch for advertisements on paired devices. (#235)
725dbf7 
This removes the enforcement that a site can only see service data for services
from its allowed services list. Since an advertisement is broadcast and
read-only, I think there's neither any private data in the advertisement nor a
need to protect the device from hostile sites.

Fixes #117 and fixes #212.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
beacons
Projects
None yet
Milestone
Initial GATT Communication
Development

No branches or pull requests
2 participants
@jyasskin @beaufortfrancois