In WebKit (WebKit-SVN-r21081.dmg), the bug reappears for multicolumn layouts using the preliminary CSS3 functionality. Specifically, dataWithPDFInsideRect returns a PDF as if the multicolumn layout was not present. For example, http://webkit.org/blog/?p=88 would produce a PDF with a single column. This is also true when the same page is printed. +++ This bug was initially created as a clone of Bug #12419 +++ There appears to be no way for a user to render the current web page to a single PDF file *exactly* as it appears on screen. The value of [[[[webView mainFrame] frameView] documentView] bounds] is incorrect when used to specify the bounds for a subsequent dataWithPDFInsideRect: call on the documentView. The resulting PDF file on pages with lots of text, such as the sample page loaded in this app, are clipped at the very end. In addition, WebKit does not respect the user's media style preferences when calling dataWithPDFInsideRect:. Apparently, a different text layout engine is being used, which is why the bounds result is incorrect. To see a graphic example, build and run the attached application, follow the instructions, and examine the results.
I think this is a known issue with the initial CSS3 column implementation. Dave Hyatt will know more about this.
I only found one commit with this "dataWithPDFInsideRect": https://github.com/WebKit/WebKit/commit/cf8ed2dc1b0ad52607036e2069f181affb29c951 and in current code base, only single reference in one comment here: https://github.com/WebKit/WebKit/blob/c2f1bd3f763bca4b4b769f0dad4334ec28a25832/Tools/DumpRenderTree/mac/DumpRenderTree.mm#L1452 Do we need to track this any further? Thanks!
-dataWithPDFInsideRect is an AppKit method, which is implemented by WebKit indirectly. Unsure if this is still an issue, but given that Legacy WebKit is deprecated, we will not be fixing it either way.