When annotaion exceeds 10 pages, print and download are abnormal

[OnlY0226]

Attach (recommended) or Link to PDF file here: https://mozilla.github.io/pdf.js/legacy/web/viewer.html

Configuration:

• Web browser and its version: Google 版本 104.0.5112.79（正式版本） （64 位）
• Operating system and its version: linux
• PDF.js version: v3.0.279
• Is a browser extension:

Steps to reproduce the problem:

1. add annotation on page 1
2. add annotation on page 11
3. print

What is the expected behavior? (add screenshot)
print with annotation
What went wrong? (add screenshot)
report error：
editor.js:298 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'viewportBaseDimensions')
at InkEditor.getRect (editor.js:298:53)
at InkEditor.serialize (ink.js:1065:23)
at get serializable [as serializable] (annotation_storage.js:168:47)
at new PrintAnnotationStorage (annotation_storage.js:204:49)
at get print [as print] (annotation_storage.js:153:12)
at app.js:1683:52
at async Promise.all (index 1)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
https://mozilla.github.io/pdf.js/legacy/web/viewer.html

[Snuffleupagus]

Naively, it seems to me that we should probably serialize the applicable editors when destroying the layer in

pdf.js/src/display/editor/annotation_editor_layer.js

Lines 513 to 530 in 67e1c37

	/**
	* Destroy the main editor.
	*/
	destroy() {
	if (this.#uiManager.getActive()?.parent === this) {
	this.#uiManager.setActiveEditor(null);
	}
	for (const editor of this.#editors.values()) {
	this.#accessibilityManager?.removePointerInTextLayer(editor.contentDiv);
	editor.isAttachedToDOM = false;
	editor.div.remove();
	editor.parent = null;
	}
	this.div = null;
	this.#editors.clear();
	this.#uiManager.removeLayer(this);
	}

Similarly, we should probably deserialize any applicable editors when re-constructing the layer in

pdf.js/src/display/editor/annotation_editor_layer.js

Lines 64 to 82 in 67e1c37

	/**
	* @param {AnnotationEditorLayerOptions} options
	*/
	constructor(options) {
	if (!AnnotationEditorLayer._initialized) {
	AnnotationEditorLayer._initialized = true;
	FreeTextEditor.initialize(options.l10n);
	InkEditor.initialize(options.l10n);
	}
	options.uiManager.registerEditorTypes([FreeTextEditor, InkEditor]);
	this.#uiManager = options.uiManager;
	this.annotationStorage = options.annotationStorage;
	this.pageIndex = options.pageIndex;
	this.div = options.div;
	this.#accessibilityManager = options.accessibilityManager;
	this.#uiManager.addLayer(this);
	}

/cc @calixteman, @marco-c This seems like a pretty serious usability issue, and it's possible that this is also the same bug as outlined in https://www.reddit.com/r/firefox/comments/yxlgx3/how_to_actually_save_an_edited_pdf/

[calixteman]

Naively, it seems to me that we should probably serialize the applicable editors when destroying the layer in

Good idea.

/cc @calixteman, @marco-c This seems like a pretty serious usability issue, and it's possible that this is also the same bug as outlined in https://www.reddit.com/r/firefox/comments/yxlgx3/how_to_actually_save_an_edited_pdf/

It's very likely the same issue.