Comment 7 for bug 1449685

@Jos, we knew this issue happened in v1.x. We are currently working on refactoring the code and plan to release v2.x. Current we are still in pre-alpha stage for v2.x. The test in #5 is against v2 pre-alpha version.