Brian Sweeney

I'll need to see if I can reproduce in my environment.

Without doing more research this sounds like an issues related to complex text layout, which Dompdf does not currently support (#2619). Current option for correct handling is to pre-process your...

@rsm0578 I'm posting your HTML here since the debug helper occasionally clears out old files. ``` The benefits of training in the access control market - SourceSecurity.com body, a, p{...

You'd have to look at something like [XDebug's profiling capabilities](https://xdebug.org/docs/profiler) to get a sense of where Dompdf is spending it's time. If you can post a sample of your document...

I mean, as a template that doesn't look like something that would be problematic to render. But it doesn't really help debug any issues since there's no HTML to test...

@RainerBielefeld are you saying that page itself is slow to render? I didn't see a "print to PDF" function so I thought it was just a bug report for the...

@RainerBielefeld it looks like the nested custom elements (datum, gespr, infokopie, etc) are causing the rendering issues. While the original request in this issue can help identify where things are...

So tracking the timing of individual elements is ... hard? Dompdf doesn't provide a lot of hooks into it's internal process. Something that can help here are render-time callbacks. With...

If you think your performance issues might be impacted by a large number of nested inline frames #2949 should address the issue.

I was going to say just style the container `white-space: pre;`. But it looks like somewhere along the way tab is replaced with single spaces. This is maybe not correct...