Looks like it happens because the input field is absolutely positioned in relation to an inline element, which is a Chromium bug reported here: https://bugs.chromium.org/p/chromium/issues/detail?id=1001438 (they’re saying it’s going to be fixed for not the next Chrome release but the one after that.)
You can monkeypatch it by adding this CSS somewhere on the page:
.InvisibleCursor {
display: inline-block;
}