9052 2006-05-22 17:57:57 -0700 <canvas> content prints at screen resolution instead of printer resolution 2008-06-30 09:39:41 -0700 1 1 1 Unclassified WebKit Layout and Rendering 420+ Mac OS X 10.4 RESOLVED WONTFIX InRadar P3 Normal --- 1 eric webkit-unassigned andpoul ian oldest_to_newest 43230 0 eric 2006-05-22 17:57:57 -0700 <canvas> content prints at screen resolution instead of printer resolution We should use some sort of PDFContext instead of the current BitmapContext for the <canvas> backend, to allow canvas content to print nicely. We have a Radar for this already, I don't remember the number (and don't have radar on this machine). I believe it was filed by Martin Ott. 59805 1 andpoul 2007-10-29 12:27:06 -0700 I think this is not possible due to the philosophy of <canvas> as a bitmap graphics context (with vector input). Authors of <canvas> pages are relying on the fact that certain operations take a small amout of time when done with limited numbers of pixels, and the fact that when overwritten, pixels "go away" meaning require no further storage. However, if every drawing operation performed on the canvas is cached and then replayed for printing, there could be a ton of drawing commands that essentially make some pages non-printable because it would take forever to compute what actually needed to be drawn for printing. 84623 2 oliver 2008-06-27 21:24:37 -0700 This doesn't make sense in the context of the canvas element (especially given it now includes actual raw bitmap access). 84640 3 ap 2008-06-28 01:30:09 -0700 <rdar://problem/4364207> 84757 4 eric 2008-06-30 09:39:41 -0700 Well, it would still be possible to support both. :) But it's also fine to close this. We have many many many more things to fix with printing first. :)