Currently, there is no option in requestLEScan to listen for scan responses, nor is there a field in BluetoothAdvertisingEvent to access the scan response. I believe it would be beneficial to introduce 'normal' and 'active' scan modes, as there appears to be confusion in various implementations at present.

For instance, in Chromium, the watchAdvertisements method returns two subsequent events: one with standard manufacturer data and another with the scan response. However, when using requestLEScan, only the standard advertising response is provided.

I propose that establishing a clear distinction would, at the very least, aid in determining which API is stable enough in different implementations to effectively utilize scan responses.