Ensure that the /Properties, used with optional content, is actually loaded *before* parsing the operatorList/textContent (PR 12095 follow-up)
Ensure that the /Properties, used with optional content, is actually loaded *before* parsing the operatorList/textContent (PR 12095 follow-up)

By not waiting for the /Properties to load, before parsing of the operatorList/textContent starts, there's a very real risk that a `MissingDataException` will be thrown when trying to access the data in the `PartialEvaluator.parseMarkedContentProps` method.
If this ever happens it will thus lead to incomplete and/or outright broken rendering, and with e.g. `disableAutoFetch=true` set the likelihood of this occuring would increase quite a bit.

*Please note:* While I've not yet seen this error in an actual PDF document, it can happen during loading if you're unlucky enough with e.g. the structure of the PDF document and/or the download speed offered by the server.

Snuffleupagus/pdf.js,showpad/mozilla-pdf.js,timvandermeij/pdf.js,timvandermeij/pdf.js,macroplant/pdf.js,nawawi/pdf.js,xavier114fch/pdf.js,Shoobx/pdf.js,Snuffleupagus/pdf.js,Shoobx/pdf.js,macroplant/pdf.js,showpad/mozilla-pdf.js,xavier114fch/pdf.js,mozilla/pdf.js,mozilla/pdf.js,timvandermeij/pdf.js,Snuffleupagus/pdf.js,mozilla/pdf.js,nawawi/pdf.js,nawawi/pdf.js,macroplant/pdf.js,Shoobx/pdf.js,showpad/mozilla-pdf.js