nth-child condition fix

[datb-com]

Great to see that flyingsaucer is still being maintained, and now with OpenPDF - excellent!

I found a bug in support for the nth-child CSS condition. This suggested correction aligns to the formal representation and matches Firefox, Safari and Chrome.
See screenshots in the attached for the pre and post flyingsaucer behaviour and the same CSS in browsers.

[pbrant]

Thanks! Do you need a release with this change? I'm happy to do one if so, but if not, I'll bundle it into the next one (which, depending on the number of patches submitted, is probably a few months away).

[datb-com]

Peter No, I don't need a release urgently, I'll use my locally modified copy. We've been using flyingsaucer for quite a few years and hadn't been keeping up to date. It was great yesterday to be able to update FS and move from iText to OpenPDF with very little issue. I'm about to look into a pagination issue. I sometimes get a blank page when I do a page-break-before:always. My theory is that if the page that follows is a full page it does another page break. If I have any luck with this I'll raise another PR. Thanks for a great library. Jason Jason Dore Technical director datb 07970 663669 01572 720767

…

On 15 Mar 2019, at 13:17, Peter Brant ***@***.***> wrote: Thanks! Do you need a release with this change? I'm happy to do one if so, but if not, I'll bundle it into the next one (which, depending on the number of patches submitted, is probably a few months away). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#158 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AuTg71ZGX6HL6nXSzfrKDFLbnnZ2Nn5fks5vW51fgaJpZM4b13cB>.