We are experiencing an issue with Prince's `static` / `flow` header creation mechanic. Please see the screenshot attached.
Basically, when we inject our header into the 'flow', the spacing on them becomes 'off' and the <td> are each 1px on each side larger than the original <td>. When paired with normal that is on the regular page, this creates growingly "off" spacing. Note how the red lines no longer align, by the end of the table. Note that the "header" (the top collection of cells) is in fact a collection of <tr> <td> inside a <table>, not a <tr> <th> inside a <table>.
Is this a known issue? When we take things out of the flow, everything is correctly aligned again, which strongly suggests the "flow" injection process is doing some kind of weird wrapping that is causing alignment issues.
We were able to somewhat confirm that we do not have inherited CSS issues because we've !important reset our margins, padding and border, and set box-sizing to borders.
Additionally, to emphasize, the issue goes away when we no longer use the prince-flow mechanism.
Basically, when we inject our header into the 'flow', the spacing on them becomes 'off' and the <td> are each 1px on each side larger than the original <td>. When paired with normal that is on the regular page, this creates growingly "off" spacing. Note how the red lines no longer align, by the end of the table. Note that the "header" (the top collection of cells) is in fact a collection of <tr> <td> inside a <table>, not a <tr> <th> inside a <table>.
Is this a known issue? When we take things out of the flow, everything is correctly aligned again, which strongly suggests the "flow" injection process is doing some kind of weird wrapping that is causing alignment issues.
We were able to somewhat confirm that we do not have inherited CSS issues because we've !important reset our margins, padding and border, and set box-sizing to borders.
Additionally, to emphasize, the issue goes away when we no longer use the prince-flow mechanism.
Edited by zackingit