From 06f3042167126d60184dc3c401e71924cf3b46af Mon Sep 17 00:00:00 2001 From: Ryan Harrison Date: Fri, 5 Oct 2018 20:43:46 +0000 Subject: Remove SetSaveCalled API This was meant to be part of a mechanism to alert users that entered data into a PDF form was not going to actually be saved how they would expect. The UI for this is blocked on a bug in V8, and is now being superseded by work to correctly implement saving. BUG=pdfium:953 Change-Id: Id9c85c109a3f6a6b4ee69d35f366006be4dc9c32 Reviewed-on: https://pdfium-review.googlesource.com/c/43552 Reviewed-by: Henrique Nakashima Commit-Queue: Ryan Harrison --- fpdfsdk/fpdf_view_c_api_test.c | 1 - 1 file changed, 1 deletion(-) (limited to 'fpdfsdk/fpdf_view_c_api_test.c') diff --git a/fpdfsdk/fpdf_view_c_api_test.c b/fpdfsdk/fpdf_view_c_api_test.c index 2c8665156e..0fc28c31f4 100644 --- a/fpdfsdk/fpdf_view_c_api_test.c +++ b/fpdfsdk/fpdf_view_c_api_test.c @@ -249,7 +249,6 @@ int CheckPDFiumCApi() { #endif CHK(FORM_Redo); CHK(FORM_ReplaceSelection); - CHK(FORM_SetSaveCallback); CHK(FORM_Undo); CHK(FPDFDOC_ExitFormFillEnvironment); CHK(FPDFDOC_InitFormFillEnvironment); -- cgit v1.2.3