From 3a105e37f4fa9155ae703261545acdf8221e874e Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Sun, 18 Sep 2016 22:36:40 +0200 Subject: [PATCH] Ensure that `test/driver.js` actually takes the same `Annotation` code-path as the viewer when running `forms` tests (PR 7633 follow-up) Unfortunately PR 7633 missed, and I didn't catch it during review, to update `test/driver.js` such that the `forms` tests takes the correct code-path. This resultet in the `forms` reference test images looking better than they should, and more problematicly differing from the rendering in the viewer. With this patch, the tests now correctly skip over any `Appearance` streams. The `forms` tests now highlights quite clearly (e.g. look at `annotation-tx2.pdf`/`annotation-tx3.pdf`) that we cannot just skip the `Appearance` streams when rendering forms. Hence we're going to have to find a way to fix that *before* enabling forms by default, since both display *and* print would look completely wrong otherwise. Finally, this patch also uncovers one more existing bug that still needs to be fixed, since the current `rasterizeAnnotationLayer` in `test/driver.js` isn't able to handle the contents of e.g. `` and `