That is normal behavior and won't affect final users in any way:
- If the intervention is about blocked vibrate calls: some browsers won't allow vibration requests to be called by our library if the user hasn't first touched/clicked the page, and will block these calls (outside from normal JavaScript code execution).
- If the intervention is about non-passive event listeners: we need to actively listen for scroll events inside the BarcodePicker component in order to provide our camera zoom functionality on supported browsers/devices. Rest assured that due to their limited scope and functionality these listeners won't actually affect the performance of your webpage in any way.