- From: James Graham <james@hoppipolla.co.uk>
- Date: Thu, 12 Dec 2019 13:11:59 +0000
- To: Philip Jägenstedt <foolip@google.com>
- Cc: David Burns <dburns@mozilla.com>, Luke Zielinski <lpz@google.com>, public-browser-tools-testing@w3.org
On 12/12/2019 13:09, Philip Jägenstedt wrote: > On Thu, Dec 12, 2019 at 12:25 PM James Graham <james@hoppipolla.co.uk> wrote: >> >> On 12/12/2019 10:52, Philip Jägenstedt wrote: >>> Would this be used only for automating PDF creation, or is there also a >>> testing (WPT) side to it? +Luke Zielinski <mailto:lpz@google.com> >> >> Both are valuable; we want to make it possible to test paginated layout >> and the working hypothesis is that the best way to do that is reftests >> using the print rendering pipeline. > > Would that work by rendering the PDF to an image using another tool, > or should this endpoint be able to print directly to an image? > I suspect the render-pdf-to-image — if useful at all — is only required for the wpt use case and is also something we can add in the wpt layer. So I don't think we should make that part of the spec in the absence of a signal from authors that it's functionality they require.
Received on Thursday, 12 December 2019 13:11:52 UTC