@MikeV @Pegasus @jbob That does indeed sound like a little component bug…
What would be helpful is a list of components you’re seeing this issue on along with a sample document. That way we can aim to get a fix in ASAP for you guys!