Stub out Document::syncAnnotScan method.

Stub out Document::syncAnnotScan method.

The PDF specification [1] says:

"
syncAnnotScan guarantees that all annotations will be scanned
by the time this method returns.
(..)
Normally a background task runs that examine every page and
looks for annotations during idle times.
"

The statement details specifically how Acrobat implements
this method.
Although, neither the method itself nor the background scanner
task are implemented in PDFium (as of today, Ago/2016),
not having ::syncAnnotScan at least stubbed out can be considered
harmfull since its absence makes JS acrobat scripts silently
fail when it has a call to it.

Given that, and following a stub-out pattern present in other
methods including ::addAnnot and ::addField, CL provides
a stubbed out implementation of Document::syncAnnotScan.

[1] http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_api_reference.pdf

BUG=pdfium:492
Committed: https://pdfium.googlesource.com/pdfium/+/bb5fa043a7ef2de165c7903548e5663a6f8bcf9a

[tonikitoo, 2016-08-19 16:16:02]

Description was changed from

==========
Stub out Document::syncAnnotScan method.

The PDF specification [1] says:

"
syncAnnotScan guarantees that all annotations will be scanned
by the time this method returns.
(..)
Normally a background task runs that examine every page and
looks for annotations during idle times.
"

The statement details specifically how Acrobat implements
this method.
Although, neither the method itself nor the background scanner
task are implemented in PDFium (as of today, Ago/2016),
not having ::syncAnnotScan at least stubbed out can be considered
harmfull since its absence makes JS acrobat scripts silently
fail when it has a call to it.

Given that, and following a stub-out pattern present in other
methods including ::addAnnot and ::addField, CL provides
a stub out implementation of Document::syncAnnotScan.

[1]
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_api_referenc...

BUG=pdfium:492
==========

to

==========
Stub out Document::syncAnnotScan method.

The PDF specification [1] says:

"
syncAnnotScan guarantees that all annotations will be scanned
by the time this method returns.
(..)
Normally a background task runs that examine every page and
looks for annotations during idle times.
"

The statement details specifically how Acrobat implements
this method.
Although, neither the method itself nor the background scanner
task are implemented in PDFium (as of today, Ago/2016),
not having ::syncAnnotScan at least stubbed out can be considered
harmfull since its absence makes JS acrobat scripts silently
fail when it has a call to it.

Given that, and following a stub-out pattern present in other
methods including ::addAnnot and ::addField, CL provides
a stubbed out implementation of Document::syncAnnotScan.

[1]
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_api_referenc...

BUG=pdfium:492
==========

[tonikitoo, 2016-08-19 16:16:02]

tonikitoo@igalia.com changed reviewers:
+ dsinclair@chromium.org, thestig@chromium.org, tsepez@chromium.org

[tonikitoo, 2016-08-19 16:16:16]

PTAL

[Tom Sepez, 2016-08-19 17:35:41]

The CQ bit was checked by tsepez@chromium.org

[Tom Sepez, 2016-08-19 17:35:41]

lgtm

[commit-bot: I haz the power, 2016-08-19 17:35:45]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-19 18:18:31]

Description was changed from

==========
Stub out Document::syncAnnotScan method.

The PDF specification [1] says:

"
syncAnnotScan guarantees that all annotations will be scanned
by the time this method returns.
(..)
Normally a background task runs that examine every page and
looks for annotations during idle times.
"

The statement details specifically how Acrobat implements
this method.
Although, neither the method itself nor the background scanner
task are implemented in PDFium (as of today, Ago/2016),
not having ::syncAnnotScan at least stubbed out can be considered
harmfull since its absence makes JS acrobat scripts silently
fail when it has a call to it.

Given that, and following a stub-out pattern present in other
methods including ::addAnnot and ::addField, CL provides
a stubbed out implementation of Document::syncAnnotScan.

[1]
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_api_referenc...

BUG=pdfium:492
==========

to

==========
Stub out Document::syncAnnotScan method.

The PDF specification [1] says:

"
syncAnnotScan guarantees that all annotations will be scanned
by the time this method returns.
(..)
Normally a background task runs that examine every page and
looks for annotations during idle times.
"

The statement details specifically how Acrobat implements
this method.
Although, neither the method itself nor the background scanner
task are implemented in PDFium (as of today, Ago/2016),
not having ::syncAnnotScan at least stubbed out can be considered
harmfull since its absence makes JS acrobat scripts silently
fail when it has a call to it.

Given that, and following a stub-out pattern present in other
methods including ::addAnnot and ::addField, CL provides
a stubbed out implementation of Document::syncAnnotScan.

[1]
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_api_referenc...

BUG=pdfium:492

Committed:
https://pdfium.googlesource.com/pdfium/+/bb5fa043a7ef2de165c7903548e5663a6f8b...
==========

[commit-bot: I haz the power, 2016-08-19 18:18:33]

Committed patchset #1 (id:1) as
https://pdfium.googlesource.com/pdfium/+/bb5fa043a7ef2de165c7903548e5663a6f8b...