Results 1 comments of Klaus Kopec

@jimpdx I have not encountered that error back when I implemented this. However, I've not used the component much after that, so it's possible that recent changes on either side...