There was an issue with this previously, but it looks like it should have been fixed in v1.3.0. I haven't seen it since then, would be interested to hear if anyone else has seen it on recent versions.
↧
There was an issue with this previously, but it looks like it should have been fixed in v1.3.0. I haven't seen it since then, would be interested to hear if anyone else has seen it on recent versions.