- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 28 Apr 2010 07:45:55 +0200
- To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "Jatinder Mann" <jmann@microsoft.com>
On Tue, 27 Apr 2010 22:16:27 +0200, Jatinder Mann <jmann@microsoft.com> wrote: > I would like to get clarification on the following passage [1]: > > "In non-interactive, static, visual media, if the canvas element has > been previously painted on (e.g. if the page was viewed in an > interactive visual medium and is now being printed, or if some script > that ran during the page layout process painted on the element), then > the canvas element represents embedded content with the current image > and size. Otherwise, the element represents its fallback content > instead." This seems like a stupid requirement. Why would we want to print the fallback? In many cases the fallback will be "your browser does not support canvas". > I interpret this to mean, in a non-interactive, static, visual media, > where the canvas element has not been previously painted on, you will > see the fallback content. An example of this scenario would be printing > a webpage where nothing has been drawn on the canvas. What are the other > scenarios? > > I have tried printing a webpage containing the following code, but I did > not see the fallback content on Chrome, Safari, Opera, or Firefox > browsers. > > 0 <html> > 1 <head> > 2 </head> > > 3 <body> > 4 <canvas>This is the fallback</canvas> > > 5 </body> > 6 </html> > > Thanks, > Jatinder > > [1] > http://dev.w3.org/html5/spec/the-canvas-element.html#the-canvas-element > > Jatinder Mann | Internet Explorer Program Manager > -- Simon Pieters Opera Software
Received on Wednesday, 28 April 2010 05:46:32 UTC