XFA: make FPDFViewEmbeddertest.Crashers test run successfully.

XFA: make FPDFViewEmbeddertest.Crashers test run successfully.

XFA is pickier, and returns false when loading some mangled documents.

TBR=thestig@chromium.org

Committed: https://pdfium.googlesource.com/pdfium/+/a946e3a8854b09c2130c92f1ae24cb796a0f9095

[Tom Sepez, 2015-01-27 01:18:30]

FYI ... just fixing a test result.

[Tom Sepez, 2015-01-27 01:18:38]

Committed patchset #1 (id:1) manually as
a946e3a8854b09c2130c92f1ae24cb796a0f9095 (presubmit successful).

[Lei Zhang, 2015-01-27 02:23:43]

Shouldn't the two branches both return true? Are we out of sync because we
didn't merge everything, or is the XFA code causing the test to return false?

[Tom Sepez, 2015-01-27 18:56:16]

On 2015/01/27 02:23:43, Lei Zhang wrote:
> Shouldn't the two branches both return true? Are we out of sync because we
> didn't merge everything, or is the XFA code causing the test to return false?
Its a change to the test harness to make it run seamlessly with XFA, which
requires one additional API call (LoadXFA()) before the document is considered
opened. Some malformed documents survived early phases of the parse, but are
recognized as bad by LoadXFA.

[Lei Zhang, 2015-01-27 19:23:33]

lgtm