UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15
Platform: 10895.56.0

Steps to reproduce the problem:
1. Using Nordic's "nRF Connect" app, scan bluetooth where there is a device which can change the advertised manufacturer data (e.g. Wonder Workshop's Dash robot)
2. Note the raw data in the manufacturer field (field 0xFF) 
3. Change the device's advertised manufacturer data (e.g. Put Dash robot in DFU mode by pressing three small top buttons while powering-on)
4. Perform another scan
5. Note the raw data in the manufacturer field

What is the expected behavior?
The manufacturer data field should contain only the data advertised by the device

What went wrong?
The manufacturer data in the second scan is the concatenation of the data from the first scan, with the data from the second, less one byte.

After a reboot of the Chromebook, the manufacturer data is reset.

Attached are screen shots of the initial scan's manufacturer data ("APP mode"), after a second scan once the manufacturer data has changed ("DFU mode after APP mode") and a scan of the second manufacturer data immediately after a reboot ("DFU mode after reboot).

Note that the "DFU mode after app mode" manufacturer data is 57 bytes long, and is a concatenation of the other sets of manufacturer data.  Also, manufacturer data is limited to 31 bytes by specification.

Did this work before? Yes 66, perhaps as recently as 68

Chrome version: 69.0.3497.95  Channel: beta
OS Version: 69.0.3497.95
Flash Version: 31.0.0.108

We have previously provided Google with a device to test.  Please contact me if you need any further information about this hardware.
 

Deleted: APP_mode_after_reboot.png 47.5 KB

	APP_mode_after_reboot.png 47.5 KB View Download

Deleted: DFU_mode_after_APP_mode_scan.png 58.6 KB

	DFU_mode_after_APP_mode_scan.png 58.6 KB View Download

Deleted: DFU_mode_after_reboot.png 46.9 KB

	DFU_mode_after_reboot.png 46.9 KB View Download