Send/receive Type3 images the same way as other globally-cached images

There's quite frankly no particular reason to special-case Type3-fonts with image resources, which are very rare anyway, now that we have a general mechanism for sending/receiving images globally.
mozilla · Jul 26, 2020 · 4fad4d6 · 4fad4d6
1 parent f93f5bc
commit 4fad4d6
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 9 deletions.
diff --git a/src/core/evaluator.js b/src/core/evaluator.js
@@ -455,14 +455,7 @@ class PartialEvaluator {
   _sendImgData(objId, imgData, cacheGlobally = false) {
     const transfers = imgData ? [imgData.data.buffer] : null;
 
-    if (this.parsingType3Font) {
-      return this.handler.send(
-        "commonobj",
-        [objId, "FontType3Res", imgData],
-        transfers
-      );
-    }
-    if (cacheGlobally) {
+    if (this.parsingType3Font || cacheGlobally) {
       return this.handler.send(
         "commonobj",
         [objId, "Image", imgData],

diff --git a/src/display/api.js b/src/display/api.js
@@ -2265,7 +2265,6 @@ class WorkerTransport {
             });
           break;
         case "FontPath":
-        case "FontType3Res":
         case "Image":
           this.commonObjs.resolve(id, exportedData);
           break;