[whatwg] Proposal: HTMLCanvasElement.printCallback API

Robert O'Callahan robert at ocallahan.org
Mon Jan 28 15:02:59 PST 2013

On Mon, Jan 28, 2013 at 6:25 PM, Elliott Sprehn <esprehn at gmail.com> wrote:

> 3) If we're advocating that developers "put a canvas on every page that
> covers the whole page" as the standard way to handle large document
> printing why not have a handler that gets given a canvas for every page
> automatically instead of requiring the developer to insert it themselves.

Another use-case is when you have a document that's regular HTML and just
happens to contain one or more <canvas> images that should be beautiful
when printed.

4) SVG is for vector graphics, not canvas. Why can't I replace an entire
> page with an <svg> instead of drawing to a canvas? :)

SVG doesn't fit some use-cases very well, for example, when you generate
graphics from some underlying (large) data model.

Jesus called them together and said, “You know that the rulers of the
Gentiles lord it over them, and their high officials exercise authority
over them. Not so with you. Instead, whoever wants to become great among
you must be your servant, and whoever wants to be first must be your
slave — just
as the Son of Man did not come to be served, but to serve, and to give his
life as a ransom for many.” [Matthew 20:25-28]

More information about the whatwg mailing list