The problem was with how we were sending the boundary events when the capture is changed. In the previous model the processPendingPointerCapture was sending the boundary events particularly if some conditions hold. Those conditions were tricky and not covering every case and this case was noe of them. The case is that a touch starts on A and it captures itself to B and move to B and leaves the screen.
After crrev.com/2174863002 the previous model is simplified and we don't have this many edge cases to cover and they automatically work.

Thanks for investigating.