Closed julienV closed 1 year ago
I can't reproduce this issue. Can you provide a reproduction?
i don't see it any more either, maybe an issue with cache on my side, let's close it...
i still see the issue as its not included in version 1.0.1. Do you plan to release a new version that includes the fix?
please can you make a new release with the fix... it's in fact not in 1.0.1
Version 1.0.2 has been published
see #3