hmm I don't think this is the chooser's fault. There is something wrong in either the device/bluetooth api or in the Web Bluetooth code. I'll have to take a look at how the page is getting the name.

So this is what happens:

1. Show the chooser
2. Start scanning
3. Once we find a device we get some information i.e. the name and put it in the chooser.

It seems that in 3, the device name is not yet available if this is the *first time* we are seeing the device, so it just shows the address.

To solve we I think we'll have to parse the name from the advertising data manually (Which is what CoreBluetooth does so it's surprising we don't get the name as soon as a device is discovered) and use that if the name is not available yet.

ortuno's patch series from https://codereview.chromium.org/2217573002/ will update the chooser items as additional advertisements are received. It may have the side-effect of updating the items with names if they're available at that later time.

Fixed by http://crrev.com/2242943002