summaryrefslogtreecommitdiff
path: root/fpdfsdk/fpdfview_c_api_test.c
diff options
context:
space:
mode:
authorArtem Strygin <art-snake@yandex-team.ru>2017-08-09 18:50:59 +0300
committerChromium commit bot <commit-bot@chromium.org>2017-08-09 16:10:23 +0000
commitd24b97ee1d065eff482355ea3ff82be59bb528b1 (patch)
treea736ae139525dddf6f1c62a1669d79d405782fea /fpdfsdk/fpdfview_c_api_test.c
parente13c4f887201e3cce33f927bfd6467e8e0263ea7 (diff)
downloadpdfium-d24b97ee1d065eff482355ea3ff82be59bb528b1.tar.xz
Unify of saving documents.chromium/3181
In the original code the method of writing of objects depends on a much unpredictable factors: as: 1) Is there an updated version of the at least one object in the document. 2) The password is changed. 3) Was this object loaded earlier. 4) The Object is compressed and document have a password. With these factors it is difficult to predict what will be the final file. To reduce volatility use only one method that works in all cases mentioned. This method is parse then serialize. Change-Id: I3d7dcadd10abffbad68d1f993f2dd60b039ed989 Reviewed-on: https://pdfium-review.googlesource.com/9572 Commit-Queue: Art Snake <art-snake@yandex-team.ru> Reviewed-by: dsinclair <dsinclair@chromium.org>
Diffstat (limited to 'fpdfsdk/fpdfview_c_api_test.c')
0 files changed, 0 insertions, 0 deletions