Honestly, maybe this is incredibly retro of me, but I prefer table-based layouts to CSS-based ones. When a site's CSS file fails to load, table-based layouts at least still generally resemble what they're supposed to look like; ones based in CSS look atrocious. And CSS-based layouts are sickeningly printer-unfriendly. I know the world's been <div>-happy for the past few years, but it really isn't all that great... especially when a .css fails to load.
I'm maintainer of an adults-only community, and one of the things that I do before admitting anyone to it is print-to-pdf their profile pages to make sure I have hard proof that they represented themselves as an adult. This is a mirror of a community on IJ. When I print-to-pdf there, things look fine, but over here, the resulting PDF looks heinously bad. It has the correct information, but it looks wretched. Half the profile information never even prints! Fortunately, the half that does print is the half I need most, but still, if I needed the rest, I'm not sure what I'd do. I've been considering opening a bug report on that for a while, as a matter of fact; I'm pretty sure it's the DIV coding that's doing it.
no subject
I'm maintainer of an adults-only community, and one of the things that I do before admitting anyone to it is print-to-pdf their profile pages to make sure I have hard proof that they represented themselves as an adult. This is a mirror of a community on IJ. When I print-to-pdf there, things look fine, but over here, the resulting PDF looks heinously bad. It has the correct information, but it looks wretched. Half the profile information never even prints! Fortunately, the half that does print is the half I need most, but still, if I needed the rest, I'm not sure what I'd do. I've been considering opening a bug report on that for a while, as a matter of fact; I'm pretty sure it's the DIV coding that's doing it.