Closed selaias closed 9 years ago
I guess its the async loading causes this (??)
Fixed with v2.2.1. Thanks!
I guess its the async loading causes this (??)