@elgarfo If we change anything in our current implementation, can fix the issue in both firefox and chrome? Any idea?