Niklas Gruhn

A little bit more context: The whole waiting-for-capabilities stuff was introduced together with [the torch feature](https://gruhn.github.io/vue-qrcode-reader/demos/Torch.html). Since support for that is inconsistent across devices, users needed a way to feature-detect....

FYI: timeout was introduced in v2.3.3 so you might want to checkout v2.3.2 for comparison.

Right. If anybody is motivated to take of that, I'll be happy to merge it. Just don't have a lot of time on my hands at the moment.

Can you `console.log(decodedCodes)` and show the output?

@robertsLando thank you for your contribution. This is probably the most requested feature but I still would prefer not to include it. Please read my comments on this in #269.

> even with the most accurate heuristic algorithm to choose the right camera you will always have some cases where the user cannot select the desired camera That's true. We...

Hi @TrevinAvery thanks for reporting this. So far I haven't managed to reproduce this but you're right memory issues are always hard to track down. We have a web worker...

Thanks. I tried to track memory allocation and look for memory leaks but nothing obvious on my side. Maybe frames extracted from Pixels camera have too high resolution or something...

There is no timeline for bugs 😅 Unfortunately, I can't reproduce this so I'm not sure what to do about it. Since you're the second person to report issues in...

@TheGreenkey thanks for attaching the report that was definitely helpful. Although I also have a hard time making sense of all this data in DevTools. I'm trying to assemble a...