Looks like we finally got a real answer here :
So version 2.8.0 might fix the issue => to be checked and confirmed