@rbmntjs @kapowaz Well it's likely to do with a parsing issue as Rob says. The browser locates the element then would have to step back.