Ok! Thank you!
We reproduced the issue – it seems to be a bug with header height computations.
We plan to find a solution till the next beta release.
As a workaround I would recommend to use inline header definitions with
; however there are some scenarios, where it is quite tricky to use the tag – for example if your source documents are read-only and cannot be modified.