Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
071e6bc7e7
pdf.js/test/test_manifest.json

7688 lines
203 KiB
JSON
Raw Normal View History

Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
[
[api-minor] Don't add in the text content the chars which are out-of-page (bug 1755201) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1755201; - if the glyph position is not within the view then skip it.
2022-02-14 03:39:40 +09:00
{ "id": "bug1755201",
"file": "pdfs/bug1755201.pdf",
"md5": "cece14097812d8a1f69e86a51e4a3804",
"rounds": 1,
"link": true,
"type": "other"
},
Support encoded dest-strings in /GoTo destination dictionaries (issue 14864) Interestingly enough this appears to be the very first case of *encoded* dest-strings, in /GoTo destination dictionaries, that we've actually come across. What's really fascinating is that it's less than a week after issue 14847, given that these issues are *somewhat* similar.
2022-05-02 16:46:44 +09:00
{ "id": "issue14864",
"file": "pdfs/issue14864.pdf",
"md5": "cfe5e68267d1e84ec909a915911974cf",
"rounds": 1,
"link": true,
"type": "other"
},
Implement progressive loading of PDFs
2013-02-07 08:19:29 +09:00
{ "id": "filled-background-range",
"file": "pdfs/filled-background.pdf",
"md5": "2e3120255d9c3e79b96d2543b12d2589",
"rounds": 1,
"type": "eq"
},
test-harness improvements
2011-06-22 06:53:57 +09:00
{ "id": "tracemonkey-eq",
Modify paths of web resources to work with test resources more buried.
2011-06-24 01:48:34 +09:00
"file": "pdfs/tracemonkey.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
"rounds": 1,
test-harness improvements
2011-06-22 06:53:57 +09:00
"type": "eq"
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
},
Add at least *some* test-coverage for the `RenderTask.onContinue` functionality The default viewer, and thus Firefox, depends on the `RenderTask.onContinue` functionality to pause/continue rendering (such that the most visible page always renders first). Despite this functionality thus being very important, it has however never actually been tested *at all* as far as I can tell. Hence this patch which adds a new boolean `renderTaskOnContinue` parameter (`false` by default), that can be used to force a reference-test to use the `RenderTask.onContinue` code-path in the `InternalRenderTask` class. Note that I purposely made this new reference-test behaviour *optional*, since I didn't want to negatively affect the general runtime of the tests (given that there's a slight delay added to the rendering). Also, for e.g. benchmarking you'd most likely want to stay away from the `RenderTask.onContinue` functionality for similar reasons.
2020-06-29 03:14:03 +09:00
{ "id": "tracemonkey-renderTaskOnContinue",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"type": "eq",
"renderTaskOnContinue": true
},
Skip extra objects in object stream in using offsets
2021-03-28 02:45:48 +09:00
{ "id": "issue13130",
"file": "pdfs/issue13130.pdf",
"md5": "318518299132fe3b52252ca43a69a23e",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq"
},
Improve handling of JPEG images with non-standard /Decode-entries (issue 16395) The /Decode-implementation in the our JPEG decoder, i.e. `src/core/jpg.js`, seems to only handle *inverting* of images properly. To support arbitrary /Decode-entries correctly we'll always use the `PDFImage.decodeBuffer` method, even for "simple" JPEG images, which should be fine since non-default /Decode-entries aren't a very common occurrence. *Please note:* This patch will lead to a little bit of movement in some existing test-cases, however it should be virtually imperceivable to the naked eye.
2023-05-06 20:29:42 +09:00
{ "id": "issue16395",
"file": "pdfs/issue16395.pdf",
"md5": "a5de985711ec27cd2a2ed97d5f1c536c",
"rounds": 1,
"link": true,
"firstPage": 3,
"lastPage": 3,
"type": "eq"
},
Attempt to fallback to a default font, for non-available ones, in more cases (issue 16432) This essentially extends PR 11218 to also apply when looking up the final font-reference, via the XRef-table, fails because the font isn't available. This patch also changes `PartialEvaluator.fallbackFontDict` to simply use "Helvetica" as the default font-name, since that seems generally reasonable given the now existing font-substitution code.
2023-05-17 17:19:14 +09:00
{ "id": "issue16432",
"file": "pdfs/issue16432.pdf",
"md5": "b67b0324c307d8af43d11b0edec88e3e",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Ignore named encoding for non-embedded symbol fonts (issue 16464) The affected font is non-embedded ZapfDingbats, however the PDF document for some inexplicable reason specifies the encoding as "WinAnsiEncoding" (which is obviously wrong). To work-around this bug in the PDF generator, we'll simply ignore any explicitly specified named encoding for non-embedded symbol fonts.
2023-05-24 16:52:49 +09:00
{ "id": "issue16464",
"file": "pdfs/issue16464.pdf",
"md5": "2bd97ff909e2185605788daa70de38ee",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
{ "id": "tracemonkey-fbf",
Modify paths of web resources to work with test resources more buried.
2011-06-24 01:48:34 +09:00
"file": "pdfs/tracemonkey.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
"rounds": 2,
"type": "fbf"
},
Adds text layer testing
2012-09-12 08:04:01 +09:00
{ "id": "tracemonkey-text",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"type": "text"
},
[api-minor] Improve pdf reading in high contrast mode - Use Canvas & CanvasText color when they don't have their default value as background and foreground colors. - The colors used to draw (stroke/fill) in a pdf are replaced by the bg/fg ones according to their luminance.
2022-05-04 22:37:13 +09:00
{ "id": "tracemonkey-forced-colors-eq",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"pageColors": {
"background": "black",
"foreground": "#00FF00"
},
"type": "eq"
},
{ "id": "tracemonkey-viewer-colors-eq",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"pageColors": {
"background": "Canvas",
"foreground": "CanvasText"
},
"type": "eq",
"about": "Uses the same pageColors as the viewer."
},
{ "id": "tracemonkey-default-colors-eq",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"pageColors": {
"background": "white",
"foreground": "black"
},
"type": "eq",
"about": "Uses the default colors."
},
Prevent updating the current transformation matrix when the stateStack is empty
2013-11-17 09:51:34 +09:00
{ "id": "issue3925",
"file": "pdfs/issue3925.pdf",
"md5": "c5c895deecf7a7565393587e0d61be2b",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "text"
},
Fallback gracefully when encountering corrupt PDF files with empty /MediaBox and /CropBox entries This is based on a real-world PDF file I encountered very recently[1], although I'm currently unable to recall where I saw it. Note that different PDF viewers handle these sort of errors differently, with Adobe Reader outright failing to render the attached PDF file whereas PDFium mostly handles it "correctly". The patch makes the following notable changes: - Refactor the `cropBox` and `mediaBox` getters, on the `Page`, to reduce unnecessary duplication. (This will also help in the future, if support for extracting additional page bounding boxes are added to the API.) - Ensure that the page bounding boxes, i.e. `cropBox` and `mediaBox`, are never empty to prevent issues/weirdness in the viewer. - Ensure that the `view` getter on the `Page` will never return an empty intersection of the `cropBox` and `mediaBox`. - Add an *optional* parameter to `Util.intersect`, to allow checking that the computed intersection isn't actually empty. - Change `Util.intersect` to have consistent return types, since Arrays are of type `Object` and falling back to returning a `Boolean` thus seem strange. --- [1] In that case I believe that only the `cropBox` was empty, but it seemed like a good idea to attempt to fix a bunch of related cases all at once.
2019-08-08 22:54:46 +09:00
{ "id": "boundingBox_invalid",
"file": "pdfs/boundingBox_invalid.pdf",
"md5": "f6dfc471bf43abac00cdcf05d81cb070",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a work-around, in `glyphlist.js`, for bad PDF generators which use a non-standard `/f_f` string in the `Encoding` dictionary when referring to the ff ligature (issue 11016) This patch will not incur any (measurable) overhead, since the glyphlist is already quite long and one more entry won't really matter, which is important given that this sort of PDF corruption ought to be very rare. Furthermore, this patch purposely does *not* add a bunch of similarly modified ligature names on pure speculation. Any similar additions, for other ligatures, should only be made if there's real-world examples of PDF files where that's actually necessary.
2019-07-30 23:48:27 +09:00
{ "id": "issue11016",
"file": "pdfs/issue11016_reduced.pdf",
"md5": "b75578bd052d2e6acdcc85b615eab6b1",
"rounds": 1,
"link": false,
"type": "text"
},
For Type1 fonts, replace missing font dictionary /Widths entries with ones from the font data (issue 11150) Hopefully this patch makes sense, and in order to reduce the regression risk the implementation ensures that only completely missing widths are being replaced.
2019-09-18 16:44:18 +09:00
{ "id": "issue11150",
"file": "pdfs/issue11150_reduced.pdf",
"md5": "8b86381089a9ec28723791245a9adfa6",
"rounds": 1,
"link": false,
"type": "eq"
},
Extend `getNonStdFontMap` for non-embedded versions of the ItcSymbol font (issue 11532) Despite its name, the fonts in ItcSymbol-family are "regular" fonts and not Symbol ones. However, given that the font name contains the word "Symbol" we ended up picking the wrong code-path in the `Font.fallbackToSystemFont`-method. *Please note:* While this patch ensures that the text becomes readable, by falling back a standard font, the rendering will obviously not be perfect. However, that's the PDF generators "fault" since non-embedded fonts cannot be guaranteed to render correctly in all environments.
2021-09-01 05:37:09 +09:00
{ "id": "issue11532",
"file": "pdfs/issue11532.pdf",
"md5": "9216481d259ae2b8d747236e745cbc80",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq"
},
Always prefer abbreviated keys, over full ones, when doing any dictionary lookups (issue 14256) Note that issue 14256 was specifically about *inline* images, please refer to: - https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G7.1852045 - https://www.pdfa.org/safedocs-unearths-pdf-inline-image-issue/ - https://pdf-issues.pdfa.org/32000-2-2020/clause08.html#H8.9.7 However, during review of the initial PR in https://github.com/mozilla/pdf.js/pull/14257#issuecomment-964469710, it was suggested that we instead do this *unconditionally for all* dictionary lookups. In addition to re-ordering the existing call-sites in the `src/core`-code, and adding non-PRODUCTION/TESTING asserts to catch future errors, for consistency a number of existing `if`/`switch`-blocks were re-factored to also check the abbreviated keys first.
2021-11-10 06:39:21 +09:00
{ "id": "issue14256",
"file": "pdfs/issue14256.pdf",
"md5": "15938b7562146dbea7ed8aa15b172fe6",
"rounds": 1,
"type": "eq"
},
Ignore non-Stream /SMask-entries when parsing images (issue 14814) This is similar to the pre-existing check used in the /Mask-case below, to handle *corrupt* PDF documents that include non-Stream /SMask-entries in images; please refer to the PDF specification: https://web.archive.org/web/20220309040754if_/https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#page=216 *Please note:* Adobe Reader also fails to render the image on the second page, and displays an error message.
2022-04-21 18:57:12 +09:00
{ "id": "issue14814",
"file": "pdfs/issue14814.pdf",
"md5": "a1c8b677335ff5ea0d07e35e7dffb6e8",
"rounds": 1,
"firstPage": 2,
"type": "eq"
},
When parsing corrupt documents without any trailer-dictionary, fallback to the "top"-dictionary (issue 14269) There's obviously no guarantee that this will work in general, if the document is sufficiently corrupt, but it should hopefully be better than just throwing `InvalidPDFException` as currently happens. Please note that, as is often the case with corrupt documents, it's somewhat difficult to know if we're rendering the document "correctly" with this patch[1]. In this case even Adobe Reader cannot open the document, which is always a good sign that it's *really* corrupt, however we're at least able to render *something* with this patch. --- [1] Whatever "correct" even means when dealing with corrupt PDF documents, where often times different PDF viewers won't agree completely.
2021-11-13 21:06:21 +09:00
{ "id": "issue14269",
"file": "pdfs/issue14269.pdf",
"md5": "f34abf77a418f54e13fbcd03b063432e",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Support images with /Filter-entries that contain Arrays (issue 15220) This patch "borrows" the code found in the `Parser.makeInlineImage`-method, to ensure that JBIG2 and JPX images can be rendered correctly.
2022-07-25 15:34:28 +09:00
{ "id": "issue15220",
"file": "pdfs/issue15220.pdf",
"md5": "0864a9e3860c0cb5e98b5eb23287fba4",
"rounds": 1,
"link": true,
Fallback to a standard font when a Type1 font program is empty (issue 15292) *Please note:* This is only a, hopefully generally helpful, work-around rather than a proper solution to issue 15292. There's something that's "special" about the Type1 fonts in the referenced PDF document, since we don't manage to find any actual font programs and thus cannot render anything. Given that it shouldn't make sense for a Type1 font program to ever be empty, since that means that there's no glyph-data to render, we simply fallback to a standard font to at least try and render *something* in these rare cases.
2022-09-05 18:56:02 +09:00
"lastPage": 1,
"type": "eq"
},
{ "id": "issue15292",
"file": "pdfs/issue15292.pdf",
"md5": "24297e183bf16cdd684dac8902e9fbe6",
"rounds": 1,
"link": true,
Support images with /Filter-entries that contain Arrays (issue 15220) This patch "borrows" the code found in the `Parser.makeInlineImage`-method, to ensure that JBIG2 and JPX images can be rendered correctly.
2022-07-25 15:34:28 +09:00
"lastPage": 1,
"type": "eq"
},
Allow skipping of errors when reading broken/corrupt ToUnicode data (issue 11549) This will allow font loading/parsing to continue, rather than immediately failing, when broken/corrupt CMap data is encountered.
2020-01-30 21:13:51 +09:00
{ "id": "issue11549",
"file": "pdfs/issue11549_reduced.pdf",
"md5": "a1ea636f413e02e10dbdf379ab4a99ae",
"rounds": 1,
"link": false,
"type": "eq"
},
Ensure that there's always a setFont (Tf) operator before text rendering operators (issue 11651) The PDF document in question is *corrupt*, since it contains multiple instances of incorrect operators. We obviously don't want to slow down parsing of *all* documents (since most are valid), just to accommodate a particular bad PDF generator, hence the reason for the inline check before calling the `ensureStateFont` method.
2020-03-02 23:34:00 +09:00
{ "id": "issue11651-eq",
"file": "pdfs/issue11651.pdf",
"md5": "375233ad8dc4181a06148f8412f35b91",
"rounds": 1,
"link": false,
"type": "eq"
},
{ "id": "issue11651-text",
"file": "pdfs/issue11651.pdf",
"md5": "375233ad8dc4181a06148f8412f35b91",
"rounds": 1,
"link": false,
"type": "text"
},
Enable loading of PDFs with undefined or missing stream lengths
2013-08-16 23:32:40 +09:00
{ "id": "issue1293",
Replace the linked test-case for issue 1293 with a reduced test-case When I submitted PR 3576, I included a linked test-case. The reason was that I didn't know enough about the PDF format, in order to successfully create a reduced test-case. Considering that the link points to a Dropbox, there's no guarantee that the PDF file will remain available, hence it seems worthwhile to replace the test-case. *Note:* Since this is a `load` test, `makeref` won't be necessary.
2015-10-28 02:20:29 +09:00
"file": "pdfs/issue1293r.pdf",
"md5": "4a098f5051f34fab036f5bbe88f8deef",
Enable loading of PDFs with undefined or missing stream lengths
2013-08-16 23:32:40 +09:00
"rounds": 1,
Replace the linked test-case for issue 1293 with a reduced test-case When I submitted PR 3576, I included a linked test-case. The reason was that I didn't know enough about the PDF format, in order to successfully create a reduced test-case. Considering that the link points to a Dropbox, there's no guarantee that the PDF file will remain available, hence it seems worthwhile to replace the test-case. *Note:* Since this is a `load` test, `makeref` won't be necessary.
2015-10-28 02:20:29 +09:00
"link": false,
Enable loading of PDFs with undefined or missing stream lengths
2013-08-16 23:32:40 +09:00
"type": "load",
"about": "PDF with undefined stream length."
},
Remove glyph id's outside the range of valid glyphs. OTS does not like invalid glyph ids in a camp table.
2015-12-03 09:47:20 +09:00
{ "id": "issue5564_reduced",
"file": "pdfs/issue5564_reduced.pdf",
"md5": "097853614b56fc10bfbf7e56daa0c66b",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"about": "Causes cmap to be created with invalid glyph ids."
},
Support strokeAlpha/fillAlpha when creating a fallback appearance stream (issue 6810) This fixes the colours, by respecting the strokeAlpha/fillAlpha-values, for a couple of Annotations in the PDF document from issue 13447.[1] --- [1] Some of the annotations still won't render at all, when compared with Adobe Reader, but that could/should probably be handled separately.
2021-05-27 17:06:13 +09:00
{ "id": "issue13447-eq",
"file": "pdfs/issue13447.pdf",
"md5": "a729709950d69ec1cfc516bf559e995d",
"rounds": 1,
"type": "eq"
},
{ "id": "issue13447-annotations",
"file": "pdfs/issue13447.pdf",
"md5": "a729709950d69ec1cfc516bf559e995d",
"rounds": 1,
"type": "eq",
"annotations": true
},
Support rich content in markup annotation - use the xfa parser but in the xhtml namespace.
2021-10-25 00:29:30 +09:00
{ "id": "issue2966",
"file": "pdfs/rc_annotation.pdf",
"md5": "7b978a8c2871b8902656adb67f7bd117",
"rounds": 1,
"lastPage": 1,
"type": "eq",
"annotations": true
},
{ "id": "issue13915",
"file": "pdfs/issue13915.pdf",
"md5": "fef3108733bbf80ea8551feedb427b1c",
"rounds": 1,
"firstPage": 51,
"lastPage": 51,
"link": true,
"type": "eq",
"annotations": true
Add even more non-standard ligatures (PR 15517 follow-up) Given that we already create multi-byte ToUnicode entries in other cases, see e.g. the `getNormalizedUnicodes` table, this is hopefully fine.
2023-03-22 18:40:12 +09:00
},
{ "id": "issue15516",
"file": "pdfs/issue15516_reduced.pdf",
"md5": "a30be78c73d13aa6ff890834ce69adc1",
"rounds": 1,
"link": false,
"type": "text"
},
Fix loading of fonts that are not referenced by an object identifier
2013-12-17 08:19:31 +09:00
{ "id": "bug946506",
"file": "pdfs/bug946506.pdf",
"md5": "c28911b5c31bdc337c2ce404c5971cfc",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"about": "Fonts referenced only by name and not by an object identifier."
},
Take into account the final space if any in the TJ command The final space was just ignored and that led to wrongly position the next chunk of text.
2023-05-24 00:09:23 +09:00
{ "id": "bug946506-text",
"file": "pdfs/bug946506.pdf",
"md5": "c28911b5c31bdc337c2ce404c5971cfc",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "text"
},
Don't consider space as real space when there is an extra spacing (bug 931481) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=931481; - real space chars are pushed in the chunk but when there is an extra spacing, the next char position must be compared with the previous one; - for example, an extra spacing can cancel a space so visually there are no space.
2021-11-13 02:04:17 +09:00
{ "id": "bug931481",
"file": "pdfs/bug931481.pdf",
"md5": "547de872cbb2ecc653ae83d5be7e5be9",
"rounds": 1,
"link": true,
"type": "text"
},
Don't map glyphs to certain problematic General Punctuation Unicode locations (bug 911034) Fixes the remaining missing characters in https://bugzilla.mozilla.org/show_bug.cgi?id=911034. For reference, see http://www.unicode.org/charts/PDF/U2000.pdf (and also http://en.wikipedia.org/wiki/General_Punctuation_%28Unicode_block%29).
2015-04-09 23:09:24 +09:00
{ "id": "bug911034",
"file": "pdfs/bug911034.pdf",
"md5": "54ee432a4e16b26b242fbf549cdad177",
"rounds": 1,
"link": false,
"type": "eq"
},
Support CMap-data with only strings, when parsing TrueType composite fonts (bug 920426) In the referenced bug, the embedded fonts contain custom CMap-data that only include strings. Note how for embedded composite TrueType fonts we're using the CMap-data when building the glyph mapping, and currently we end up with a completely empty map because the code expects only CID *numbers*. Furthermore, just fixing the glyph mapping alone isn't sufficient to fully address the bug, since we also need to consider this "special" kind of CMap-data when looking up glyph widths.
2021-09-22 07:44:12 +09:00
{ "id": "bug920426",
"file": "pdfs/bug920426.pdf",
"md5": "2fd118b44513afb22509c3584388cc29",
"rounds": 1,
"type": "eq"
},
Use correct matrix for patterns with showText. We were incorrectly using the transform in the pattern before it had been adjusted causing the pattern to be misplaced relative to the page. Fixes: ShowText-ShadingPattern.pdf (already in corpus) Fixes: #8111 Fixes: #9243
2021-11-05 08:45:48 +09:00
{ "id": "issue8111",
"file": "pdfs/issue8111.pdf",
"md5": "14a2b3c19ed3d6cd7e138cdc141aa4a8",
"rounds": 1,
"type": "eq"
},
Take the `W` array into account when computing the hash, in `PartialEvaluator.preEvaluateFont`, for composite fonts (issue 13343) Without this some *composite* fonts may incorrectly end up with matching `hash`es, thus breaking rendering since we'll not actually try to load/parse some of the fonts. *Please note:* Given that the document, in the referenced issue, doesn't embed *any* of its fonts there's no guarantee that it renders correctly in all configurations even with this patch.
2021-05-07 18:49:58 +09:00
{ "id": "issue13343",
"file": "pdfs/issue13343.pdf",
"md5": "f8bf1888839e15254555092c504e1900",
"rounds": 1,
"type": "eq"
},
Take the /CIDToGIDMap data into account when computing the hash, in `PartialEvaluator.preEvaluateFont`, for composite fonts (bug 1734802) This is unfortunately *yet another* bug in the `preEvaluateFont`-implementation, and I've lost count of the number of times I've had to tweak this code over the years :-( I really cannot help thinking that PR 4423 was way too simplistic, since it missed a bunch of cases that leads to broken font rendering in many PDF documents. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1734802
2021-10-08 19:21:26 +09:00
{ "id": "bug1734802",
"file": "pdfs/bug1734802.pdf",
"md5": "a23ad8af95ffca3876e110a5f4dec9bc",
"rounds": 1,
"link": true,
"lastPage": 3,
"type": "eq"
},
Let `Lexer.getNumber` treat a single minus sign as zero (bug 1753983) This appears to be consistent with the behaviour in both Adobe Reader and PDFium (in Google Chrome); this is essentially the same approach as used for a single decimal point in PR 9827.
2022-02-08 00:14:45 +09:00
{ "id": "bug1753983",
"file": "pdfs/bug1753983.pdf",
"md5": "432be86262e5071176c49713ce458031",
"rounds": 1,
"link": true,
"type": "eq"
},
Let `Lexer.getNumber` treat more invalid "numbers" as zero (issue 15604) In the referenced PDF document there are "numbers" which consist only of `-.`, and while that's obviously not valid Adobe Reader seems to handle it just fine. Letting this method ignore more invalid "numbers" was suggested during the review of PR 14543, so let's simply relax our the validation here.
2022-10-21 02:40:25 +09:00
{ "id": "issue15604",
"file": "pdfs/issue15604.pdf",
"md5": "505040e5634434ae97118a4c39bf27e5",
"rounds": 1,
"link": true,
"type": "eq"
},
Adds glyph mapping for standard fonts
2014-01-04 05:17:50 +09:00
{ "id": "bug921760",
"file": "pdfs/bug921760.pdf",
"md5": "1aa136d786a65b0d7cce7bdb3c58c6c3",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Fix undefined group bounding box
2013-11-05 02:16:33 +09:00
{ "id": "issue3879",
Replace the linked test-case for issue 3879 with a reduced test-case Re: issue 3879 and PR 3880.
2015-11-01 20:38:59 +09:00
"file": "pdfs/issue3879r.pdf",
"md5": "756cdaf5eb54c7d78b0aa737236b9a4f",
Fix undefined group bounding box
2013-11-05 02:16:33 +09:00
"rounds": 1,
Replace the linked test-case for issue 3879 with a reduced test-case Re: issue 3879 and PR 3880.
2015-11-01 20:38:59 +09:00
"link": false,
Fix undefined group bounding box
2013-11-05 02:16:33 +09:00
"type": "eq"
},
Add pdf from issue 3885 to tests Source: https://www.dropbox.com/s/ooqk82fq0gr5p6f/test-min-notext-opt.pdf
2013-12-18 05:32:24 +09:00
{ "id": "issue3885",
"file": "pdfs/issue3885.pdf",
"md5": "319c998910453bc44d40c7748cd2cb79",
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Fixes reading Type1 FontBBox data for usWin values
2013-11-02 01:33:30 +09:00
{ "id": "issue2833",
"file": "pdfs/issue2833.pdf",
"md5": "7bc6e17c41586155c188d7408bcb9ab5",
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Test for issue #2881
2013-05-10 11:57:00 +09:00
{ "id": "issue2881",
"file": "pdfs/issue2881.pdf",
"md5": "ea6ade27d2cb146676d23dcd6605d5ee",
"link": "true",
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
calgray: fix getRgbBuffer problem This fixes issue 3903.
2014-01-02 06:46:27 +09:00
{ "id": "issue3903",
"file": "pdfs/issue3903.pdf",
"md5": "c9a4a8012e15cf3b10d671982ce35a92",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Map all glyphs to the private use area and duplicate the first glyph. There have been lots of problems with trying to map glyphs to their unicode values. It's more reliable to just use the private use areas so the browser's font renderer doesn't mess with the glyphs. Using the private use area for all glyphs did highlight other issues that this patch also had to fix: * small private use area - Previously, only the BMP private use area was used which can't map many glyphs. Now, the (much bigger) PUP 16 area can also be used. * glyph zero not shown - Browsers will not use the glyph from a font if it is glyph id = 0. This issue was less prevalent when we mapped to unicode values since the fallback font would be used. However, when using the private use area, the glyph would not be drawn at all. This is illustrated in one of the current test cases (issue #8234) where there's an "ä" glyph at position zero. The PDF looked like it rendered correctly, but it was actually not using the glyph from the font. To properly show the first glyph it is always duplicated and appended to the glyphs and the maps are adjusted. * supplementary characters - The private use area PUP 16 is 4 bytes, so String.fromCodePoint must be used where we previously used String.fromCharCode. This is actually an issue that should have been fixed regardless of this patch. * charset - Freetype fails to load fonts when the charset size doesn't match number of glyphs in the font. We now write out a fake charset with the correct length. This also brought up the issue that glyphs with seac/endchar should only ever write a standard charset, but we now write a custom one. To get around this the seac analysis is permanently enabled so those glyphs are instead always drawn as two glyphs.
2018-01-05 07:43:07 +09:00
{ "id": "issue8795_reduced",
"file": "pdfs/issue8795_reduced.pdf",
"md5": "3ce58fa4aff351d46c42e0677d582099",
"rounds": 1,
"type": "eq"
},
Skip commands that have too few arguments - Commands that have too few args will be skipped - Commands that have too many args will generate an info, but still execute
2013-01-11 11:00:44 +09:00
{ "id": "issue2391-1",
"file": "pdfs/issue2391-1.pdf",
"md5": "25ae9cb959612e7b343b55da63af2716",
"rounds": 1,
Error, rather than warn, once a number of invalid path operators are encountered in `EvaluatorPreprocessor.read` (bug 1443140) Incomplete path operators, in particular, can result in fairly chaotic rendering artifacts, as can be observed on page four of the referenced PDF file. The initial (naive) solution that was attempted, was to simply throw a `FormatError` as soon as any invalid (i.e. too short) operator was found and rely on the existing `ignoreErrors` code-paths. However, doing so would have caused regressions in some files; see the existing `issue2391-1` test-case, which was promoted to an `eq` test to help prevent future bugs. Hence this patch, which adds special handling for invalid path operators since those may cause quite bad rendering artifacts. You could, in all fairness, argue that the patch is a handwavy solution and I wouldn't object. However, given that this only concerns *corrupt* PDF files, the way that PDF viewers (PDF.js included) try to gracefully deal with those could probably be described as a best-effort solution anyway. This patch also adjusts the existing `warn`/`info` messages to print the command name according to the PDF specification, rather than an internal PDF.js enumeration value. The former should be much more useful for debugging purposes. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1443140.
2018-06-24 16:53:32 +09:00
"type": "eq"
Skip commands that have too few arguments - Commands that have too few args will be skipped - Commands that have too many args will generate an info, but still execute
2013-01-11 11:00:44 +09:00
},
Default to a built-in font if an invalid non-embedded font is encountered
2013-01-12 04:04:56 +09:00
{ "id": "issue2391-2",
"file": "pdfs/issue2391-2.pdf",
"md5": "7e68756d11021a087383eaac95ba45dd",
"rounds": 1,
"type": "eq"
},
Error, rather than warn, once a number of invalid path operators are encountered in `EvaluatorPreprocessor.read` (bug 1443140) Incomplete path operators, in particular, can result in fairly chaotic rendering artifacts, as can be observed on page four of the referenced PDF file. The initial (naive) solution that was attempted, was to simply throw a `FormatError` as soon as any invalid (i.e. too short) operator was found and rely on the existing `ignoreErrors` code-paths. However, doing so would have caused regressions in some files; see the existing `issue2391-1` test-case, which was promoted to an `eq` test to help prevent future bugs. Hence this patch, which adds special handling for invalid path operators since those may cause quite bad rendering artifacts. You could, in all fairness, argue that the patch is a handwavy solution and I wouldn't object. However, given that this only concerns *corrupt* PDF files, the way that PDF viewers (PDF.js included) try to gracefully deal with those could probably be described as a best-effort solution anyway. This patch also adjusts the existing `warn`/`info` messages to print the command name according to the PDF specification, rather than an internal PDF.js enumeration value. The former should be much more useful for debugging purposes. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1443140.
2018-06-24 16:53:32 +09:00
{ "id": "bug1443140",
"file": "pdfs/bug1443140.pdf",
"md5": "8f9347b0d5620537850b24b8385b0982",
"rounds": 1,
"link": true,
"firstPage": 4,
"lastPage": 4,
"type": "eq"
},
Prevent errors in `sanitizeTTProgram`, during parsing of CALL functions, when encountering invalid functions stack deltas (bug 1473809) *I was feeling bored; so this is a very quick, and somewhat naive, attempt at fixing the bug.* The breaking error, i.e. `Error during font loading: invalid array length`, was thrown when attempting to re-size the `stack` to a *negative* length when parsing the CALL functions. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1473809.
2018-07-10 05:11:46 +09:00
{ "id": "bug1473809",
"file": "pdfs/bug1473809.pdf",
"md5": "4b1ca51cf8cad58a1ce0618667341c76",
"rounds": 1,
"link": false,
"type": "eq"
},
Fix invalid version number in truetype 'head' table
2013-01-19 08:06:12 +09:00
{ "id": "issue2531",
"file": "pdfs/issue2531.pdf",
"md5": "c58e6642d8a6e2ddd5e07a543ef8f30d",
"link": true,
"rounds": 1,
Sanitization of truetype fonts to fix #2537
2013-01-23 03:46:54 +09:00
"firstPage": 4,
"lastPage": 4,
"type": "eq"
},
Support parsing encrypted documents in `XRef.indexObjects` (issue 15893) *Please note:* The reduced test-case is *not* a perfect reproduction of the original PDF document, since this one fails to open in e.g. Adobe Reader, but I do believe that it captures the most important points here. For corrupt *and* encrypted PDF documents, it's possible that only some trailer dictionaries actually contain an /Encrypt-entry. Previously we'd could easily miss that, since we generally pick the first not obviously corrupt trailer dictionary, and the solution implemented here is to simply pre-parse all trailer dictionaries to see if there's any /Encrypt-entries.
2023-01-06 18:27:20 +09:00
{ "id": "issue15893_reduced",
"file": "pdfs/issue15893_reduced.pdf",
"md5": "cf889b927f9f53d164622a99378bf39d",
"rounds": 1,
"type": "eq",
"password": "test"
},
Only use base encoding if it's populated. (bug 1727053) The font dict in this file has an encoding entry, but only specifies a differences map. The base encoding is empty in this case and shouldn't be used.
2021-08-31 04:51:59 +09:00
{ "id": "bug1727053",
"file": "pdfs/bug1727053.pdf",
"md5": "8ed1e52da64000f9fdcb8b732f5a58f8",
"rounds": 1,
"type": "eq"
},
[JBIG2] Fix getting decodeParms when it's an array
2013-12-20 04:23:58 +09:00
{ "id": "issue3999",
"file": "pdfs/issue3999.pdf",
"md5": "0a59cd612e93758aa9f104470f45574b",
"link": true,
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Sanitization of truetype fonts to fix #2537
2013-01-23 03:46:54 +09:00
{ "id": "issue2537",
Missing test for #2537 (e4c3b4501dffe5bd)
2014-05-03 04:04:16 +09:00
"file": "pdfs/issue2537r.pdf",
"md5": "0f47a8bda08eebd986c254e65dcc2a76",
Sanitization of truetype fonts to fix #2537
2013-01-23 03:46:54 +09:00
"rounds": 1,
Fix invalid version number in truetype 'head' table
2013-01-19 08:06:12 +09:00
"type": "eq"
},
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
{ "id": "html5-canvas-cheat-sheet-load",
Modify paths of web resources to work with test resources more buried.
2011-06-24 01:48:34 +09:00
"file": "pdfs/canvas.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "59510028561daf62e00bf9f6f066b033",
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
"rounds": 1,
"type": "load"
add support for linking pdfs we can't/won't distribute
2011-06-22 07:14:42 +09:00
},
Compute the loca table `endOffset`, of the "first" glyph, correctly (issue 14618) When there are *multiple* empty glyphs at the start of the data, ensure that the "first" glyph gets a correct `endOffset` to avoid skipping it during parsing in the `sanitizeGlyph` function.
2022-03-03 22:14:22 +09:00
{ "id": "issue14618",
"file": "pdfs/issue14618.pdf",
"md5": "8a4a5aac59519228019aaffdfbd56f17",
"rounds": 1,
"type": "eq"
},
Correct stroke width for text; convert intel-load test to eq-test
2011-12-23 08:43:14 +09:00
{ "id": "intelisa-eq",
add Intel ISA doc as load test, and make harness resilient to bad PDF loads
2011-06-25 11:23:29 +09:00
"file": "pdfs/intelisa.pdf",
Clean up test PDF references
2013-12-17 09:37:10 +09:00
"md5": "24643ebe348a568cfe6a532055c71493",
add Intel ISA doc as load test, and make harness resilient to bad PDF loads
2011-06-25 11:23:29 +09:00
"link": true,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 100,
add Intel ISA doc as load test, and make harness resilient to bad PDF loads
2011-06-25 11:23:29 +09:00
"rounds": 1,
Correct stroke width for text; convert intel-load test to eq-test
2011-12-23 08:43:14 +09:00
"type": "eq"
add Intel ISA doc as load test, and make harness resilient to bad PDF loads
2011-06-25 11:23:29 +09:00
},
Add support for GBK-EUC-H encoding for cid fonts
2013-01-30 06:16:54 +09:00
{ "id": "issue2128",
Replace the unavailable linked test-case for issue 2128 with a reduced test-case Re: issue 2128 and PR 2628.
2015-11-09 20:57:20 +09:00
"file": "pdfs/issue2128r.pdf",
"md5": "64118f4e74590b88bd476b4178a516d5",
"link": false,
Add support for GBK-EUC-H encoding for cid fonts
2013-01-30 06:16:54 +09:00
"rounds": 1,
"type": "eq"
},
Implement 9.6.6.4 of pdf spec for truetype fonts
2013-01-31 03:01:32 +09:00
{ "id": "german-umlaut",
Replace the unavailable linked test-cases for PR 2606 with reduced test-cases Re: PR 2606.
2015-11-16 21:15:36 +09:00
"file": "pdfs/german-umlaut-r.pdf",
"md5": "baa2cd74c76473cf7b914a17403a7f9a",
"link": false,
Implement 9.6.6.4 of pdf spec for truetype fonts
2013-01-31 03:01:32 +09:00
"rounds": 1,
"type": "eq"
},
Fix loading of fonts with invalid encoding name entry (bug 859204 and 878112)
2014-01-21 09:44:46 +09:00
{ "id": "bug859204",
"file": "pdfs/bug859204.pdf",
"md5": "ac1ea1dbfa6ac9d5b13167483049af0b",
"link": false,
"rounds": 1,
"type": "eq"
},
Extend `getGlyphMapForStandardFonts` with some quote-entries (issue 15441)
2022-09-15 18:35:21 +09:00
{ "id": "issue15441",
"file": "pdfs/issue15441.pdf",
"md5": "4a30ea4c8d32fc7dee2a26f78b24966e",
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for bug 1027533
2014-07-29 23:48:01 +09:00
{ "id": "bug1027533",
"file": "pdfs/bug1027533.pdf",
"md5": "07235b2bb0e03f8d727072d48fae3b0a",
"rounds": 1,
"link": false,
"type": "eq"
},
[CIDFontType2] Map characters missing in toUnicode to the private use area (bug 1028735 and issue 4881)
2014-06-28 19:38:25 +09:00
{ "id": "bug1028735",
"file": "pdfs/bug1028735.pdf",
"md5": "5d1a2a87d176ff3b24e66af3cb2365be",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Prevent adding invalid values in `CFFDict_setByKey` (bug 1068432) In the font in question, there are a couple of `topDict` entries that have invalid values (`0xF 0xF`, i.e. just eof markers without any actual numbers). This causes the `parseFloatOperand` function, inside `CFFParser_parseDict`, to return `NaN`. Currently we pass this broken font onto the browser, which OTS unsurprisingly rejects. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1068432.
2016-05-08 01:23:47 +09:00
{ "id": "bug1068432",
"file": "pdfs/bug1068432.pdf",
"md5": "b76ac8d7d0ef471f28535c881f421e33",
"rounds": 1,
"link": false,
"type": "eq"
},
Attempt to recover valid `format 3` FDSelect data from broken CFF fonts (bug 1146106) According to the CFF specification, see http://partners.adobe.com/public/developer/en/font/5176.CFF.pdf#G3.46884, for `format 3` FDSelect data: "The first range must have a ‘first’ GID of 0". Since the PDF file (attached in the bug) violates that part of the specification, this patch tries to recover valid FDSelect data to prevent OTS from rejecting the font. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1146106.
2016-05-27 00:34:00 +09:00
{ "id": "bug1146106",
"file": "pdfs/bug1146106.pdf",
"md5": "a323d3766da49ee40f7d5dff0aeb0cc1",
"rounds": 1,
"link": false,
"type": "eq"
},
Implement 9.6.6.4 of pdf spec for truetype fonts
2013-01-31 03:01:32 +09:00
{ "id": "issue1512",
Replace the unavailable linked test-cases for PR 2606 with reduced test-cases Re: PR 2606.
2015-11-16 21:15:36 +09:00
"file": "pdfs/issue1512r.pdf",
"md5": "af48ede2658d99cca423147085c6609b",
"link": false,
Implement 9.6.6.4 of pdf spec for truetype fonts
2013-01-31 03:01:32 +09:00
"rounds": 1,
"type": "eq"
},
add support for linking pdfs we can't/won't distribute
2011-06-22 07:14:42 +09:00
{ "id": "pdfspec-load",
Modify paths of web resources to work with test resources more buried.
2011-06-24 01:48:34 +09:00
"file": "pdfs/pdf.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "dbdb23c939d2be09b43126c3c56060c7",
add support for linking pdfs we can't/won't distribute
2011-06-22 07:14:42 +09:00
"link": true,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 500,
add support for linking pdfs we can't/won't distribute
2011-06-22 07:14:42 +09:00
"rounds": 1,
"type": "load"
Support for multi-size page PDFs
2011-06-26 23:15:33 +09:00
},
Do not error when an EndOfPage segment is encountered in jbig2
2013-01-16 08:04:05 +09:00
{ "id": "issue2129",
"file": "pdfs/issue2129.pdf",
"md5": "b082dd2cb3648f979fd668f498af14d6",
"link": true,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 1,
Do not error when an EndOfPage segment is encountered in jbig2
2013-01-16 08:04:05 +09:00
"rounds": 1,
"type": "load"
},
add unicode test
2011-07-06 02:21:28 +09:00
{ "id": "shavian-load",
"file": "pdfs/shavian.pdf",
Clean up test PDF references
2013-12-17 09:37:10 +09:00
"md5": "4fabf0a03e82693007435020bc446f9b",
add unicode test
2011-07-06 02:21:28 +09:00
"link": true,
"rounds": 1,
"type": "load"
},
Support for multi-size page PDFs
2011-06-26 23:15:33 +09:00
{ "id": "sizes",
"file": "pdfs/sizes.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "c101ba7b44aee36048e1ac7b98f302ea",
Support for multi-size page PDFs
2011-06-26 23:15:33 +09:00
"rounds": 1,
"type": "eq"
openweb-cover test
2011-06-28 10:13:11 +09:00
},
Fixing DescendantFonts object fetching (#600)
2011-10-08 12:46:01 +09:00
{ "id": "plusminus",
"file": "pdfs/Test-plusminus.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "1ec7ade5b95ac9aaba3a618af28d34c7",
Fixing DescendantFonts object fetching (#600)
2011-10-08 12:46:01 +09:00
"rounds": 1,
"type": "eq"
},
Add support for MMType1 fonts with embedded font files
2014-09-18 23:10:46 +09:00
{ "id": "mmtype1",
"file": "pdfs/mmtype1.pdf",
"md5": "7d632263d28bc2ff05ee0cc426966a5a",
"link": false,
"rounds": 1,
"type": "eq"
},
Added sample OpenOffice file to tests
2011-07-06 08:43:47 +09:00
{ "id": "openoffice-pdf",
Replace the unavailable linked test-case for PR 197 with a reduced test-case Re: PR 197. *Note:* Since this is a `load` test, `makeref` won't be necessary.
2015-11-16 04:07:54 +09:00
"file": "pdfs/openoffice.pdf",
"md5": "ecb0225c7ce2df2cd9a5323a349f8f84",
"link": false,
Added sample OpenOffice file to tests
2011-07-06 08:43:47 +09:00
"rounds": 1,
"type": "load"
Add and wire in test files
2011-07-13 17:55:13 +09:00
},
{ "id": "openofficecidtruetype-pdf",
"file": "pdfs/arial_unicode_en_cidfont.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "03591cdf20214fb0b2dd5e5c3dd32d8c",
Add and wire in test files
2011-07-13 17:55:13 +09:00
"rounds": 1,
"type": "load"
},
{ "id": "openofficearabiccidtruetype-pdf",
"file": "pdfs/arial_unicode_ab_cidfont.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "35090fa7d29e7196ae3421812e554988",
Add and wire in test files
2011-07-13 17:55:13 +09:00
"rounds": 1,
"type": "load"
},
{ "id": "arabiccidtruetype-pdf",
"file": "pdfs/ArabicCIDTrueType.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "d66dbd18bdb572d3ac8b88b32de2ece6",
Add and wire in test files
2011-07-13 17:55:13 +09:00
"rounds": 1,
"type": "load"
link to AESV2 encrypted file
2011-07-21 13:17:31 +09:00
},
Fix tiling pattern with smask. After drawing a tiling pattern we were not calling endDrawing, which handles compositing any active smasks. Fixes #8565.
2021-05-13 03:41:36 +09:00
{ "id": "issue8565",
"file": "pdfs/issue8565.pdf",
"md5": "84e0e2fc2775bc489beac475503dd67b",
"rounds": 1,
"type": "eq"
},
Add test coverage for simpletype3font test PDF
2012-09-15 03:37:00 +09:00
{ "id": "arabiccidtruetype-text",
"file": "pdfs/ArabicCIDTrueType.pdf",
"md5": "d66dbd18bdb572d3ac8b88b32de2ece6",
"rounds": 1,
"type": "text"
},
Change the way Type 2 CID fonts are encoded. Move the cmap glyphs above the first 255 unicode values so that fillText does not change them and create an encoding to map characters to the glyphs.
2011-08-19 22:04:34 +09:00
{ "id": "complexttffont-pdf",
"file": "pdfs/complex_ttf_font.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "76de93f9116b01b693bf8583b3e76d91",
Change the way Type 2 CID fonts are encoded. Move the cmap glyphs above the first 255 unicode values so that fillText does not change them and create an encoding to map characters to the glyphs.
2011-08-19 22:04:34 +09:00
"rounds": 1,
"type": "load"
},
Display widget signature - but don't validate them for now; - Firefox will display a bar to warn that the signature validation is not supported (see https://bugzilla.mozilla.org/show_bug.cgi?id=854315) - almost all (all ?) pdf readers display signatures; - validation is done in edge but for now it's behind a pref.
2021-04-10 23:53:17 +09:00
{ "id": "bug854315",
"file": "pdfs/bug854315.pdf",
"md5": "675754c07f71c068d2997905a5456f05",
"rounds": 1,
"type": "eq"
},
Resizes loca table when needed
2013-11-03 08:56:48 +09:00
{ "id": "bug868745",
"file": "pdfs/bug868745.pdf",
"md5": "86111ea5097dd7daffcdea891ad1b348",
"rounds": 1,
"type": "load"
},
Add test case
2011-10-03 21:57:01 +09:00
{ "id": "thuluthfont-pdf",
"file": "pdfs/ThuluthFeatures.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "b7e18bf7a3d6a9c82aefa12d721072fc",
Add test case
2011-10-03 21:57:01 +09:00
"rounds": 1,
Making ThuluthFeatures "eq" reftest
2011-10-06 11:22:52 +09:00
"type": "eq"
Add test case
2011-10-03 21:57:01 +09:00
},
Slightly improved test coverage for vertical text Our current test coverage for vertical text is somewhat lacking, as evident from e.g. issue 6387. That regression could easily have been avoided if the `taro` test-case would have been an `eq` test, as well as an `text` test.
2015-08-29 22:44:26 +09:00
{ "id": "taro",
"file": "pdfs/TaroUTR50SortedList112.pdf",
"md5": "ce63eab622ff473a43f8a8de85ef8a46",
"link": true,
"rounds": 1,
"lastPage": 4,
"type": "eq"
},
Fixes Text rotation issue #2095
2013-06-21 07:03:30 +09:00
{ "id": "taro-text",
"file": "pdfs/TaroUTR50SortedList112.pdf",
"md5": "ce63eab622ff473a43f8a8de85ef8a46",
"link":true,
"rounds": 1,
"lastPage": 4,
"type": "text"
},
Extend `getSupplementalGlyphMapForCalibri` with some umlauts (issue 15594)
2022-10-20 00:49:40 +09:00
{ "id": "issue15594",
"file": "pdfs/issue15594_reduced.pdf",
"md5": "6820808944a2a84c72d00a0e1476227b",
"rounds": 1,
"type": "eq"
},
Fixes Text rotation issue #2095
2013-06-21 07:03:30 +09:00
{ "id": "rotated-text",
"file": "pdfs/rotated.pdf",
"md5": "aed187f53e969ccdcbab0bb4c59f9e46",
"rounds": 1,
"type": "text"
},
Do not cache content stream
2013-04-20 05:07:08 +09:00
{
"id": "issue3115",
Update the link location for the `issue3115` test file The file (`lshort.pdf`) has changed a couple of times since the test was added, hence there's no guarantee that the current version accurately reflects the issues the test was added to check. In this patch, I'm updating the link location to point to the *intended* file version (hosted on the "Internet Archive").
2015-09-15 22:05:37 +09:00
"file": "pdfs/issue3115r.pdf",
Do not cache content stream
2013-04-20 05:07:08 +09:00
"md5": "ea10f4131202b9b8f2a6cb7770d3f185",
"rounds": 1,
"type": "eq",
"link": true,
Remove a duplicate PDF file from the test suite The files issue3115.pdf and issue2337.pdf are identical, the only difference being that the first one is an `eq` test and the second one a `load` test. Hence there is no reason to keep the `load` test, since it's just a subset of the `eq` test.
2014-08-24 23:05:11 +09:00
"lastPage": 1,
"about": "The same file as issue2337."
Do not cache content stream
2013-04-20 05:07:08 +09:00
},
remove glyph references outside range of avaialable glyphs
2011-12-08 12:38:34 +09:00
{ "id": "freeculture",
"file": "pdfs/freeculture.pdf",
"md5": "dcdf3a8268e6a18938a42d5149efcfca",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 5,
remove glyph references outside range of avaialable glyphs
2011-12-08 12:38:34 +09:00
"type": "eq"
},
Fixing large cmap-s; reduce changes in the indent encoding
2011-09-18 07:13:22 +09:00
{ "id": "wnv_chinese-pdf",
"file": "pdfs/wnv_chinese.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "db682638e68391125e8982d3c984841e",
Fixing large cmap-s; reduce changes in the indent encoding
2011-09-18 07:13:22 +09:00
"link": true,
"rounds": 1,
"type": "eq"
},
link to AESV2 encrypted file
2011-07-21 13:17:31 +09:00
{ "id": "i9-pdf",
"file": "pdfs/i9.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "ba7cd54fdff083bb389295bc0415f6c5",
link to AESV2 encrypted file
2011-07-21 13:17:31 +09:00
"link": true,
"rounds": 1,
"type": "eq"
Added test for inline images
2011-08-04 14:22:24 +09:00
},
Use a new method for handling soft masks. The old method of handling soft masks had a number of issues where the temporary drawing canvas and the suspended main canvas could get out of sync (e.g. mismatched save/restores or clip state) or we could end up compositing at the wrong time. A good example of things getting out sync is the reduced test case in #9017. To fix this I've changed two big things: 1) Duplicate all the needed graphics state from the temporary canvas to the suspended main canvas. This ensure the canvases stay in sync so that when we switch back to the main canvas the graphics state stack is the same (e.g. transforms, clip paths). 2) Immediately composite after each drawing operation. This ensures that if there's an active clip region that we'll still be able to composite the correct portions of the canvas. Note: This solution could be avoided by using getImageData and putImageData since those ignore clipping region, but this is very very slow. Note2: I also think the old way of only compositing at the end of the soft mask is incorrect and can lead to wrong colors if drawing over the same region, but in practice this doesn't seem to matter much. Fixes: #5781 Fixes: #5853 Fixes: #7267 Fixes: #7891 Fixes: #8403 Fixes: #8624 Fixes: #12798 Fixes: #13891 Fixes: #9017 (reduced test case) Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1703683
2021-10-20 12:14:48 +09:00
{ "id": "issue12798_page1_reduced",
"file": "pdfs/issue12798_page1_reduced.pdf",
"md5": "f4c3e91c181b510929ade67c1e34c5c5",
"rounds": 1,
"type": "eq"
},
Ensure that `Page.getOperatorList` handles Annotation parsing errors correctly (issue 15557) *Fixes a regression from PR 15246, sorry about that!* The return value of all `Annotation.getOperatorList` methods was changed in PR 15246, however I missed updating the error code-path in `Page.getOperatorList` which thus breaks all operatorList-parsing for pages with corrupt Annotations.
2022-10-10 16:40:30 +09:00
{ "id": "issue15557",
"file": "pdfs/issue15557.pdf",
"md5": "5f024a42acf27f3eadc4c7418e8f4e42",
"rounds": 1,
"type": "eq",
"annotations": true
},
Take the /CIDToGIDMap into account when getting the glyph mapping for CFF fonts (issue 15559) *Please note:* I don't really know what I'm doing here, however the patch appears to fix the referenced issue when comparing the rendering with Adobe Reader (with the caveat that I don't speak the language in question).
2022-10-12 03:08:36 +09:00
{ "id": "issue15559",
"file": "pdfs/issue15559.pdf",
"md5": "b937f2e32925aef8c1740f357f2a6282",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Fallback and try a *previous* generation if all else fails in `XRef.indexObjects` (issue 15577) When we fail to find a usable PDF document `trailer` *and* there were errors during parsing, try and fallback to a *previous* generation as a last resort during fetching of uncompressed references. *Please note:* This will not affect "normal" PDF documents, with valid /XRef data, and even most *corrupt* documents should be completely unaffected by these changes.
2022-10-16 20:15:07 +09:00
{ "id": "issue15577",
"file": "pdfs/issue15577.pdf",
"md5": "6939244cf44b7b31ff960b58ed7e4004",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Added test for inline images
2011-08-04 14:22:24 +09:00
{ "id": "hmm-pdf",
"file": "pdfs/hmm.pdf",
Update the linked test case hmm.pdf to point to the intended version The test case was changed in https://github.com/mozilla/pdf.js/commit/1faca190216deed1ef6084697d04a1d90621e210 because the original file was not available anymore. However, its hash was also changed, meaning that we do not test the intended version anymore. This patch makes sure that we test the intented version by reverting to the original hash and using a link, also pointing to the Internet Archive, with the original file.
2016-01-14 00:30:26 +09:00
"md5": "e08467e60101ee5f4a59716e86db6dc9",
Added test for inline images
2011-08-04 14:22:24 +09:00
"link": true,
"rounds": 1,
update manifest of hmm.pdf
2013-03-05 12:33:50 +09:00
"firstPage": 1,
"lastPage": 2,
Added test for inline images
2011-08-04 14:22:24 +09:00
"type": "load"
Adding support for page rotation
2011-08-07 06:41:18 +09:00
},
Fix several issues with radial/axial shadings and tiling patterns. Previously, we set the base transformation and pattern matrix directly to the main rendering ctx of the page, however doing this caused the current transform to be lost. This would cause issues with things like shear missing so the pattern was misaligned or when stroke was used the scale of the line width or dash would be wrong. Instead we should leave the current transform and use setTransfrom on the pattern so it is applied correctly. For axial and radial shadings I had to create a temporary canvas to draw the shading so I could in turn use setTransform. Fixes: #13325, #6769, #7847, #11018, #11597, #11473 The following already in the corpus are improved: issue8078-page1 issue1877-page1
2021-05-11 09:43:37 +09:00
{ "id": "issue7847_radial",
"file": "pdfs/issue7847_radial.pdf",
"md5": "59dc206ec5dd6e6f701943e4694e4147",
"rounds": 1,
"type": "eq"
},
Adding support for page rotation
2011-08-07 06:41:18 +09:00
{ "id": "rotation",
"file": "pdfs/rotation.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "4fb25ada00ce7528569d9791c14decf5",
Adding support for page rotation
2011-08-07 06:41:18 +09:00
"rounds": 1,
Change rotation and extgstate to eq tests.
2011-10-14 06:57:56 +09:00
"type": "eq"
BaseFont and misc fonts fixes
2011-08-14 22:40:22 +09:00
},
{ "id": "ecma262-pdf",
"file": "pdfs/ecma262.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "763ead98f535578842891e5574e0af0f",
BaseFont and misc fonts fixes
2011-08-14 22:40:22 +09:00
"link": true,
"rounds": 1,
"type": "load"
Handle 'space' character correctly in MacRomanEncoding (bug 878026)
2014-04-08 03:50:27 +09:00
},
Add validation for callsubr and callgsubr for type 2 charstrings.
2016-01-06 02:53:31 +09:00
{ "id": "issue6286",
"file": "pdfs/issue6286.pdf",
"md5": "d13fd1b98fb1c9980356314fd1d3a91b",
"rounds": 1,
"type": "eq"
},
Overwrite glyphs contour count if it's less than -1. The test pdf has a contour count of -70, but OTS doesn't like values less than -1. Fixes issue #7562.
2017-10-30 11:07:02 +09:00
{ "id": "PDFJS-7562-reduced",
"file": "pdfs/PDFJS-7562-reduced.pdf",
"md5": "ddfb96fd492599fe54adbc685493ba3a",
"rounds": 1,
"type": "eq"
},
Add validation for callsubr and callgsubr for type 2 charstrings.
2016-01-06 02:53:31 +09:00
{ "id": "issue3694_reduced",
Fix a typo in the "file" entry for issue3694_reduced in test_manifest.json When generating new references locally on Windows, after PR 6724, I get the following output: ``` WARNING: Unable to open file for reading "Error: ENOENT, open 'c:\Users\Jonas\Git\pdfjs\test\pdfs\issue_3694_reduced.pdf'". Unable to verify the checksum for the files that are used for testing. Please re-download the files, or adjust the MD5 checksum in the manifest for the files listed above. ``` Compared to the name of the file (`issue3694_reduced.pdf`), you see that the manifest entry has a superfluous underscore in the "file" entry.
2016-01-06 05:21:14 +09:00
"file": "pdfs/issue3694_reduced.pdf",
Add validation for callsubr and callgsubr for type 2 charstrings.
2016-01-06 02:53:31 +09:00
"md5": "c1438c7bad12d70c4cd684f8ce04448f",
"rounds": 1,
"type": "eq"
},
Add a reduced test case for bug 847420
2014-10-13 05:36:50 +09:00
{ "id": "bug847420",
"file": "pdfs/bug847420.pdf",
"md5": "0decd96fec4ef858c2c663a6de24e887",
"rounds": 1,
"link": false,
"type": "eq"
},
Handle 'space' character correctly in MacRomanEncoding (bug 878026)
2014-04-08 03:50:27 +09:00
{ "id": "bug878026",
"file": "pdfs/bug878026.pdf",
"md5": "13072db0586f2b4e96de189e23fc7395",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
Add JAI.pdf (issue #292) to the ref tests
2011-08-15 02:26:48 +09:00
},
Tests for text layer
2014-04-11 04:36:37 +09:00
{ "id": "issue4550-text",
"file": "pdfs/issue4550.pdf",
"md5": "d64cfc4b50e225f596130d9938e8d5cc",
"rounds": 1,
"type": "text"
},
Improve the heuristics, in `PartialEvaluator._buildSimpleFontToUnicode`, for glyphNames of the Cdd{d}/cdd{d} format (issue 9655) *Please note:* I've been thinking about possible ways of addressing this issue for a while now, but all of the solutions I came up with became too complicated and thus hurt readability of the code. However, it occured to me that we're essentially trying to add a heuristic *on top* of another heuristic, and that it shouldn't matter how efficient the code is as long as it works. In the PDF file in the issue the Encoding contains glyphNames of the `Cdd` format, which our existing heuristics will treat as base 10 values. However, in this particular file they actually contain base 16 values, which we thus attempt to detect and fix such that text-selection works.
2019-09-30 06:50:58 +09:00
{ "id": "issue9655-text",
"file": "pdfs/issue9655_reduced.pdf",
"md5": "87259a82cf3cda18e240517ca53c312a",
"rounds": 1,
"link": false,
"type": "text"
},
Add JAI.pdf (issue #292) to the ref tests
2011-08-15 02:26:48 +09:00
{ "id": "jai-pdf",
"file": "pdfs/jai.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "1f5dd128c3757420a881a155f2f8ace3",
Add JAI.pdf (issue #292) to the ref tests
2011-08-15 02:26:48 +09:00
"link": true,
"rounds": 1,
"type": "load"
Adds cable.pdf link to tests
2011-08-29 06:36:58 +09:00
},
{ "id": "cable",
"file": "pdfs/cable.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "09a41b9a759d60c698228224ab85b46d",
Adds cable.pdf link to tests
2011-08-29 06:36:58 +09:00
"link": true,
"rounds": 1,
"type": "eq"
Add PdKids.pdf as a ref test
2011-08-31 12:32:56 +09:00
},
{ "id": "pdkids",
"file": "pdfs/pdkids.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "278982bf016dbe46d2066f9245d9b3e6",
Add PdKids.pdf as a ref test
2011-08-31 12:32:56 +09:00
"link": true,
"rounds": 1,
"type": "eq"
Fixing properties.widths is null issue; fips197 test file
2011-09-15 11:29:32 +09:00
},
Ensure that Annotation `appearance`-entries are actually Streams Note how all over the `src/core/annotation.js`-code we're assuming that if an `appearance`-entry exists it's also a Stream. However, we're not actually checking that thoroughly enough which causes issues in some badly generated PDF documents.
2023-01-16 20:56:43 +09:00
{ "id": "checkbox-bad-appearance",
"file": "pdfs/checkbox-bad-appearance.pdf",
"md5": "acdac655911cb3d33c3fb1462cf2ad56",
"rounds": 1,
"type": "eq",
"forms": true
},
Disable encryption when a ToUnicode stream is used in a font
2011-09-14 09:23:49 +09:00
{ "id": "artofwar",
"file": "pdfs/artofwar.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "7bdd51c327b74f1f7abdd90eedb2f912",
Disable encryption when a ToUnicode stream is used in a font
2011-09-14 09:23:49 +09:00
"link": true,
"rounds": 1,
"type": "eq"
Merge branch 'master' of https://github.com/andreasgal/pdf.js.git into charstoglyphs Conflicts: test/test_manifest.json
2011-09-15 11:45:12 +09:00
},
Adds test for issue 3371 and enables testing with password.
2013-06-24 03:20:47 +09:00
{ "id": "issue3371",
"file": "pdfs/issue3371.pdf",
"password": "ELXRTQWS",
"md5": "db2fedbd36d6fa27d4e52f9bd2d96b8c",
"rounds": 1,
"type": "load"
},
Correctly detect OpenType font files with CFF data Fixes 5334. Fixes 215. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1125614. According to the specification, http://www.microsoft.com/typography/otspec/otff.htm, OpenType font files with CFF data should have `OTTO` in the header.
2015-02-28 20:58:53 +09:00
{ "id": "issue5334",
"file": "pdfs/issue5334.pdf",
"md5": "5575020f37f6e5b3c43b8183bf7f96ae",
"rounds": 1,
"link": false,
"type": "eq"
},
Use charstring as plain text when lengthIV is -1. Fixes #7769
2017-10-19 06:10:40 +09:00
{ "id": "issue7769",
"file": "pdfs/issue7769.pdf",
"md5": "814f167b8437eb8e4e4b6e89743011d5",
"rounds": 1,
"link": false,
"type": "eq"
},
Adds transfer function support for SMask.
2015-12-05 03:52:45 +09:00
{ "id": "issue5044",
"file": "pdfs/issue5044.pdf",
"md5": "44788cd31dcb4a2495ded34a84c4a765",
"rounds": 1,
"link": false,
"type": "eq"
Correctly detect OpenType font files with CFF data Fixes 5334. Fixes 215. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1125614. According to the specification, http://www.microsoft.com/typography/otspec/otff.htm, OpenType font files with CFF data should have `OTTO` in the header.
2015-02-28 20:58:53 +09:00
},
Use post table when Encoding has only Differences Fixes #13107 In the issue, some TrueType glyph names have the format `uniXXXX`. Font's `Encoding` dictionary has the entry `Differences` but no `BaseEncoding`. `uniXXXX` names are converted to glyph indices using font's `post` table but currently that is done only when `BaseEncoding` exists. We must enable the conversion also when only `Differences` exists.
2021-03-31 22:32:30 +09:00
{ "id": "issue13107",
"file": "pdfs/issue13107_reduced.pdf",
"md5": "13c8d12223dec2752d3c90d250db32b7",
"rounds": 1,
"type": "eq"
},
Adjust the heuristics used to detect OpenType font file with CFF data (bug 1186827, bug 1182130, issue 6264) *This is a tentative patch.* Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1186827. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1182130. Fixes 6264.
2015-07-25 19:26:36 +09:00
{ "id": "bug1186827",
"file": "pdfs/bug1186827.pdf",
"md5": "6c5526ae1a9d66cb517153001afc196e",
"rounds": 1,
"link": false,
"type": "eq"
},
Correct PostScript trigonometric operators PDF 32000-1:2008 7.10.5.1 "Type 4 (PostScript Calculator) Functions" defers to the PostScript Language Reference for the description of these functions. The PostScript Language Reference, third edition chapter 8 "Operators" defines the `angle` type as a "number of degrees". Section 8.1 defines "angle `sin` real", "angle `cos` real", and "num den `atan` angle". The documentation for `atan` further states that it will return an angle in degrees between 0 and 360. Handle these operators correctly in `PostScriptEvaluator.execute`. Convert the inputs to `sin` and `cos` from degrees to radians for use with `Math.sin` and `Math.cos`. Correctly pop two values from the stack for `atan`, use `Math.atan2`, and convert from radians to (positive) degrees.
2023-02-28 02:34:12 +09:00
{ "id": "colorspace_sin",
"file": "pdfs/colorspace_sin.pdf",
"md5": "4e341c346f4f37cd94b82c532badb8fd",
"rounds": 1,
"type": "eq"
},
Adjust the heuristics used to detect OpenType font file with CFF data (bug 1186827, bug 1182130, issue 6264) *This is a tentative patch.* Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1186827. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1182130. Fixes 6264.
2015-07-25 19:26:36 +09:00
{ "id": "issue215",
"file": "pdfs/issue215.pdf",
"md5": "31f3dc60ecf008987d970edfd2b1df61",
"rounds": 1,
"link": false,
"type": "eq"
},
Handle 'space' character correctly in WinAnsiEncoding (bug 850854)
2014-04-08 20:07:29 +09:00
{ "id": "bug850854",
"file": "pdfs/bug850854.pdf",
"md5": "346a034a80120d123b9fefc42bcb11da",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Modifying how the artofwar encryption handled; add wdsg_fitc as reftest
2011-09-18 00:32:42 +09:00
{ "id": "wdsg_fitc",
"file": "pdfs/wdsg_fitc.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "5bb1c2b83705d4cdfc43197ee74f07f9",
Modifying how the artofwar encryption handled; add wdsg_fitc as reftest
2011-09-18 00:32:42 +09:00
"link": true,
"rounds": 1,
"type": "eq"
Merge branch 'master' of https://github.com/andreasgal/pdf.js.git into charstoglyphs Conflicts: test/test_manifest.json
2011-09-18 01:23:34 +09:00
},
Fix several issues with radial/axial shadings and tiling patterns. Previously, we set the base transformation and pattern matrix directly to the main rendering ctx of the page, however doing this caused the current transform to be lost. This would cause issues with things like shear missing so the pattern was misaligned or when stroke was used the scale of the line width or dash would be wrong. Instead we should leave the current transform and use setTransfrom on the pattern so it is applied correctly. For axial and radial shadings I had to create a temporary canvas to draw the shading so I could in turn use setTransform. Fixes: #13325, #6769, #7847, #11018, #11597, #11473 The following already in the corpus are improved: issue8078-page1 issue1877-page1
2021-05-11 09:43:37 +09:00
{ "id": "issue6769_no_matrix",
"file": "pdfs/issue6769_no_matrix.pdf",
"md5": "f88806137fb4592975052ff3508d7b1e",
"rounds": 1,
"type": "eq"
},
Fixing "no spaces" issue (ref #577)
2011-10-02 11:24:11 +09:00
{ "id": "unix01",
"file": "pdfs/unix01.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "2742999f0bf9b9c035dbb0736096e220",
Fixing "no spaces" issue (ref #577)
2011-10-02 11:24:11 +09:00
"link": true,
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 4909 I *should* have included this is PR 4910, but for some reason I didn't so better late than never.
2015-06-26 05:16:08 +09:00
{ "id": "issue4909",
"file": "pdfs/issue4909.pdf",
"md5": "ecd62637532aa8383837ef11d72a96b9",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a (linked) test-case for issue 4914
2015-09-26 23:02:12 +09:00
{ "id": "issue4914",
"file": "pdfs/issue4914.pdf",
"md5": "6e1da9c5283d9acef0314d87ce953659",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
Change test-case `issue4914` to an `annotations` test This PDF file (see issue 4914) originally regressed in PR 4318, and was subsequently fixed in PR 4915. I added the PDF file as a (linked) test-case in PR 6481, in an effort to prevent regressions. Since we at that time didn't have the necessary framework in place, in order to correctly test annotations, this almost regressed *again* in PR https://github.com/mozilla/pdf.js/pull/6672#issuecomment-158689392. In that PDF file, some of the annotations are both printable and hidden, and should definitely *not* be visible on normal display. Hence this patch, which adds the `annotations` flag to the manifest in order to ensure that those annotations won't be rendered when `intent === 'display'`.
2015-12-21 23:15:26 +09:00
"annotations": true,
Add a (linked) test-case for issue 4914
2015-09-26 23:02:12 +09:00
"about": "PDF with annotations, some of which have the Hidden flag set."
},
Always fallback to system font on font failure. The font in the PDF is marked as a CIDFontType0, but the font file is actually a true type font. To fully address this issue we should really peek into the font file and try to determine what it is. However, this is the first case of this issue, so I think this solution is acceptable for now.
2018-08-04 08:47:45 +09:00
{ "id": "issue9949",
"file": "pdfs/issue9949.pdf",
"md5": "55d24d7fc71b849818ea91d3b9eaf302",
"rounds": 1,
"type": "eq"
},
Add a reduced `text` test-case for issue 4665 Re: issue 4665 and PR 6601. Since we currently don't have a good `text` test-case that fails without the above PR, this patch adds a reduced one.
2015-11-07 21:04:03 +09:00
{ "id": "issue4665-text",
"file": "pdfs/issue4665.pdf",
"md5": "0de1308432819c101881df7ca4424575",
"rounds": 1,
"link": false,
"type": "text"
},
Set CFF header to 4 when writing it because it contains 4 elements (#13149)
2021-03-27 02:23:18 +09:00
{ "id": "issue13147",
"file": "pdfs/issue13147.pdf",
"md5": "83db23f29b5e1a80d31d5069299e29cc",
"rounds": 1,
"type": "eq"
},
Add fit11-talk as a eq reftest
2011-10-12 08:26:25 +09:00
{ "id": "fit11-talk",
"file": "pdfs/fit11-talk.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "eb7b224107205db4fea9f7df0185f77d",
Add fit11-talk as a eq reftest
2011-10-12 08:26:25 +09:00
"link": true,
"rounds": 1,
"type": "eq"
},
Fixing properties.widths is null issue; fips197 test file
2011-09-15 11:29:32 +09:00
{ "id": "fips197",
"file": "pdfs/fips197.pdf",
Fixes test pdfs MD5; make server does not download
2012-10-17 00:30:14 +09:00
"md5": "4742c3f470cd8c4686a0dbb3da808b71",
Fixing properties.widths is null issue; fips197 test file
2011-09-15 11:29:32 +09:00
"link": true,
"rounds": 1,
Fixing #650 regression
2011-10-13 07:52:11 +09:00
"type": "eq"
Handle missing encoding differences array
2011-09-21 07:42:52 +09:00
},
Prevent trying to map characters to the specials unicode block in adjustMapping (issue 4650)
2014-04-29 03:09:00 +09:00
{ "id": "issue4650",
"file": "pdfs/issue4650.pdf",
"md5": "ad736804f57f9f96f5ac108e514e1686",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
Don't blindly trust toUnicode when building toFontChar for non-standard fonts without a font file (issue 4934)
2014-06-15 05:51:13 +09:00
},
Use a new method for handling soft masks. The old method of handling soft masks had a number of issues where the temporary drawing canvas and the suspended main canvas could get out of sync (e.g. mismatched save/restores or clip state) or we could end up compositing at the wrong time. A good example of things getting out sync is the reduced test case in #9017. To fix this I've changed two big things: 1) Duplicate all the needed graphics state from the temporary canvas to the suspended main canvas. This ensure the canvases stay in sync so that when we switch back to the main canvas the graphics state stack is the same (e.g. transforms, clip paths). 2) Immediately composite after each drawing operation. This ensures that if there's an active clip region that we'll still be able to composite the correct portions of the canvas. Note: This solution could be avoided by using getImageData and putImageData since those ignore clipping region, but this is very very slow. Note2: I also think the old way of only compositing at the end of the soft mask is incorrect and can lead to wrong colors if drawing over the same region, but in practice this doesn't seem to matter much. Fixes: #5781 Fixes: #5853 Fixes: #7267 Fixes: #7891 Fixes: #8403 Fixes: #8624 Fixes: #12798 Fixes: #13891 Fixes: #9017 (reduced test case) Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1703683
2021-10-20 12:14:48 +09:00
{ "id": "bug1703683_page2_reduced",
"file": "pdfs/bug1703683_page2_reduced.pdf",
"md5": "2b6d5d617438cf72c76c25f46ec6ad75",
"rounds": 1,
"type": "eq"
},
Ensure that `PDFImage.buildImage` won't accidentally swallow errors, e.g. from ColorSpace parsing (issue 6707, PR 11601 follow-up) Because of a really stupid `Promise`-related mistake on my part, when re-factoring `PDFImage.buildImage` during the `NativeImageDecoder` removal, we're no longer re-throwing errors occuring during image parsing/decoding as intended. The result is that some (fairly) corrupt documents will never finish loading, and unfortunately there were apparently no sufficiently corrupt images in the test-suite to catch this.
2020-06-13 21:41:34 +09:00
{ "id": "issue6707",
"file": "pdfs/issue6707.pdf",
"md5": "068ceaec23d265b1d38dfa6ab279f017",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Only draw glyphs on canvas if they are in the font or the font file is missing.
2016-02-25 03:48:02 +09:00
{ "id": "issue6721_reduced",
"file": "pdfs/issue6721_reduced.pdf",
"md5": "719aa66d8081a15e3ba6032ed4279237",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Avoid rendering errors by passing in the `webGLContext` when creating a new `CanvasGraphics` in `getColorN_Pattern` (PR 9095 follow-up) This was an oversight in PR 9095, which unfortunately breaks rendering in some PDF files (e.g. the one from issue 6737). It thus appears that we don't have any test-coverage for this code-path, and given the relative complexity of the PDF files affected by this bug I wasn't able to easily create a reduced test-case. *Please note:* The linked test-case included in this patch is currently *not* rendered correctly (that'd be the PR 6606), but it at least gives us some test-coverage here.
2017-12-27 21:35:18 +09:00
{ "id": "issue6737",
"file": "pdfs/issue6737.pdf",
"md5": "6f091967ad15ba63855c56049e86c68b",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Prevent CMapFactory.create from failing by passing the necessary parameters from PartialEvaluator_readToUnicode (issue 5010)
2014-06-27 07:41:44 +09:00
{ "id": "issue5010",
"file": "pdfs/issue5010.pdf",
"md5": "419f4b13403a0871c463ec69d96e342c",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Ensure that entries in the Differences array of Type1 fonts are either numbers or names This patch is yet another installment in the (never ending) series of bugs in PDF files with non-embedded fonts. Fixes http://www.int.washington.edu/talks/WorkShops/int_08_37W/People/Franz_M/Franz.pdf.
2015-03-09 22:36:45 +09:00
{ "id": "franz",
"file": "pdfs/franz.pdf",
"md5": "12f0bbdec09900cbdd86e1737ed5f992",
"link": false,
"rounds": 1,
"type": "eq",
"about": "Type1 font with |Ref|s in the Differences array of the Encoding dictionary."
},
Add a (linked) test-case for issue 8019 Given that [bug 1336572](https://bugzilla.mozilla.org/show_bug.cgi?id=1336572) was just closed as fixed, thus fixing issue 8019 in Firefox[1], let's add a test-case to enable us to catch any future regressions either in PDF.js or in browsers themselves. --- [1] It also seems to be working in Google Chrome, although I'm having a slightly difficult time deciphering *exactly* what configurations were affected when looking through issue 8019.
2021-12-04 16:47:32 +09:00
{ "id": "issue8019",
"file": "pdfs/issue8019.pdf",
"md5": "5263ea3e295ee004c9fe770146bc34ef",
"link": true,
"rounds": 1,
"type": "eq"
},
Add a (linked) test-case for issue 8022 Given that [bug 1336591](https://bugzilla.mozilla.org/show_bug.cgi?id=1336591) was just closed as fixed, thus fixing issue 8022 in Firefox, let's add a test-case to enable us to catch any future regressions either in PDF.js or in browsers themselves.
2021-12-06 23:21:22 +09:00
{ "id": "issue8022",
"file": "pdfs/issue8022.pdf",
"md5": "a1a028a5d44433a965dd1e778f321c14",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Tweak the `QueueOptimizer` to recognize `OPS.paintImageMaskXObject` operators as *repeated* when the "skew" transformation matrix elements are non-zero (issue 8078) *First of all, I should mention that my understanding of the finer details of the `QueueOptimizer` (and its related `CanvasGraphics` methods) is somewhat limited.* Hence I'm not sure if there's actually a very good reason for *only* considering ImageMasks where the "skew" transformation matrix elements are zero as *repeated*, however simply looking at the code I just don't see why these elements cannot be non-zero as long as they are *all identical* for the ImageMasks. Furthermore, looking at the *group* case (which is what we're currently falling back to), there's no particular limitation placed upon the transformation matrix elements. While this patch obviously isn't enough to *completely* fix the issue, since there should be a visible Pattern rendered as well[1], it seem (at least to me) like enough of an improvement that submitting this is justified. With these changes the referenced PDF document will no longer hang the *entire* browser, and rendering also finishes in a *reasonable* time (< 10 seconds for me) which seem fine given the *huge* number of identical inline images present.[2] --- [1] Temporarily changing the Pattern to a solid color *does* render the correct/expected area, which suggests that the remaining problem is a pre-existing issue related to the Pattern-handling itself rather than the `QueueOptimizer` functionality. [2] The document isn't exactly rendered immediately in e.g. Adobe Reader either.
2020-06-20 18:34:41 +09:00
{ "id": "issue8078",
"file": "pdfs/issue8078.pdf",
"md5": "8b7d74bc24b4157393e4e88a511c05f1",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Tweak `adjustType1ToUnicode` for fonts with a predefined *named* encoding (bug 1811668, PR 14050 follow-up) *Please note:* I cannot reproduce the problem reported in bug 1811668, regarding the context menu, and in any case it's not clear that that part is even a PDF Viewer bug. Looking at bug 1811668 I couldn't help but noticing that the textLayer isn't correct, and it's unfortunately once again a problem with the `adjustType1ToUnicode` function. That's intended to help improve text-selection for fonts without a /ToUnicode-entry, and in many cases it does help (the original PR fixed lots of issues) however it's also caused some problems. In order to improve text-selection in bug 1811668, we'll now properly ignore fonts that have a predefined *named* encoding specified since that's really the intention with PR 14050.
2023-01-21 20:00:17 +09:00
{ "id": "bug1811668",
"file": "pdfs/bug1811668_reduced.pdf",
"md5": "87aa65d89aa0682cbe7b87152b884495",
"rounds": 1,
"type": "text"
},
Apply bounding box before using shading patterns. Fixes #8092
2019-05-24 09:45:25 +09:00
{ "id": "issue8092",
"file": "pdfs/issue8092.pdf",
"md5": "e4f3376b35fd132580246c3db1fbd738",
"rounds": 1,
"type": "eq"
Ensure that entries in the Differences array of Type1 fonts are either numbers or names This patch is yet another installment in the (never ending) series of bugs in PDF files with non-embedded fonts. Fixes http://www.int.washington.edu/talks/WorkShops/int_08_37W/People/Franz_M/Franz.pdf.
2015-03-09 22:36:45 +09:00
},
Prevent `PartialEvaluator_buildFormXObject` from failing if the `Matrix` or `BBox` contains indirect objects This patch fixes yet another instance of bad PDF data, specifically a case where the `BBox` array contains indirect objects (i.e. `Ref`s). Fixes the missing image in http://www.int.washington.edu/talks/WorkShops/int_08_37W/People/Franz_M/Franz.pdf#page=24. *Note:* There are missing images on a number of the pages in that file.
2015-09-28 22:09:24 +09:00
{ "id": "franz_2",
"file": "pdfs/franz_2.pdf",
"md5": "9d301ed8816e879891115b5cc3c39559",
"link": false,
"rounds": 1,
"type": "eq",
"about": "XObject with BBox array containing indirect object."
},
Prevent failures in the Annotation code if the `Rect` array contains indirect objects (issue 7115) Note that in the PDF files provided by the reporter, this issue was limited to `Rect` arrays in AcroForm entries (which we currently don't support). However, since a bad PDF generator could create this problem in *any* kind of annotation, the reduced test-case included here uses a simple LinkAnnotation instead. Fixes 7115.
2016-03-26 22:41:15 +09:00
{ "id": "issue7115",
"file": "pdfs/issue7115.pdf",
"md5": "63c78e25a0433dd5a01ddff6ec720f29",
"link": false,
"rounds": 1,
"type": "eq",
"annotations": true,
"about": "Annotation with Rect array containing indirect objects."
},
Avoid hanging the worker-thread for CMap data with ridiculously large ranges (issue 11922) This patch was inspired by https://github.com/kermitt2/xpdf-4.00/blob/ad2b64f1244b32fca0ff0868af1cfa0238c9933e/xpdf/CharCodeToUnicode.cc#L480-L484
2020-05-22 21:07:28 +09:00
{ "id": "issue11922",
"file": "pdfs/issue11922_reduced.pdf",
"md5": "711bb4b4bf92d967644b4f88d11a93db",
"rounds": 1,
"type": "load"
},
Hide unsupported `LinkAnnotation`s (issue 3897) Rather than displaying links that does *nothing* when clicked, it probably makes more sense to simply not render them instead. Especially since it turns out that, at least at this point in time, this is *very* easy to both implement and test. Fixes 3897.
2017-09-02 17:06:44 +09:00
{ "id": "file_url_link",
"file": "pdfs/file_url_link.pdf",
"md5": "b0253c96c38d43bc49259bbf36db938a",
"link": false,
"rounds": 1,
"type": "eq",
"annotations": true,
"about": "Annotation with (unsupported) file:// URL."
},
Add support for missing appearances for hightlights, strikeout, squiggly and underline annotations.
2020-08-08 03:46:41 +09:00
{ "id": "bug1538111",
"file": "pdfs/bug1538111.pdf",
"md5": "3f3635cfc25d132fb1054042e520e297",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Ignore Annotations with too large border `width`s, to prevent the `annotationLayer` from rendering it over the surrounding document (bug 1552113) The border `width` will instead fallback to the default value of `1`, rather than ignoring it altoghether, to also ensure that e.g. `LinkAnnotation`s become clickable as intended. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1552113
2019-06-01 03:44:24 +09:00
{ "id": "bug1552113",
"file": "pdfs/bug1552113.pdf",
"md5": "dafb7ba1328e8deaab2e3619c94bf974",
"link": false,
"rounds": 1,
"type": "eq",
"annotations": true,
"about": "Annotation with (ridiculously) large border width."
},
Compute the `transformOrigin` correctly, for negative values, when rendering `AnnotationElement`s (bug 1627030) This changes the `transformOrigin` calculations in `AnnotationElement._createContainer` and `PopupAnnotationElement.render`, to ensure that e.g. the clickable area of annotations and/or popups are both positioned correctly. The problem occurs for *negative* values, since they're not negated correctly because of how the `transformOrigin` strings were build; see issue 12406 for a more in-depth explanation. Previously, for negative values, the `transformOrigin` strings would thus be ignored since they're not valid.
2020-09-24 17:28:29 +09:00
{ "id": "bug1627030",
"file": "pdfs/bug1627030.pdf",
"md5": "4cde6134daa80449c43defd02c1393e2",
"rounds": 1,
"link": true,
"firstPage": 3,
"lastPage": 3,
"type": "eq",
"annotations": true
},
Use a new method for handling soft masks. The old method of handling soft masks had a number of issues where the temporary drawing canvas and the suspended main canvas could get out of sync (e.g. mismatched save/restores or clip state) or we could end up compositing at the wrong time. A good example of things getting out sync is the reduced test case in #9017. To fix this I've changed two big things: 1) Duplicate all the needed graphics state from the temporary canvas to the suspended main canvas. This ensure the canvases stay in sync so that when we switch back to the main canvas the graphics state stack is the same (e.g. transforms, clip paths). 2) Immediately composite after each drawing operation. This ensures that if there's an active clip region that we'll still be able to composite the correct portions of the canvas. Note: This solution could be avoided by using getImageData and putImageData since those ignore clipping region, but this is very very slow. Note2: I also think the old way of only compositing at the end of the soft mask is incorrect and can lead to wrong colors if drawing over the same region, but in practice this doesn't seem to matter much. Fixes: #5781 Fixes: #5853 Fixes: #7267 Fixes: #7891 Fixes: #8403 Fixes: #8624 Fixes: #12798 Fixes: #13891 Fixes: #9017 (reduced test case) Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1703683
2021-10-20 12:14:48 +09:00
{ "id": "issue9017_reduced",
"file": "pdfs/issue9017_reduced.pdf",
"md5": "8b45b3ea91778d6d98f407620d645f48",
"rounds": 1,
"type": "eq"
},
Don't blindly trust toUnicode when building toFontChar for non-standard fonts without a font file (issue 4934)
2014-06-15 05:51:13 +09:00
{ "id": "issue4934",
"file": "pdfs/issue4934.pdf",
"md5": "6099da44f677702ae65a648b51a2226d",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
Prevent trying to map characters to the specials unicode block in adjustMapping (issue 4650)
2014-04-29 03:09:00 +09:00
},
Don't skip mapping of glyphs for CIDFontType2 fonts with a CIDToGIDMap Also don't skip mapping of glyphs which are empty, if the corresponding charCode is included in toUnicode.
2015-01-02 22:21:56 +09:00
{ "id": "issue4061",
"file": "pdfs/issue4061.pdf",
"md5": "236aaa8840a47c3c061f8e3034549764",
"rounds": 1,
"link": false,
"type": "eq"
},
Attempt to skip zero bytes at the end of Scan blocks when decoding JPEG images (issue 4090)
2016-09-22 17:11:27 +09:00
{ "id": "issue4090",
"file": "pdfs/issue4090.pdf",
"md5": "8cec73e090985acf6094c683d7944425",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Fix transformations when painting image masks and tiling patterns. Previously, when we filled image masks we didn't copy over the current transformation, this caused patterns to be misaligned when painted. Now we create a temporary canvas with the mask and have the transform copied over and offset it relative to where the mask would be painted. We also weren't properly offsetting tiling patterns. This isn't usually noticeable since patters repeat, but in the case of #13561 the pattern is only drawn once and has to be in the correct position to line up with the mask image. These fixes broke #11473, but highlighted that we were drawing that correctly by accident and not correctly handling negative bounding boxes on tiling patterns. Fixes #6297, #13561, #13441 Partially fixes #1344 (still blurry but boxes are in correct position now)
2021-07-01 07:09:07 +09:00
{ "id": "issue13561_reduced",
"file": "pdfs/issue13561_reduced.pdf",
"md5": "e68c315d6349530180dd90f93027147e",
"rounds": 1,
"type": "eq"
},
Don't skip mapping of glyphs for CIDFontType2 fonts with a CIDToGIDMap Also don't skip mapping of glyphs which are empty, if the corresponding charCode is included in toUnicode.
2015-01-02 22:21:56 +09:00
{ "id": "issue5202",
"file": "pdfs/issue5202.pdf",
"md5": "bb9cc69211112e66aab40828086a4e5a",
"rounds": 1,
"link": false,
"type": "eq"
},
Fix Symbol fonts without font file but with Encoding dictionary (issue 5238)
2014-08-31 21:03:25 +09:00
{ "id": "issue5238",
"file": "pdfs/issue5238.pdf",
"md5": "6ddecda00893be1793de20a70c83a3c2",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a reduced test case for issue 5470
2014-11-05 00:16:48 +09:00
{ "id": "issue5470",
"file": "pdfs/issue5470.pdf",
"md5": "4805fdcd7e142e8df3c04c6ba06025af",
"rounds": 1,
"link": false,
"type": "eq"
},
Make `XRef_indexObjects` even more robust against bad PDF files, by checking for the existence of 'trailer' if 'xref' is not found Fixes http://www.cyjack.com/cognition/Terence%20McKenna%20-%20Lectures%20on%20Alchemy.pdf.
2015-10-01 21:46:03 +09:00
{ "id": "xref_command_missing",
"file": "pdfs/xref_command_missing.pdf",
"md5": "06cdb0f13cfeff41d6bfb24b7bbe1268",
"rounds": 1,
"link": false,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"type": "eq"
Make `XRef_indexObjects` even more robust against bad PDF files, by checking for the existence of 'trailer' if 'xref' is not found Fixes http://www.cyjack.com/cognition/Terence%20McKenna%20-%20Lectures%20on%20Alchemy.pdf.
2015-10-01 21:46:03 +09:00
},
Check the top-level /Pages dictionary when finding the trailer in `XRef.indexObjects` (issue 12402) In addition to the existing /Root and /Pages validation, also check that the /Pages-entry actually is a dictionary and that it has a valid /Count-entry. This way we can avoid picking a trailer candidate which e.g. the `Catalog.numPages` getter will just end up rejecting, thus breaking PDF document loading completely.
2020-11-25 21:44:57 +09:00
{ "id": "issue12402",
"file": "pdfs/issue12402.pdf",
"md5": "70031cf610e24cc7164fb6ecd6980c8e",
"rounds": 1,
"link": true,
"firstPage": 8,
"lastPage": 8,
"type": "eq"
},
Add a test-case for bug 1292316 It appears that the PDF document in [bug 1292316](https://bugzilla.mozilla.org/show_bug.cgi?id=1292316) now renders "correctly"[1] when compared to e.g. Adobe Reader and PDFium. Most likely this bug was fixed by a *somewhat* recent patch, or patches, to the `XRef.indexObjects` method. Before just closing [bug 1292316](https://bugzilla.mozilla.org/show_bug.cgi?id=1292316) as WFM, I figured that it probably can't hurt to add it as a new test-case to avoid accidentally regressing this document in the future. --- [1] Given that the XRef table is corrupt, and that we're forced to recover, there's generally speaking probably some question as to what actually constitutes "correct" in this case.
2020-12-12 21:08:03 +09:00
{ "id": "bug1292316",
"file": "pdfs/bug1292316.pdf",
"md5": "f0a815ada0276059242f264653cfd2bc",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Attempt to find truncated endstream commands, in the fallback code-path, in `Parser.makeStream` (issue 10004) Apparently there's some PDF generators, in this case the culprit is "Nooog Pdf Library / Nooog PStoPDF v1.5", that manage to mess up PDF creation enough that endstream[1] commands actually become truncated. *Please note:* The solution implemented here isn't perfect, since it won't be able to cope with PDF files that contains a *mixture* of correct and truncated endstream commands. However, considering that this particular mode of corruption *fortunately* doesn't seem very common[2], a slightly less complex solution ought to suffice for now. Fixes 10004. --- [1] Scanning through the PDF data to find endstream commands becomes necessary, in order to determine the stream length in cases where the `Length` entry of the (stream) dictionary is missing/incorrect. [2] I cannot recall having seen any (previous) issues/bugs with "Missing endstream" errors.
2018-08-26 08:49:31 +09:00
{ "id": "issue10004",
"file": "pdfs/issue10004.pdf",
"md5": "64d1853060cefe3be50e5c4617dd0505",
"rounds": 1,
"link": true,
"type": "load"
},
XFA - Avoid an exception when looking for a font in a parent node - it aims to fix issue https://github.com/mozilla/pdf.js/issues/14150; - a parent can be null in case the root has been reached, so just add a check.
2021-11-13 00:17:02 +09:00
{ "id": "xfa_issue14150",
"file": "pdfs/xfa_issue14150.pdf",
"md5": "295b3e513b62945fbba73bce6908344c",
"link": true,
"rounds": 1,
"enableXfa": true,
"lastPage": 1,
"type": "eq"
},
XFA - Draw arcs correctly - it aims to fix #14315; - take into account the startAngle to compute the coordinates of the final point.
2021-11-28 01:34:05 +09:00
{ "id": "xfa_issue14315",
"file": "pdfs/xfa_issue14315.pdf",
"md5": "e239710875f9dea72fd94c20672a29e1",
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Create a new page in case of overflow - it aims to fix #14071; - a subform is overflowing and the the target in case of overflow is itself. In this case we must create a new page.
2021-09-24 21:57:51 +09:00
{ "id": "xfa_issue14071",
"file": "pdfs/xfa_issue14071.pdf",
"md5": "7ef09705091602668ce22086c83a90f3",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
Ignore Square/Circle-annnotations with a zero borderWidth when creating a fallback appearance stream (issue 14164) Trying to render these Annotation-types, when the borderWidth is `0`, causes a "hairline" border to appear. If these Annotations included an appearance stream, as they are supposed to, this wouldn't have happened and the simplest solution here seem to be to just ignore these particular Annotations.
2021-10-19 22:13:04 +09:00
{ "id": "issue14164",
"file": "pdfs/issue14164.pdf",
"md5": "feb444c716b0337efff8094b156def32",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
XFA - Save filled data in the pdf when downloading the file (Bug 1716288) - when binding (after parsing) we get a map between some template nodes and some data nodes; - so set user data in input handlers in using data node uids in the annotation storage; - to save the form, just put the value we have in the storage in the correct data nodes, serialize the xml as a string and then write the string at the end of the pdf using src/core/writer.js; - fix few bugs around data bindings: - the "Off" issue in Bug 1716980.
2021-06-25 21:31:55 +09:00
{ "id": "xfa_filled_imm1344e",
"file": "pdfs/xfa_filled_imm1344e.pdf",
"md5": "0576d16692fcd8ef2366cb48bf296e81",
"rounds": 1,
"enableXfa": true,
"lastPage": 2,
"type": "eq"
},
XFA - Correctly bind global data (bug 1718725)
2021-07-07 23:16:21 +09:00
{ "id": "xfa_bug1718725",
"file": "pdfs/xfa_bug1718725.pdf",
"md5": "09c7a599338ff75491f29a8f1f94454b",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
XFA - Avoid an error when an exdata is a string (bug 1723114)
2021-07-29 21:27:17 +09:00
},
XFA - Fix a breakBefore issue when target is a contentArea and startNew is 1 (bug 1739502) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1739502; - when the target area was the current content area, everything was pushed in it instead of creating a new one (and consequently a new pageArea is created). - the pdf shows an alignment issue on page 4: - the hAlign is "center" but the subform was the width of its parent, so compute the real width of the subform with tb layout; - there is an extra empty page at the end of the pdf: - there is a subform with some hidden elements which are not rendered for now (since there is no plugged JS engine it isn't possible to draw them in changing their visibility). - so in case a subform is empty and has no real dimensions (at least one is 0), we just consider it as empty.
2021-11-06 02:59:49 +09:00
{ "id": "xfa_bug1739502",
"file": "pdfs/xfa_bug1739502.pdf",
"md5": "a760a950cb225c3cbf25a55b5d95e264",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Remove the checked attribute from the checkbox when unchecked (bug 1729877) - it aims to fix: https://bugzilla.mozilla.org/show_bug.cgi?id=1729877.
2021-09-09 19:39:10 +09:00
{ "id": "xfa_bug1729877",
"file": "pdfs/xfa_bug1729877.pdf",
"md5": "1bf5429ea13a090f52edcd49cb0c4a47",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq",
"lastPage": 1,
"print": true,
"annotationStorage": {
"jobReq13847": {
"value": "0"
}
}
},
XFA - Avoid an error when an exdata is a string (bug 1723114)
2021-07-29 21:27:17 +09:00
{ "id": "xfa_bug1722038",
"file": "pdfs/xfa_bug1722038.pdf",
"md5": "95170baaade2ab6e1d0372f35db01747",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
XFA - Correctly bind global data (bug 1718725)
2021-07-07 23:16:21 +09:00
},
XFA - Fix font scale factors (bug 1720888) - All the scale factors in for the substitution font were wrong because of different glyph positions between Liberation and the other ones: - regenerate all the factors - Text may have polish chars for example and in this case the glyph widths were wrong: - treat substitution font as a composite one - add a map glyphIndex to unicode for Liberation in order to generate width array for cid font
2021-07-29 01:30:22 +09:00
{ "id": "xfa_bug1720888",
"file": "pdfs/xfa_bug1720888.pdf",
"md5": "3a9486b851b7d069c3cb31b0be2bc2ff",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Fix auto-sized fields (bug 1722030) - In order to better compute text fields size, use line height with no gaps (and consequently guessed height for text are slightly better in general). - Fix default background color in fields.
2021-07-28 01:43:05 +09:00
{ "id": "xfa_bug1722030_1",
"file": "pdfs/xfa_bug1722030_1.pdf",
"md5": "0baf149f21536ebb2bfc636a95e1d62d",
"link": true,
"rounds": 1,
"lastPage": 3,
"enableXfa": true,
"type": "eq"
},
XFA - Elements created outside of XML must have all their properties (bug 1722029) - an Image element was created, attached to its parent but the $globalData property was not set and that led to an error. - the pdf in bug 1722029 has 27 rendered rows (checked in Acrobat) when only one was displayed: this patch some binding issues around the occur element.
2021-07-26 23:14:46 +09:00
{ "id": "xfa_bug1722029",
"file": "pdfs/xfa_bug1722029.pdf",
"md5": "d8dd6bb20599fc777b4c7ff7b74dd5e3",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Remove namespace from nodes under xfa:data node - in real life some xfa contains xml like <xfa:data><xfa:Foo><xfa:Bar>...</xfa:data> since there are no Foo or Bar in the xfa namespace the JS representation are empty and that leads to errors. - so the idea is to make all nodes under xfa:data namespace agnostic which means that ns are removed from nodes in the parser but only xfa:data descendants.
2021-07-21 23:24:53 +09:00
{ "id": "xfa_bug1721600",
"file": "pdfs/xfa_bug1721600.pdf",
"md5": "5f514f476169eeb7254da380a8db495a",
"link": true,
"rounds": 1,
"lastPage": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Checkboxes must be printed (bug 1720182) - to avoid future regressions, annotationStorage is passed to the xfa render in reftests.
2021-07-16 16:18:53 +09:00
{ "id": "xfa_bug1720182",
Update the file used with the `xfa_bug1720182` test-case The file used in this test-case is *identical* to, i.e. the md5 entry perfectly matches, the file used with the `xfa_bug1716380` test-case. While it's obviously fine to use the same PDF document in different reference-tests, note how we e.g. have both `eq` and `text` tests for one document, we should always avoid adding *duplicate* files in the `test/pdfs/` folder.
2022-02-08 22:05:53 +09:00
"file": "pdfs/xfa_bug1716380.pdf",
XFA - Checkboxes must be printed (bug 1720182) - to avoid future regressions, annotationStorage is passed to the xfa render in reftests.
2021-07-16 16:18:53 +09:00
"md5": "1351f816f0509fe750ca61ef2bd40872",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq",
"print": true,
"annotationStorage": {
"RadioButtonList2707": {
"value": "1"
},
"ComplainantFirstname2710": {
"value": "Foo"
},
"ComplainantLastname2711": {
"value": "Bar"
}
Update the file used with the `xfa_bug1720182` test-case The file used in this test-case is *identical* to, i.e. the md5 entry perfectly matches, the file used with the `xfa_bug1716380` test-case. While it's obviously fine to use the same PDF document in different reference-tests, note how we e.g. have both `eq` and `text` tests for one document, we should always avoid adding *duplicate* files in the `test/pdfs/` folder.
2022-02-08 22:05:53 +09:00
},
"about": "This *intentionally* uses the same file as test-case xfa_bug1716380."
XFA - Checkboxes must be printed (bug 1720182) - to avoid future regressions, annotationStorage is passed to the xfa render in reftests.
2021-07-16 16:18:53 +09:00
},
Ensure that the field value, for checkboxes, refers to an existing appearance state (bug 1720411) Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1720411
2021-07-15 02:31:09 +09:00
{ "id": "bug1720411",
"file": "pdfs/bug1720411.pdf",
"md5": "a3a3616d89d475b000373025fbd24735",
"rounds": 1,
"link": true,
"type": "eq",
"forms": true
},
XFA - Layout correctly a subform with row layout (bug 1718740) - Fix issues with subformSet elements which are not a real container.
2021-07-06 21:11:21 +09:00
{ "id": "xfa_bug1718740",
"file": "pdfs/xfa_bug1718740.pdf",
"md5": "fab4277f2c70fd1edb35f597f5fe6819",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Fix text positions (bug 1718741) - font line height is taken into account by acrobat when it isn't with masterpdfeditor: I extracted a font from a pdf, modified some ascent/descent properties thanks to ttx and the reinjected the font in the pdf: only Acrobat is taken it into account. So in this patch, line heights for some substituted fonts are added. - it seems that Acrobat is using a line height of 1.2 when the line height in the font is not enough (it's the only way I found to fix correctly bug 1718741). - don't use flex in wrapper container (which was causing an horizontal overflow in the above bug). - consequently, the above fixes introduced a lot of small regressions, so in order to see real improvements on reftests, I fixed the regressions in this patch: - replace margin by padding in some case where padding is a part of a container dimensions; - remove some flex display: some containers are wrongly sized when rendered; - set letter-spacing to 0.01px: it helps to be sure that text is not broken because of not enough width in Firefox.
2021-07-10 00:29:21 +09:00
{ "id": "xfa_bug1718741",
"file": "pdfs/xfa_bug1718741.pdf",
"md5": "1b80f8287cdbf9a67e4bff8be20b1bbd",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Handle correctly nested containers with lr-tb layout (bug 1718670) - and avoid to push a field with no dimensions when we have some available space in width in a parent.
2021-07-07 22:24:14 +09:00
{ "id": "xfa_bug1718670_1",
"file": "pdfs/xfa_bug1718670_1.pdf",
"md5": "06745be56a89acd80e5bdeddabb7cb7b",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
When no "V" entry exists, let the fieldValue fallback to the "DV" entry (issue 13823)
2021-07-30 23:15:41 +09:00
{ "id": "issue13823",
"file": "pdfs/issue13823.pdf",
"md5": "8ca53bba9b2c68f5cd87f13a963e6b6a",
"rounds": 1,
"link": true,
"type": "eq",
"forms": true
},
Fallback to font name matching, when checking for serif fonts (issue 13845) In order to handle fonts that specify completely bogus /Flags-entries, fallback to font name matching to determine if the font is a serif one.
2021-09-23 00:02:06 +09:00
{ "id": "issue13845",
"file": "pdfs/issue13845.pdf",
"md5": "7c6b675f61ae68a2e416f4aa26da567c",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "text"
},
XFA - An image can be a stream in the pdf (bug 1718521) - hrefs can be found in catalog > Names > XFAImages
2021-07-03 03:05:23 +09:00
{ "id": "xfa_bug1718521_1",
"file": "pdfs/xfa_bug1718521_1.pdf",
"md5": "9b89dd9e6a4c6c3258ca24debd806863",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
{ "id": "xfa_bug1718521_2",
"file": "pdfs/xfa_bug1718521_2.pdf",
"md5": "c23beb39e1c91a780da9d4b60cbd157f",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
{ "id": "xfa_bug1718521_3",
"file": "pdfs/xfa_bug1718521_3.pdf",
"md5": "5cc6fb1a65515518e3e64baa81e7a21e",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Don't fill when the fill element is not visible (bug 1718735)
2021-07-01 00:13:59 +09:00
{ "id": "xfa_bug1718735",
"file": "pdfs/xfa_bug1718735.pdf",
"md5": "1001f5c02c026943cbd37f646725d82f",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Replace deprecated break element (bug 1718053) - the break element has been deprecated in XFA 2.4 but some old documents can use it, so replace it with one (or more) of its possible substitutions: - breakBefore; - breakAfter; - overflow.
2021-06-27 22:02:53 +09:00
{ "id": "xfa_bug1718053",
"file": "pdfs/xfa_bug1718053.pdf",
"md5": "252d728d2c456dcb81699342a71c42ea",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
{ "id": "xfa_bug1717805",
"file": "pdfs/xfa_bug1717805.pdf",
"md5": "c68ccebd0d92b8fd70c465660458507f",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Don't fail xfa loading because of a JS subexpression in SOM expressions - Fix for one pdf in bug 1717668 (PDFIUM-292-0.pdf).
2021-07-07 17:32:53 +09:00
{ "id": "xfa_bug1717668_1",
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
"file": "pdfs/xfa_bug1717668_1.pdf",
"md5": "564ecff67be690b43c2a144ae5967034",
"link": true,
"rounds": 1,
"enableXfa": true,
Remove the `xfa_bug1716838` browser-test since it's a duplicate The md5 entry perfectly matches the `xfa_bug1717668_1` test-case, which means that we unnecessarily test the same exact document twice.
2022-02-01 20:05:19 +09:00
"type": "eq",
"about": "Also tests bug 1716838."
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
},
XFA - Don't fail xfa loading because of a JS subexpression in SOM expressions - Fix for one pdf in bug 1717668 (PDFIUM-292-0.pdf).
2021-07-07 17:32:53 +09:00
{ "id": "xfa_bug1717668_2",
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
"file": "pdfs/xfa_bug1717668_2.pdf",
"md5": "08aa8bf9fec5aa7b8ff13d9ba72ca8ac",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Don't fail xfa loading because of a JS subexpression in SOM expressions - Fix for one pdf in bug 1717668 (PDFIUM-292-0.pdf).
2021-07-07 17:32:53 +09:00
{ "id": "xfa_bug1717668_3",
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
"file": "pdfs/xfa_bug1717668_3.pdf",
"md5": "4ff2531dbefebabc3f128d4ae20552a4",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Don't fail xfa loading because of a JS subexpression in SOM expressions - Fix for one pdf in bug 1717668 (PDFIUM-292-0.pdf).
2021-07-07 17:32:53 +09:00
{ "id": "xfa_bug1717668_4",
"file": "pdfs/xfa_bug1717668_4.pdf",
"md5": "1c3dc4873ad6b84adb164ed69ed202f5",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Fix width of a container with lr-tb layout (bug 1718037)
2021-06-27 06:21:43 +09:00
{ "id": "xfa_bug1718037",
"file": "pdfs/xfa_bug1718037.pdf",
"md5": "a0b53d50e9faed9d57950a5159d5da12",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Get line height from the font - when the CSS line-height property is set to 'normal' then the value depends of the user agent. So use a line height based on the font itself and if for any reasons this value is not available use 1.2 as default. - it's a partial fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1717681.
2021-06-23 18:10:20 +09:00
{ "id": "xfa_bug1717681",
"file": "pdfs/xfa_bug1717681.pdf",
"md5": "435b1eae7e017b1a932fe204d1ba8be5",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
Add PDFs from #1773 to the reftests
2021-06-23 19:58:26 +09:00
{ "id": "xfa_imm5257e",
"file": "pdfs/xfa_imm5257e.pdf",
"md5": "5b8dcc12d7461100f48b4b427c0f976e",
"rounds": 1,
"link": true,
"enableXfa": true,
"type": "eq"
},
XFA - Add margins if needed after having layout some text
2021-06-21 00:39:54 +09:00
{ "id": "xfa_bug1716380",
"file": "pdfs/xfa_bug1716380.pdf",
"md5": "1351f816f0509fe750ca61ef2bd40872",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
{ "id": "xfa_dhl_shipment",
"file": "pdfs/xfa_dhl_shipment.pdf",
"md5": "503ece429d69e7d626d6932a475fbe63",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Add support for overflow element - and fix few bugs: - avoid infinite loop when layout the document; - avoid confusion between break and layout failure; - don't add margin width in tb layout when getting available space.
2021-06-14 01:57:51 +09:00
{ "id": "xfa_bug1716047",
"file": "pdfs/xfa_bug1716047.pdf",
"md5": "2f524163bd8397f43d195090978c3b56",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Match font family correctly - partial fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1716980; - some pdf can contain an invalid font family (e.g. 'Windings 3') so in this case remove the space; - the font family in typeface attribute doesn't always match the one defined in the FontDescriptor dictionary.
2021-06-20 21:03:59 +09:00
{ "id": "xfa_bug1716980",
"file": "pdfs/xfa_bug1716980.pdf",
"md5": "3d7598b9548d78f209d013c485162e9a",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Add support for access property - it's a partial fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1716816.
2021-06-21 01:56:14 +09:00
{ "id": "xfa_bug1716816",
"file": "pdfs/xfa_bug1716816.pdf",
"md5": "3051cd18db7839bc4953df35b52cf3e0",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - By default a text ui has only one line when in a field element - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1716809.
2021-06-17 03:15:24 +09:00
{ "id": "xfa_bug1716809",
"file": "pdfs/xfa_bug1716809.pdf",
"md5": "7192f9e27e8b84776d107f57cbe353d5",
"link": true,
"rounds": 1,
"enableXfa": true,
Revert "Revert "XFA - Fix the way to select page on breaking"" - and fix the error which caused the backout: add an $extra property when creating html. - switch to next content area when breaking on page area.
2021-06-21 23:02:33 +09:00
"type": "eq"
},
XFA - Fix layout issues - PR #13554 is buggy, so this patch aims to fix bugs. - check if a component fits into its parent in taking into account the parent layout. - introduce method isSplittable for template nodes to know if a component can be splitted in case of overflow.
2021-06-16 23:02:41 +09:00
{ "id": "xfa_candidate_petitions",
"file": "pdfs/xfa_candidate_petitions.pdf",
"md5": "0db96a00667f8f58f94cf81022e69341",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Add support for overflow element - and fix few bugs: - avoid infinite loop when layout the document; - avoid confusion between break and layout failure; - don't add margin width in tb layout when getting available space.
2021-06-14 01:57:51 +09:00
{ "id": "xfa_annual_expense_report",
"file": "pdfs/xfa_annual_expense_report.pdf",
"md5": "06866e7a6bbc0346789208ef5f6e885c",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
{ "id": "xfa_annual_voting_survey",
"file": "pdfs/xfa_annual_voting_survey.pdf",
"md5": "92239648ea1bf189435c927e498c4ec9",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Display rectangle, line and arc
2021-06-05 03:10:35 +09:00
{ "id": "xfa_fish_licence",
"file": "pdfs/xfa_fish_licence.pdf",
"md5": "9b993128bbd7f4217098fd44116ebec2",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Default background in rectangle is white - Fix a typo in order to open the pdf in issue #13679 - After fixing the fill default color there wer some regressions because of z-index and when fixing z-index there were some regressions because of borders - So fix the borders rendering.
2021-07-07 00:52:05 +09:00
{ "id": "xfa_issue13679",
"file": "pdfs/xfa_issue13679.pdf",
"md5": "b7231495f0c063435e7cfb92b4f281a3",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Handle shorcut in SOM expression (issue #13994)
2021-09-10 02:54:45 +09:00
{ "id": "xfa_issue13994",
"file": "pdfs/xfa_issue13994.pdf",
"md5": "787ad7cfbb822bb4f80e2243305c9f0c",
"link": true,
"rounds": 1,
"lastPage": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Avoid to put something in very small areas - it aims to fix #13855.
2021-08-03 23:22:52 +09:00
{ "id": "xfa_issue13855",
"file": "pdfs/xfa_issue13855.pdf",
"md5": "0aaaf62ff979c7837c2c63df44456238",
"link": true,
"rounds": 1,
"firstPage": 3,
"lastPage": 3,
"enableXfa": true,
"type": "eq"
},
XFA - A rectangle must have the width of its parent but without inner margins - it aims to fix #13584; - to avoid bad rendering because of clipping just set overflow to visible on SVG element.
2021-07-14 22:36:00 +09:00
{ "id": "xfa_issue13584",
"file": "pdfs/xfa_issue13584.pdf",
"md5": "c41af0754dabd81996a0d54db1900beb",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Use fake MyriadPro as a fallback for missing fonts - aims to fix #13597.
2021-07-10 23:18:45 +09:00
{ "id": "xfa_issue13597",
"file": "pdfs/xfa_issue13597.pdf",
"md5": "1ed9338f7e797789c0b41182f51b9002",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
Always prefer the post-table for TrueType fonts with (0, x) cmap-tables (issue 13433) While I don't know if this is necessarily the "correct" solution, it does fix issue 13433 without breaking any of the existing reference-tests.
2021-09-01 19:22:49 +09:00
{ "id": "issue13433",
"file": "pdfs/issue13433.pdf",
"md5": "4038cd87ff48fd54b3c4a36593d2ba03",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
XFA - Avoid to have containers not pushed in the html - it aims to fix issue #13668.
2021-07-12 02:12:50 +09:00
{ "id": "xfa_issue13668",
"file": "pdfs/xfa_issue13668.pdf",
"md5": "8a5ed3c8a58b425b1ec53329334a0f5b",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Fix indentation for justified paragraph - and ceil the reserve for a caption to avoid to split it; - both issues are present in the pdf in issue #13633.
2021-07-04 01:06:59 +09:00
{ "id": "xfa_issue13633",
"file": "pdfs/xfa_issue13633.pdf",
"md5": "e5b0d09285ca6a140eba08d740be0ea0",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Remove quotes of font name in xhtml
2021-06-28 01:05:05 +09:00
{ "id": "xfa_issue13631",
"file": "pdfs/xfa_issue13631.pdf",
"md5": "bf24397950dc8b8fcb7e91299af1315a",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Remove empty pages - it aims to fix #13583; - fix the switch to breakBefore target; - force the layout of an unsplittable element on an empty page; - don't fail when there is horizontal overflow (except in lr-tb); - handle correctly overflow in the same content area (bug 1717805, bug 1717668); - fix a typo in radial gradient first argument.
2021-06-21 16:38:50 +09:00
{ "id": "xfa_issue13611",
"file": "pdfs/xfa_issue13611.pdf",
"md5": "e713fb46a6b4637660010f1850559ff6",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Implement aspect property on image element - it aims to fix issue #13634; - move some img-related functions in test/drivers.js in order to have images in xfa reftests.
2021-06-28 00:17:44 +09:00
{ "id": "xfa_issue13634",
"file": "pdfs/xfa_issue13634.pdf",
"md5": "459a04045470811cbab6671772929d3d",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Fix error when creating a new data node - fix for issue #13556; - value in a field can be empty.
2021-06-14 18:33:03 +09:00
{ "id": "xfa_issue13556",
"file": "pdfs/xfa_issue13556.pdf",
"md5": "197e93a010763c3b6f9845595ee66c70",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Handle correctly subformSet - it aims to avoid to loop forever when opening pdf in #13213; - the idea is to consider subformSet as inexistent when running in the tree. So if we've subformA > subformSet > subformB then subformB will be visited as a direct child of subformA.
2021-06-12 00:49:13 +09:00
{ "id": "xfa_issue13213",
"file": "pdfs/xfa_issue13213.pdf",
"md5": "8a0e3179bffbac721589d1b1df863b49",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
Improve handling of named destinations in out-of-order NameTrees (PR 10274 follow-up) According to the specification, see https://web.archive.org/web/20210404042322if_/https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G6.2384179, the keys of a NameTree/NumberTree should be ordered. For corrupt PDF files, which violate this assumption, it's thus possible that trying to lookup a single entry fails. Previously, in PR 10274, we implemented a fallback that only applies to the "bottom" node of a NameTree/NumberTree, which in general might not actually help for sufficiently corrupt NameTree/NumberTree data. Instead we remove the current *limited* fallback from `NameOrNumberTree.get`, and defer to the call-site to handle this case explicitly e.g. by using `NameOrNumberTree.getAll` for data where that makes sense. For well-formed documents, these changes should *not* lead to any additional data fetching/parsing. Finally, as part of these changes, the validation of named destination data is improved in the `Catalog` and a new unit-test is also added.
2021-05-21 20:58:33 +09:00
{ "id": "issue10272",
"file": "pdfs/issue10272.pdf",
"md5": "bf3b2f74c6878d38a70dc0825f1b9a02",
"link": true,
"type": "other"
},
Avoid truncating inline images, where the data and the "EI" marker is glued together (issue 10388) (#10436) Thanks to the *excellent* debugging done by @janpe2, this was easy to fix!
2019-01-13 04:31:23 +09:00
{ "id": "issue10388",
"file": "pdfs/issue10388_reduced.pdf",
"md5": "62a6b2adbea1535432bd94a3516e2d4c",
"rounds": 1,
"link": false,
"type": "eq"
},
Overwrite maxSizeOfInstructions in maxp with computed value. In issue #7507 the value is less than the actuall max size of the glyph instructions causing OTS to fail the font.
2017-09-26 09:24:21 +09:00
{ "id": "issue7507",
"file": "pdfs/issue7507.pdf",
"md5": "f7aeaafe0c89b94436e94eaa63307303",
"rounds": 1,
"link": false,
"type": "eq"
},
Use the correct stream position when reading `maxSizeOfInstructions` from the `maxp` table (issue 9458) Please refer to the `maxp` table specification, found at https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6maxp.html. Fixes 9458.
2018-02-08 04:53:44 +09:00
{ "id": "issue9458",
"file": "pdfs/issue9458.pdf",
"md5": "ee54358d8b2fdc75dc8da5220cf8e8da",
"rounds": 1,
"link": false,
"type": "eq"
},
Add support for TrueType (0, 0) cmap tables (issue 5501 and 5574)
2015-01-11 22:54:12 +09:00
{ "id": "issue5501",
"file": "pdfs/issue5501.pdf",
"md5": "55a60699728fc92f491a2d7d490474e4",
"rounds": 1,
"link": false,
"type": "eq"
Fix two cmap related issues. In issue #8707, there's a char code mapped to a non- existing glyph which shouldn't be drawn. However, we saw it was missing and tried to then use the post table and end up mapping it incorrectly. This illuminated a problem with issue #5704 and bug 893730 where glyphs disappeared after above fix. This was from the cmap returning the wrong glyph id. Which in turn was caused because the font had multiple of the same type of cmap table and we were choosing the last one. Now, we instead default to the first one. I'm unsure if we should instead be merging the multiple cmaps, but using only the first one works.
2017-08-04 14:19:36 +09:00
},
For non-embedded fonts, map softhyphen (0x00AD) to regular hyphen (0x002D) (issue 9084) In the PDF file, the `ToUnicode` data first maps the hyphen correctly, and then *overwrites* it to point to the softhyphen instead. That one cannot be rendered in browsers, and an empty space thus appear instead. Fixes 9084.
2017-10-31 21:01:29 +09:00
{ "id": "issue9084",
"file": "pdfs/issue9084.pdf",
"md5": "5570ec01cc869d299fec1b2f68926a08",
"rounds": 1,
"link": false,
"type": "eq"
},
Add basic support for non-embedded Calibri fonts (issue 9195) There's a number of issues with the fonts in the referenced PDF file. First of all, they contain broken `ToUnicode` data (`NUL` bytes all over the place). However even if you skip those, the `ToUnicode` data appears to contain nothing but a `IdentityH` CMap which won't help provide a proper glyph mapping. The real issue actually turns out to be that the PDF file uses the "Calibri" font[1], but doesn't include any font files. Since that one isn't a standard font, and uses a fairly different CID to GID map compared to the standard fonts, we're not able to render the file even remotely correct. To work around this, I'm thus proposing that we include a (incomplete) glyph map for Calibri, and fallback to the standard Helvetica font. Obviously this isn't going to look perfect, but it's really the best that we can hope to achieve given that the PDF file is missing the necessary font data. Finally, please note that none of the PDF readers I've tried (Adobe Reader, PDFium in Chrome) were able to extract the text (which isn't very surprising, given the broken `ToUnicode` data). Fixes 9195. --- [1] According to Wikipedia, see https://en.wikipedia.org/wiki/Calibri, Calibri is (primarily) a Windows font.
2017-12-03 22:02:22 +09:00
{ "id": "issue9195",
"file": "pdfs/issue9195.pdf",
"md5": "90e78a11abdc6c5ae79b8b95cfbb1895",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Let `Lexer.getNumber` treat a single decimal point as zero (issue 9252) This is consistent with the behaviour in Adobe Reader.
2018-06-19 16:37:56 +09:00
{ "id": "issue9252",
"file": "pdfs/issue9252.pdf",
"md5": "c7d039d808d9344a95d2c9cfa7586ca3",
"rounds": 1,
"link": false,
"type": "eq"
},
Add basic validation of the 'trailer' dictionary candidates in `XRef.indexObjects` (issue 9418) This patch avoids choosing a (possible) 'trailer' dictionary that `XRef.parse` and/or the `Catalog` constructor/methods will reject anyway. Since `XRef.indexObjects` is already parsing the entire PDF file, the extra dictionary look-ups added here shouldn't matter much. Besides, this is a fallback code-path that only applies to corrupt PDF files anyway.
2018-06-19 18:31:31 +09:00
{ "id": "issue9418",
"file": "pdfs/issue9418.pdf",
"md5": "32ecad8098acb1938539d47944ecb54b",
"rounds": 1,
"link": false,
"type": "eq"
},
XFA - Add a missing method to `XFAAttribute`, to prevent breaking errors (issue 13748) *This is yet another case where I've got no idea if the patch is correct, but it does at least fix a breaking error :-)* Note how in the [`Binder._bindValue` method](https://github.com/mozilla/pdf.js/blob/683ce66a48cd54fa48e96e1925277c134859e76c/src/core/xfa/bind.js#L92-L93), we're assuming that if a `data`-value exists then it'll also be possible to actually access it. For the `XFAAttribute`-implementation however, the second method is missing and that's what causes the breaking errors in issue 13748. Please note that another possible way of "fixing" the error wouldn't been to simply change the exists-check to return `false`, and I could see that being a preferred solution. However, the reason for submitting the current patch is that we get *fewer* warnings about Nodes with mis-matched types this way.
2021-07-21 00:14:20 +09:00
{ "id": "issue13748",
"file": "pdfs/issue13748.pdf",
"md5": "de0e4dde2890b9ff145a3184831bae02",
"link": true,
"rounds": 1,
"lastPage": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Handle `startIndex` correctly in the `Template.$toHTML` method (issue 13751) *Please note:* The PDF document in issue 13751 is *dynamically* created (in e.g. Adobe Reader), with pages added when certain buttons are clicked, hence this patch simply fixes the breaking error and nothing more. It looks like the current code contains a little bit too much copy-and-paste from the *similar* `index` branch above, since we cannot set the `startIndex` to a negative value. Note how it's being used to initialize the loop-variable, which is then used to lookup values in an Array and accessing the `-1`th element of an Array obviously makes no sense.
2021-07-21 16:06:25 +09:00
{ "id": "issue13751",
"file": "pdfs/issue13751.pdf",
"md5": "b9960bfa99be3573d9c32a9d55e5b7da",
"link": true,
"rounds": 1,
"lastPage": 1,
"enableXfa": true,
"type": "eq"
},
XFA - Prevent breaking errors in `Binder`, when `searchNode` doesn't return data (issue 13756) As can be seen in the code (see below), the `searchNode` helper function will return `null` in some cases and all of its call-sites should protect against that before attempting to access the returned data. While only one of these changes were necessary to fix the breaking errors in issue 13756, in order to prevent future bugs I've added similar defensive code throughout this file. - https://github.com/mozilla/pdf.js/blob/07955fa1d31df62fd668a15f58cd40b29a82bd63/src/core/xfa/som.js#L169 - https://github.com/mozilla/pdf.js/blob/07955fa1d31df62fd668a15f58cd40b29a82bd63/src/core/xfa/som.js#L239 - https://github.com/mozilla/pdf.js/blob/07955fa1d31df62fd668a15f58cd40b29a82bd63/src/core/xfa/som.js#L254
2021-07-20 00:45:10 +09:00
{ "id": "issue13756",
"file": "pdfs/issue13756.pdf",
"md5": "67040c6df3b5039fcbc81bf63b7c7f98",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
},
When parsing corrupt documents, avoid inserting obviously broken data in the XRef-table (issue 13783) In cases where even the very *first* attempt at reading from an object will throw, simply ignoring such objects will help improve rendering of *some* corrupt documents. Note that this will lead to more parsing in some cases, but considering that this only applies to *corrupt* documents that shouldn't be a big deal.
2021-07-24 00:37:55 +09:00
{ "id": "issue13783",
"file": "pdfs/issue13783.pdf",
"md5": "6958d827afa566efbd82f53271ea5cd6",
"link": true,
"rounds": 1,
"firstPage": 7,
"lastPage": 7,
"type": "eq"
},
Allow `StreamsSequenceStream.readBlock` to skip sub-streams with errors (issue 13794) This patch makes use of the existing `ignoreErrors` option, thus allowing a page to continue parsing/rendering even if (some of) its sub-streams are corrupt. Obviously this may cause *part* of a page to be broken/missing, however it should be better than (potentially) rendering nothing. Also, to the best of my knowledge, this is the first bug of its kind that we've encountered. To avoid having to pass in a bunch of, for a `BaseStream`-instance, mostly unrelated parameters when initializing a `StreamsSequenceStream`-instance, I settled on utilizing a callback function instead to allow conditional Error-suppression. Note that the `StreamsSequenceStream`-class is a *special* stream-implementation that we only use when the `/Contents`-entry, in the `/Page`-dictionary, consists of an Array with streams.
2021-07-26 22:34:14 +09:00
{ "id": "issue13794",
"file": "pdfs/issue13794.pdf",
"md5": "6b4c099e04c9df145198740f2bf75c48",
"link": true,
"rounds": 1,
"firstPage": 3,
"type": "eq"
},
Add support for TrueType Collection fonts (issue 9262) The specification can be found at https://www.microsoft.com/typography/otspec/otff.htm, under the "Font Collections" heading. Fixes 9262.
2017-12-15 08:23:56 +09:00
{ "id": "issue9262",
"file": "pdfs/issue9262_reduced.pdf",
"md5": "5347ce2d7b3866625c22e115fd90e0de",
"rounds": 1,
"link": false,
"type": "eq"
},
Attempt to actually resolve ColourSpace names in accordance with the specification (issue 9285) Please refer to the PDF specification, in particular http://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G7.3801570 > A colour space shall be specified in one of two ways: > - Within a content stream, the CS or cs operator establishes the current colour space parameter in the graphics state. The operand shall always be name object, which either identifies one of the colour spaces that need no additional parameters (DeviceGray, DeviceRGB, DeviceCMYK, or some cases of Pattern) or shall be used as a key in the ColorSpace subdictionary of the current resource dictionary (see 7.8.3, "Resource Dictionaries"). In the latter case, the value of the dictionary entry in turn shall be a colour space array or name. A colour space array shall never be inline within a content stream. > > - Outside a content stream, certain objects, such as image XObjects, shall specify a colour space as an explicit parameter, often associated with the key ColorSpace. In this case, the colour space array or name shall always be defined directly as a PDF object, not by an entry in the ColorSpace resource subdictionary. This convention also applies when colour spaces are defined in terms of other colour spaces.
2017-12-20 23:35:04 +09:00
{ "id": "issue9285",
"file": "pdfs/issue9285.pdf",
"md5": "aa53ad98a72fd76c414101927951448b",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Fix two cmap related issues. In issue #8707, there's a char code mapped to a non- existing glyph which shouldn't be drawn. However, we saw it was missing and tried to then use the post table and end up mapping it incorrectly. This illuminated a problem with issue #5704 and bug 893730 where glyphs disappeared after above fix. This was from the cmap returning the wrong glyph id. Which in turn was caused because the font had multiple of the same type of cmap table and we were choosing the last one. Now, we instead default to the first one. I'm unsure if we should instead be merging the multiple cmaps, but using only the first one works.
2017-08-04 14:19:36 +09:00
{ "id": "issue8707",
"file": "pdfs/issue8707.pdf",
"md5": "d3dc670adde9ec9fb82c974027033029",
"rounds": 1,
"link": false,
"type": "eq"
Add support for TrueType (0, 0) cmap tables (issue 5501 and 5574)
2015-01-11 22:54:12 +09:00
},
For /Filter entries containing `Name`s, ignore the /DecodeParms entry if it contains an Array (issue 8895)
2017-09-16 04:23:47 +09:00
{ "id": "issue8895",
"file": "pdfs/issue8895.pdf",
"md5": "098658008fc2bf7d433fd0d6d468a9e1",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Handle PDF files with missing 'endobj' operators, by searching for the "obj" string rather than "endobj" in `XRef.indexObjects` (issue 9105) This patch refactors the searching for 'endobj', to try and find the next occurance of "obj" and then check if it was in fact an 'endobj' and continue searching otherwise. This approach is used to avoid having to first find 'endobj', and then re-check the entire contents of the object and having to run (potentially expensive) regular expressions on arbitrary long strings. Fixes 9105.
2017-12-09 00:37:12 +09:00
{ "id": "issue9105",
"file": "pdfs/issue9105_reduced.pdf",
"md5": "f3889f7c7b60e1ab998aac430cc7e08e",
"rounds": 1,
"link": false,
"type": "eq"
},
Re-factor searching for incomplete objects in `XRef.indexObjects` (issue 15803) When trying to find incomplete objects, i.e. those missing the "endobj"-string at the end, there's unfortunately a number of possible operators that we need to check for. Otherwise we could miss e.g. the "trailer" at the end of a corrupt PDF document, which is why the referenced document didn't work. Currently we do all searching on the "raw" bytes of the PDF document, for efficiency, however this doesn't really work when we need to check for *multiple* potential command-strings. To keep the complexity manageable we'll instead use regular expressions here, but we can at least avoid creating lots of substrings thanks to the `RegExp.lastIndex` property; which is well supported across browsers according to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/lastIndex#browser_compatibility Note that this repeated regular expression usage could perhaps be slightly less efficient than the old code, however this method is only invoked for corrupt PDF documents.
2022-12-20 07:01:09 +09:00
{ "id": "issue15803",
"file": "pdfs/issue15803.pdf",
"md5": "e501a4418d4ece5be7ce4e8acf029100",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
"annotations": true
},
Relax the /Pages dictionary /Count check for corrupt documents (issue 9105) After PR 14311, and follow-up patches, we no longer require that the /Count entry (in the /Pages dictionary) is either present or even valid in order to parse/render a PDF document. Hence it seems strange to keep this requirement for *corrupt* PDF documents, when trying to find a usable `trailer` in the `XRef.indexObjects` method.
2022-10-19 19:28:25 +09:00
{ "id": "issue9105_other",
"file": "pdfs/issue9105_other.pdf",
"md5": "4c8b9c2cceb9c5d621e1d50b3dc38efc",
"rounds": 1,
"link": false,
"type": "eq"
},
Add support for optional marked content. Add a new method to the API to get the optional content configuration. Add a new render task param that accepts the above configuration. For now, the optional content is not controllable by the user in the viewer, but renders with the default configuration in the PDF. All of the test files added exhibit different uses of optional content. Fixes #269. Fix test to work with optional content. - Change the stopAtErrors test to ensure the operator list has something, instead of asserting the exact number of operators.
2020-07-15 07:17:27 +09:00
{ "id": "issue269_1",
"file": "pdfs/issue269_1.pdf",
"md5": "ab932f697b4d2e2bf700de15a8efea9c",
"rounds": 1,
"type": "eq",
"about": "Optional marked content."
},
{ "id": "issue269_2",
"file": "pdfs/issue269_2.pdf",
"md5": "0f553510850ee17c87fbab3fac564165",
"rounds": 1,
"type": "eq",
"about": "Optional marked content."
},
{ "id": "issue11144_reduced",
"file": "pdfs/issue11144_reduced.pdf",
"md5": "09e3e771ebd6867558074e900adb54b9",
"rounds": 1,
"type": "eq",
"about": "Optional marked content."
},
{ "id": "issue12007_reduced",
"file": "pdfs/issue12007_reduced.pdf",
"md5": "3aa9d8a0c5ff8594245149f9c7379613",
"rounds": 1,
"type": "eq",
"about": "Optional marked content."
},
Handle more cases of corrupt PDF files with missing 'endobj' operators, where the "obj" string is immediately followed by the dictionary (PR 9288 follow-up)
2019-01-11 01:49:33 +09:00
{ "id": "issue10438",
"file": "pdfs/issue10438_reduced.pdf",
"md5": "bb26f68493e33af17b256a6ffe777a24",
"rounds": 1,
"link": false,
"type": "eq"
},
Create the glyph mapping correctly for composite Type1, i.e. CIDFontType0, fonts (issue 11740) This updates `Type1Font.getGlyphMapping` with a code-path "borrowed" from `CFFFont.getGlyphMapping`.
2020-03-25 22:06:01 +09:00
{ "id": "issue11740",
"file": "pdfs/issue11740_reduced.pdf",
"md5": "f3f2957f171af52229c6e749e8a5572b",
"rounds": 1,
"type": "eq"
},
Ensure that `XRef.indexObjects` can handle object numbers with zero-padding (issue 10491) All objects in the PDF document follow this pattern: ``` 0000000001 0 obj << % Some content here... >> endobj 0000000002 0 obj << % More content here... endobj ```
2019-01-25 06:27:36 +09:00
{ "id": "issue10491",
"file": "pdfs/issue10491.pdf",
"md5": "0759ec46739b13bb0b66170a18d33d4f",
"rounds": 1,
"link": true,
"firstPage": 2,
"type": "eq"
},
Attempt to handle corrupt PDF documents that contains path operators inside of text object (issue 10542) First of all, while this simple approach appears to work OK in practice I'm not sure if it's the best way of addressing the problem (assuming that you even want to). Second of all, while the solution implemented here only requires tracking/checking one new boolean in order for this to work, I'm nonetheless not entirely happy about this since it will add additional overhead (albeit *very* small) to the parsing of path operators in PDF documents just for a handful of *corrupt* ones.
2019-04-22 00:03:38 +09:00
{ "id": "issue10542",
"file": "pdfs/issue10542_reduced.pdf",
"md5": "92406cb903be6c7a63221ba61fcb8eaf",
"rounds": 1,
"link": false,
"type": "eq"
},
support tiff predictor for 16bit (for issue #6289) This does the same for 16 bit as the existing 8 bit tiff predictor code, an addition of the last word to this word. The last two "& 0xFF" may or may not be needed, I see this isn't done in the 8 bit code, but I'm not a JS developer.
2017-09-18 01:06:43 +09:00
{ "id": "issue6289",
"file": "pdfs/issue6289.pdf",
"md5": "0869f3d147c734ec484ffd492104095d",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Fallback to the |Dummy| Pattern when we fail to parse a Shading Pattern (issue 5509)
2014-12-01 05:15:18 +09:00
{ "id": "issue5509",
"file": "pdfs/issue5509.pdf",
"md5": "1975ef8db7355b1d691bc79d0749574b",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "load"
},
Fix color of image masks inside uncolored patterns
2017-09-06 19:41:48 +09:00
{ "id": "pr8808",
"file": "pdfs/pr8808.pdf",
"md5": "bdac6051a98fd8dcfc5344b05fed06f4",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Ensure that |get fingerprint| doesn't fail if the ID is not an array (issue 5599) According to the [PDF specification](http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=51) the `ID` should be an array. To prevent errors if the PDF file violates that part of the spec, check that the `ID` is actually an array. Fixes 5599.
2014-12-30 23:43:04 +09:00
{ "id": "issue5599",
"file": "pdfs/issue5599.pdf",
"md5": "529a4a9409ac024aeb57a047210280fe",
"rounds": 1,
"link": false,
"type": "load"
},
Test for text layer issue 1045.
2015-11-06 23:54:50 +09:00
{ "id": "issue1045",
"file": "pdfs/issue1045.pdf",
"md5": "61d7e9bfbc03cd457dcefeab3e78a687",
"rounds": 1,
"link": false,
"type": "text"
},
Skip mapping of CIDFontType2 glyphs when the font either has a |IdentityToUnicodeMap| or a |toUnicodeMap| with 65536 elements (issue 5677) This patch slightly extends the heuristics used when trying to skip mapping of missing glyphs. Fixes 5677.
2015-06-19 04:53:15 +09:00
{ "id": "issue5677",
"file": "pdfs/issue5677.pdf",
"md5": "c9101578fcb806269145132724d24ac1",
"rounds": 1,
"link": false,
"type": "eq"
},
Extend `getSupplementalGlyphMapForCalibri` with more entries (issue 15443)
2022-09-16 05:19:16 +09:00
{ "id": "issue15443",
"file": "pdfs/issue15443.pdf",
"md5": "95a9e28b3f2754aa310f3379e01d781d",
"rounds": 1,
"type": "eq"
},
Ensure that the `baseTransform` is applied when rendering annotations Fixes 3350. Fixes 5946. Fixes 6334. Fixes 6722. Probably fixes 3826 (since the PDF files are no longer available, I cannot confirm it).
2015-12-28 22:10:30 +09:00
{ "id": "issue5946",
"file": "pdfs/issue5946.pdf",
"md5": "1217a3c8e2ee4ceb96d85a2f27e437b4",
"rounds": 1,
"link": false,
"type": "eq"
},
Sanitize name index in compile phase of CFF. Fixes #8960
2017-10-19 10:33:35 +09:00
{ "id": "issue8960_reduced",
"file": "pdfs/issue8960_reduced.pdf",
"md5": "12ccf71307f4b5bd4148d5f985ffde07",
"rounds": 1,
"link": false,
"type": "eq"
},
Always traverse the entire parent chain in Page_getInheritedPageProp (issue 5954) This enables us to find resources placed on multiple levels of the tree. Fixes 5954.
2015-05-20 22:08:55 +09:00
{ "id": "issue5954",
"file": "pdfs/issue5954.pdf",
"md5": "4f60ec0d9bbeec845b681242b8982361",
"rounds": 1,
"link": false,
"type": "eq"
},
Ensure that we don't ignore `0` values in `Page.getInheritedPageProp` (issue 8125) It appears that I accidentally broke this in PR 6065, sorry about that! The issue in this particular PDF file is that there's `/Rotate` entries on different levels of the `/Pages` tree. We're supposed to use the `/Rotate` entry in the `/Page` dict (which is `0`), but because of an incorrect condition we instead ended up with the one from the `/Pages` dict (which is `180`). Fixes 8125.
2017-03-03 20:22:55 +09:00
{ "id": "issue8125",
"file": "pdfs/issue8125.pdf",
"md5": "2073d699ea82156682542f811300b3e8",
"rounds": 1,
"link": false,
"type": "eq"
},
Try to recover when encountering JPEG markers with too short marker lengths (issue 8169) The issue with the JPEG image in question, is that the COM (Comment) marker has an incorrect length entry. Fixes 8169.
2017-03-17 18:29:08 +09:00
{ "id": "issue8169",
"file": "pdfs/issue8169.pdf",
"md5": "62fd6479f9e1c8c5ce8cba6b1781d0a5",
"rounds": 1,
"link": true,
"type": "eq"
Try harder to find the next valid JPEG marker when decoding Scan data (issue 8182, issue 8189) Tentatively fixes 8182 and fixes 8189.
2017-03-24 00:08:59 +09:00
},
{ "id": "issue8182",
"file": "pdfs/issue8182.pdf",
"md5": "e295ae13dcbefd449f9a4957aed5e582",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
Try to recover when encountering JPEG markers with too short marker lengths (issue 8169) The issue with the JPEG image in question, is that the COM (Comment) marker has an incorrect length entry. Fixes 8169.
2017-03-17 18:29:08 +09:00
},
Attempt to find the next valid marker when encountering invalid image data in `JpegImage.parse` (issue 9425) In the JPEG images in the referenced PDF file, the DHT (Define Huffman Tables) segments contain more data than expected based on the length parameter. Fixes 9425.
2018-02-01 18:35:38 +09:00
{ "id": "issue9425",
"file": "pdfs/issue9425.pdf",
"md5": "cb5e99c9ada308304ca2dfcb7f72e3a0",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Attempt to handle corrupt PDF documents that inline Page dictionaries in a Kids array (issue 9540) According to the specification, see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G6.1942297, the contents of a Kids array should be indirect objects.
2018-03-12 22:00:37 +09:00
{ "id": "issue9540",
"file": "pdfs/issue9540.pdf",
"md5": "7de7979270c9136bdd737428185fbbed",
"rounds": 1,
"link": true,
"type": "eq"
},
Handle missing encoding differences array
2011-09-21 07:42:52 +09:00
{ "id": "txt2pdf",
"file": "pdfs/txt2pdf.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "02cefa0f5e8d96313bb05163b2f88c8c",
Handle missing encoding differences array
2011-09-21 07:42:52 +09:00
"link": true,
"rounds": 1,
"type": "load"
Ignore previously parsed xref streams
2011-09-22 02:04:21 +09:00
},
Request all data, rather than throwing, when encountering general errors in `ObjectLoader._walk` (issue 9462, PR 3289 follow-up) *As far as I can tell, this has been broken ever since PR 3289 (back in 2013) without anyone noticing.* For any non-`MissingDataException` errors encountered in `ObjectLoader._walk`, we're simply throwing immediately which thus has the potential to *completely* break rendering of an entire page. In practice this is obviously only an issue for PDF documents which are in one way or another corrupt, since that's the only way that `XRef.fetch` will throw non-`MissingDataException` errors. To make matters worse these errors are *intermittent*, since they can only occur if the document is still loading when the `ObjectLoader`-code runs (note the early return in `ObjectLoader.load`). Please note that we cannot simply catch the error and let "normal" parsing continue in `ObjectLoader._walk`, since that could lead to errors elsewhere given that resources "below" the current one (in the graph) might not be checked as intended then. All-in-all, the only way to make absolutely sure that we won't cause *unexpected* `MissingDataException`s somewhere else in the code-base is to fallback to fetching the *entire* document in this edge-case.
2021-02-06 22:04:05 +09:00
{ "id": "issue9462",
"file": "pdfs/issue9462.pdf",
"md5": "0a2895b0aa8a8ef730a20b4116cd996c",
"rounds": 1,
"link": true,
"firstPage": 3,
"lastPage": 3,
"type": "eq"
},
Ignore previously parsed xref streams
2011-09-22 02:04:21 +09:00
{ "id": "f1040",
"file": "pdfs/f1040.pdf",
Clean up test PDF references
2013-12-17 09:37:10 +09:00
"md5": "7323b50c6d28d959b8b4b92c469b2469",
Ignore previously parsed xref streams
2011-09-22 02:04:21 +09:00
"link": true,
"rounds": 1,
"type": "load"
Handle references for color space names that are defined in a dictionary
2011-09-23 05:17:28 +09:00
},
Prevent rendering `TextWidgetAnnotation`s in both the `core`/`display` layer (issue 7643)
2016-09-18 22:35:12 +09:00
{ "id": "f1040-annotations",
"file": "pdfs/f1040.pdf",
"md5": "7323b50c6d28d959b8b4b92c469b2469",
"link": true,
"rounds": 1,
"type": "eq",
"annotations": true
},
Enable regression testing for interactive forms
2016-09-07 23:06:18 +09:00
{ "id": "f1040-forms",
"file": "pdfs/f1040.pdf",
"md5": "7323b50c6d28d959b8b4b92c469b2469",
"link": true,
"rounds": 1,
"type": "eq",
"forms": true
},
Fix JBIG2 symbol offsets in text regions
2017-09-20 05:43:23 +09:00
{ "id": "jbig2_symbol_offset",
"file": "pdfs/jbig2_symbol_offset.pdf",
"md5": "6b22a0f838008fa4d8cb5b40ba095c48",
"rounds": 1,
"type": "eq"
},
[JBIG2] Ensure that the `decodeInteger` function returns valid integers (issue 15942) The JBIG2 images in this PDF document are corrupt enough that even Adobe Reader warns about it when opening the file. *Please note:* I don't really know the JBIG2 image format at all, however from a very brief look at the specification it seems that integers should be 32-bit.
2023-01-20 01:08:13 +09:00
{ "id": "issue15942",
"file": "pdfs/issue15942.pdf",
"md5": "d690e16e6a3a8486ebf7289a9c43ba39",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Don't map glyphs to Unicode position 0x0E33, i.e. Thai character SARA AM (bug1046314) *A similar approach as in PR 5705.* Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1046314. According to https://dxr.mozilla.org/mozilla-central/source/gfx/harfbuzz/src/hb-ot-shape-complex-thai.cc#270-365, `0x0E33` is treated as a special case (by the font shaping code in Firefox). Hence it seems reasonable to skip it when adjusting the font mapping.
2015-03-26 20:40:37 +09:00
{ "id": "bug1046314",
"file": "pdfs/bug1046314.pdf",
"md5": "fc658439f44cd2dd27c8bee7e7a8344e",
"rounds": 1,
"link": false,
"type": "eq"
},
Improve the handling of errors, in `PartialEvaluator.loadFont`, occuring in `PartialEvaluator.preEvaluateFont` (issue 12823) Currently any errors thrown in `preEvaluateFont`, which is a *synchronous* method, will not be handled at all in the `loadFont` method and we were thus failing to return an `ErrorFont`-instance as intended here. Also, add an *explicit* check in `PartialEvaluator.preEvaluateFont` to ensure that Type0-fonts always have a *valid* dictionary.
2021-01-07 19:25:09 +09:00
{ "id": "issue12823",
"file": "pdfs/issue12823.pdf",
"md5": "8391c63006ccc4b41c95de5e8c38deeb",
"rounds": 1,
"type": "eq"
},
Fall back to the |defaultEncoding| when no valid "post" table is found in TrueType fonts (bug 1050040) Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1050040. With this patch the file is completely readable, but given that the font is broken enough to be rejected by OTS the rendering differs slightly from Adobe Reader. *Note:* the PDF file is sufficiently broken that even Adobe Reader complains about the font, *and* also about another more general issue.
2015-04-02 23:26:14 +09:00
{ "id": "bug1050040",
"file": "pdfs/bug1050040.pdf",
"md5": "9076b29bd157e2646b457f29a4472a07",
"rounds": 1,
"link": false,
"type": "eq"
},
Fallback in `readCmapTable`, instead of using `error`, for TrueType fonts with unsupported cmap formats (bug 1200096) Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1200096. The problematic font has a `format 2` cmap, which we've never supported properly. Prior to PR 2606, we were able to fallback to a working state, despite not having proper support for that cmap format. Obviously the best/correct solution would be to implement actual support for more cmap formats[1]. However, I'm hoping that a simple patch will be OK for now, given that: - `format 2` cmaps seem to be quite rare in practice, since this has been broken for 2.5 years before anyone noticed. - Having a simple patch will make potential uplifts a lot easier. [1] See the specification at https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6cmap.html
2015-09-01 20:31:02 +09:00
{ "id": "bug1200096",
"file": "pdfs/bug1200096.pdf",
"md5": "b6bd8df094b5d511c13ed095d2a07515",
"rounds": 1,
"link": false,
"type": "eq"
},
Use the correct border-style for Annotations, when a dash array is specified (bug 1219400) Even though we cannot use the dash array in the display layer, at least ensure that we use the correct border-style.
2021-10-27 19:55:56 +09:00
{ "id": "bug1219400",
"file": "pdfs/bug1219400.pdf",
"md5": "a1554914cc9653d5ee0b9220657b334f",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
"annotations": true
},
Avoid truncating/breaking some Type3 glyphs in `compileType3Glyph` (bug 1245391, issue 10568) *Hopefully this patch makes sense, since I cannot claim to fully understand this function.* With the changes made in PR 3354 *some* Type3 glyph outlines are no longer rendering correctly, since the final paths were being accidentally ignored. The fact that Type3 fonts are not very common in PDF documents, and that most Type3 glyphs are unaffected by this regression, probably explains why this has gone unnoticed since 2013.
2019-02-22 00:25:34 +09:00
{ "id": "bug1245391",
"file": "pdfs/bug1245391_reduced.pdf",
"md5": "6c946045ee0f2f663f269717c0f1614a",
"rounds": 1,
"link": false,
"type": "eq"
},
Enforce line width to be at least 1px after applied transform * add a comment to explain how minimal linewidth is computed. * when context.linewidth < 1 after transform, firefox and chrome don't render in the same way (issue #12810). * set lineWidth to 1 after transform and before stroking - aims fix issue #12295 - a pixel can be transformed into a rectangle with both heights < 1. A single rescale leads to a rectangle with dim equals to 1 and the other to something greater than 1. * change the way to render rectangle with null dimensions: - right now we rely on the lineWidth set before "re" but it can be set after "re" and before "S" and in this case the rendering will be wrong. - render such rectangles as a single line.
2021-01-04 22:25:30 +09:00
{ "id": "issue12295",
"file": "pdfs/issue12295.pdf",
"md5": "c534f74866ba8ada56010d19b57231ec",
"rounds": 1,
"type": "eq"
},
Try to improve text-selection for Type3 fonts that utilize a non-default /FontMatrix (bug 1513120) For Type3 fonts text-selection is often not that great, and there's a couple of heuristics used to try and improve things. This patch simple extends those heuristics a bit, and fixes a pre-existing "naive" array comparison, but this all feels a bit brittle to say the least. The existing Type3 test-coverage isn't that great in general, and in particular Type3 `text` tests are few and far between, hence why this patch adds *two* different new `text` tests.
2019-03-08 20:55:44 +09:00
{ "id": "bug1245391-text",
"file": "pdfs/bug1245391_reduced.pdf",
"md5": "6c946045ee0f2f663f269717c0f1614a",
"rounds": 1,
"link": false,
"type": "text"
},
{ "id": "bug1513120-text",
"file": "pdfs/bug1513120_reduced.pdf",
"md5": "e88ad8b5bb385296f475ca51ce0d216d",
"rounds": 1,
"link": false,
"type": "text"
},
Add a heuristic to scale even single-char text, when the horizontal/vertical scaling differs significantly (issue 11713) At this point in time, compared to when the "ignore single-char" code was added, we *should* generally be doing a much better job of combining text into as few chunks as possible. However, there's still bad cases where we're not able to combine text as much as one would like, which is why I'm *not* proposing to simply measure/scale all text. Instead this patch will to only measure/scale single-char text in cases where the horizontal/vertical scale is off significantly, since that's were you'd expect bad text-selection behaviour otherwise. Note that most of the movement caused by this patch is with Type3 fonts, which is a somewhat special font type and one where our current text-selection behaviour is probably the least good.
2020-03-22 22:09:08 +09:00
{ "id": "issue11713",
"file": "pdfs/issue11713.pdf",
"md5": "bafe5801234feeb95969da106f2ce6d8",
"rounds": 1,
"type": "text"
},
Add a `recoveryMode` that suppresses errors from the `Parser`, and utilize it when searching for the main trailer in `XRef_indexObjects` (bug 1250079) Instead of having `Parser_getObj` fail unconditionally for the referenced PDF file, this patch attempts to let searching for the main trailer continue even if there are errors. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1250079.
2016-02-25 01:56:28 +09:00
{ "id": "bug1250079",
"file": "pdfs/bug1250079.pdf",
"md5": "a1dd21a70ae7097d96273e85a80b26ef",
"rounds": 1,
"link": false,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"type": "eq"
Add a `recoveryMode` that suppresses errors from the `Parser`, and utilize it when searching for the main trailer in `XRef_indexObjects` (bug 1250079) Instead of having `Parser_getObj` fail unconditionally for the referenced PDF file, this patch attempts to let searching for the main trailer continue even if there are errors. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1250079.
2016-02-25 01:56:28 +09:00
},
Ignore reserved commands when parsing operands in `CFFParser_parseDict`, instead of just rejecting the entire font (bug 1308536) According to the CFF specification, see http://partners.adobe.com/public/developer/en/font/5176.CFF.pdf#page=11, certain commands are currently reserved. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1308536.
2016-10-08 03:51:02 +09:00
{ "id": "bug1308536",
"file": "pdfs/bug1308536.pdf",
"md5": "cc2258981e33ad8d96acbf87318716d5",
"rounds": 1,
"link": false,
"type": "eq"
},
Prevent an infinite loop in `XRef.readXRef` by keeping track of already parsed tables (bug 1393476) With this patch, not only is the infinite loop prevented, but we're also able to actually render the file (which e.g. Adobe Reader isn't able to). Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1393476.
2017-08-25 02:14:33 +09:00
{ "id": "bug1393476",
"file": "pdfs/bug1393476.pdf",
"md5": "163ee8727c77f27ee651eec777bb20a9",
"rounds": 1,
"link": true,
"type": "eq"
},
Gracefully handle annotation parsing errors in `Page.getOperatorList` (issue 11871) This should ensure that a page will always render successfully, even if there's errors during the Annotation fetching/parsing. Additionally the `OperatorList.addOpList` method is also adjusted to ignore invalid data, to make it slightly more robust.
2020-05-04 23:51:08 +09:00
{ "id": "issue11871",
"file": "pdfs/issue11871.pdf",
"md5": "9c533eacd0ca892df4191360848668a2",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq"
},
Replace empty CharStrings with '.notdef' in `Type1Font_wrap` to prevent OTS from rejecting the font (bug 1252420) Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1252420.
2016-09-17 21:36:42 +09:00
{ "id": "bug1252420",
"file": "pdfs/bug1252420.pdf",
"md5": "f21c911b9b655972b06ef782a1fa6a17",
"rounds": 1,
"link": false,
"type": "eq"
},
Use font's default width even when 0. Bug 1392647 has a PDF where the default width of the font is 0. It draws some charcodes that don't have glyphs, but we were wrongly using the 1000 default width for these charcodes causing some text to be overlapping.
2017-09-21 03:37:56 +09:00
{ "id": "bug1392647",
"file": "pdfs/bug1392647.pdf",
"md5": "9770ea476630ca7d560b7c39430f8850",
"rounds": 1,
"link": false,
"type": "eq"
},
Handle references for color space names that are defined in a dictionary
2011-09-23 05:17:28 +09:00
{ "id": "hudsonsurvey",
"file": "pdfs/hudsonsurvey.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "bf0e6576a7b6c2fe7485bce1b78e006f",
Handle references for color space names that are defined in a dictionary
2011-09-23 05:17:28 +09:00
"link": true,
"rounds": 1,
"type": "load"
Implement "skipPages" feature for reftests
2011-09-24 23:44:50 +09:00
},
Adds support for all the basic graphic state operators
2011-09-24 06:37:44 +09:00
{ "id": "extgstate",
"file": "pdfs/extgstate.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "001bb4ec04463a01d93aad748361f049",
Adds support for all the basic graphic state operators
2011-09-24 06:37:44 +09:00
"link": false,
"rounds": 1,
Change rotation and extgstate to eq tests.
2011-10-14 06:57:56 +09:00
"type": "eq"
Merge branch 'master' of https://github.com/andreasgal/pdf.js.git into invalidpdf-1 Conflicts: test/test_manifest.json
2011-09-24 23:57:59 +09:00
},
Skip bogus `d1` operators in Type3-glyphs (issue 14953) In the `src/display/canvas.js` code the `d1` operator will be used to set the clipping region, and it obviously cannot be empty since that prevents the Type3-glyph from rendering. Also, the patch removes an outdated comment; refer to PR 12718.
2022-05-24 19:12:53 +09:00
{ "id": "issue14953",
"file": "pdfs/issue14953.pdf",
"md5": "dd7d6cb92e58d75a0eb8c0476a3bc64a",
"rounds": 1,
"type": "eq"
},
Lookup image-data correctly in `paintImageMaskXObjectGroup` (issue 14990) *This fixes a regression from PR 14754.* We didn't lookup the image-data correctly, with the result that we tried to render some ImageMasks using a string rather than the intended TypedArray. To make matters worse, this code-path was apparently not *properly* covered by existing test-cases.
2022-06-05 19:12:05 +09:00
{ "id": "issue14990",
"file": "pdfs/issue14990.pdf",
"md5": "0fb397e1506acc4ab8e68c18212a1362",
"link": true,
"rounds": 1,
"firstPage": 25,
"lastPage": 25,
"type": "eq"
},
Fix errors in `setGState` in `PartialEvaluator_getTextContent` that prevents text-selection from working properly Currently `setGState` is completely broken, and looking through the history of that code, it seems to me that this may never have worked correctly. This patch fixes the text-selection in `extgstate.pdf` in the test-suite, which is also added as a `text` test.
2016-06-01 06:40:19 +09:00
{ "id": "extgstate-text",
"file": "pdfs/extgstate.pdf",
"md5": "001bb4ec04463a01d93aad748361f049",
"link": false,
"rounds": 1,
"type": "text"
},
Fixing PDF bad structure and 'fi' ligature
2011-10-08 12:24:26 +09:00
{ "id": "usmanm-bad",
"file": "pdfs/usmanm-bad.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "38afb822433aaf07fc8f54807cd4f61a",
Fixing PDF bad structure and 'fi' ligature
2011-10-08 12:24:26 +09:00
"link": true,
"rounds": 1,
"type": "eq"
},
Convert `uniXXXX` glyph names to proper ones when building the `charCodeToGlyphId` map for TrueType fonts (bug 1132849, issue 6893, issue 6894) This patch adds a `getUnicodeForGlyph` helper function, which is used to recover Unicode values for non-standard glyph names. Some PDF generators, e.g. Scribus PDF, use improper `uniXXXX` glyph names which breaks the glyph mapping. We can avoid this by converting them to "standard" glyph names instead. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1132849. Fixes 6893. Fixes 6894.
2016-03-08 04:56:15 +09:00
{ "id": "bug1132849",
"file": "pdfs/bug1132849.pdf",
"md5": "aedfbead1f8feb35cf2e38b279133b47",
"rounds": 1,
"link": false,
"type": "eq"
},
{ "id": "issue6894",
"file": "pdfs/issue6894.pdf",
"md5": "bb84f2025c11f23cf436170049f81215",
"rounds": 1,
"link": false,
"type": "eq"
},
Implements shading types 4-7
2014-01-27 22:17:14 +09:00
{ "id": "personwithdog",
"file": "pdfs/personwithdog.pdf",
"md5": "cd68fb2ce00dab97801b3e51495b99e3",
"rounds": 1,
"type": "eq"
},
Ensure that we don't use the same typed array for both `coords` and `colors` in Mesh `figures` (issue 6287) This regressed in https://github.com/mozilla/pdf.js/commit/1e8d70af9819d9b285e15fea8d50456c8275137e.
2015-07-31 20:59:02 +09:00
{ "id": "issue2948",
"file": "pdfs/issue2948.pdf",
"md5": "26210bed6a57d5466042aff22f0249f0",
"link": false,
"rounds": 1,
"type": "eq"
},
Prevent getOperatorList from failing to correctly parse OPS.paintXObject for TilingPatterns that are missing some /Resources entries (issue 6541) Fixes 6541.
2015-10-21 03:22:06 +09:00
{ "id": "issue6541",
"file": "pdfs/issue6541.pdf",
"md5": "81bc5b146404207ea40f2c55301b2bb6",
"link": false,
"rounds": 1,
"type": "eq"
},
Correctly access `colorSpace.numComps` in `MeshStreamReader` (issue 6287) This regressed in https://github.com/mozilla/pdf.js/commit/f750e35224d344f068542411bcb4f750b2d4dcdb.
2015-08-01 00:55:51 +09:00
{ "id": "issue6231_1",
"file": "pdfs/issue6231_1.pdf",
"md5": "eb13a9366a5142833a858472c68b4749",
"link": false,
"rounds": 1,
"type": "eq"
},
Changes to regression tests for progressive loading
2013-04-13 03:37:49 +09:00
{ "id": "usmanm-bad-auto-fetch",
"file": "pdfs/usmanm-bad.pdf",
"md5": "38afb822433aaf07fc8f54807cd4f61a",
"link": true,
"rounds": 1,
"type": "eq",
"enableAutoFetch": true
},
Recovering from RGBT-command (ref #577)
2011-10-02 09:01:58 +09:00
{ "id": "vesta-bad",
"file": "pdfs/vesta.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "0afebc109b7c17b95619ea3fab5eafe6",
Recovering from RGBT-command (ref #577)
2011-10-02 09:01:58 +09:00
"link": true,
"rounds": 1,
"type": "load"
},
Ignore the /Mask entry in images unless its /ImageMask entry is explicitly set to `true` (issue 6621) Fixes 6621.
2015-11-13 05:41:16 +09:00
{ "id": "issue6621",
"file": "pdfs/issue6621.pdf",
"md5": "8079ce514fb2cdded4251eade6380ba9",
"link": false,
"rounds": 1,
"type": "eq"
},
Extend `getGlyphMapForStandardFonts` with additional entries (issue 15977)
2023-01-30 20:04:10 +09:00
{ "id": "issue15977",
"file": "pdfs/issue15977_reduced.pdf",
"md5": "cd06accb3da81597ad11acffeb0b68fc",
"rounds": 1,
"type": "eq"
},
Use `adjustWidths` for TrueType fonts if we handle them as OpenType (issue 5027, issue 5084, issue 6556, bug 1204903) In `Font_checkAndRepair` we can decide that a font isn't TrueType, and instead parse it as CFF. In that case it's quite possible that the `fontMatrix` will be changed, and without calling `adjustWidths` we're failing to update the glyph widths correctly. Fixes 5027. Fixes 5084. Fixes 6556. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1204903.
2015-12-08 06:30:09 +09:00
{ "id": "issue5084",
"file": "pdfs/issue5084.pdf",
"md5": "a42a076ba90e20e3aae9af869eb4de45",
"link": false,
"rounds": 1,
"type": "eq"
},
Add bad PDF with lots of extra bytes at the end
2011-12-09 10:17:24 +09:00
{ "id": "scan-bad",
"file": "pdfs/scan-bad.pdf",
"md5": "4cf988f01ab83f61aca57f406dfd6584",
"rounds": 1,
"type": "load"
},
Add a linked `load` test for issue 6549
2016-02-13 02:05:19 +09:00
{ "id": "issue6549",
"file": "pdfs/issue6549.pdf",
"md5": "699aeea73a6f45375022ffc6cc80f12a",
"link": true,
"rounds": 1,
"firstPage": 2,
"lastPage": 3,
"type": "load"
},
Implement "skipPages" feature for reftests
2011-09-24 23:44:50 +09:00
{ "id": "ibwa-bad",
"file": "pdfs/ibwa-bad.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "6ca059d32b74ac2688ae06f727fee755",
Implement "skipPages" feature for reftests
2011-09-24 23:44:50 +09:00
"link": true,
"rounds": 1,
"type": "load"
Initial CID0 font encodings
2011-09-29 09:54:40 +09:00
},
Replace test pdf tcpdf 33 by custom generated pdf.
2012-04-18 02:39:17 +09:00
{ "id": "mixedfonts",
"file": "pdfs/mixedfonts.pdf",
"md5": "a582b83fa1b3a25a6f13803a367c71ec",
"link": false,
Initial CID0 font encodings
2011-09-29 09:54:40 +09:00
"rounds": 1,
"type": "eq"
fix merge conflicts
2011-10-05 00:52:15 +09:00
},
Add standard font name test (also for #621)
2011-10-12 09:45:55 +09:00
{ "id": "pal-o47",
"file": "pdfs/pal-o47.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "81ae15e539e89f0f0b41169d923b611b",
Add standard font name test (also for #621)
2011-10-12 09:45:55 +09:00
"link": true,
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 4800
2014-07-31 05:15:06 +09:00
{ "id": "issue4800",
"file": "pdfs/issue4800.pdf",
"md5": "80d285dfdb8e8e0dd66a2353f0c78b05",
"link": false,
"rounds": 1,
"type": "eq",
"about": "TrueType font with (0, 1) cmap."
},
Fix another seac regression (issue 4801)
2014-06-24 03:55:51 +09:00
{ "id": "issue4801",
"file": "pdfs/issue4801.pdf",
"md5": "7f32764717447a8b5c8eac08c9ab8380",
"link": false,
"rounds": 1,
"type": "eq"
},
Extend `getNonStdFontMap` for non-embedded Impact fonts (bug 1365930) According to https://en.wikipedia.org/wiki/Impact_(typeface) this font should be available on all current versions of Windows, and with the recently added font-substitution we should actually be able to render it correctly (at least on Windows).
2023-05-20 01:34:21 +09:00
{ "id": "bug1365930",
"file": "pdfs/bug1365930.pdf",
"md5": "0db06efce060d82da16a79e8bd762a1c",
"rounds": 1,
"type": "eq"
},
Always choose a (3, 1) cmap table for TrueType fonts that have an encoding specified, regardless of the Symbolic font flag (bug 1337429) This patch basically reverts one aspect of TrueType (3, 1) cmap parsing to the state prior to PR 4259. After that PR, a number of regressions occurred in this particular code-path, which necessitated a number of follow-ups such as PRs 5703, 5743, and 6425. The empirical data suggests, at least to me, that we should always prefer a (3, 1) cmap for TrueType fonts when they have an encoding, regardless of the Symbolic font flag. Obviously this patch passes all unit/font/reference tests locally, and I made sure that all the PRs mentioned above landed with test-cases included. However, in my opinion, there's still a very real possibility that this patch could potentially cause new regressions. Given that the PDF file in bug 1337429 has been broken for almost *three* years before anyone noticed, and considering that the code-path in question has been the source of numerous regressions, I do *not* intend to request uplift of this patch to previous Firefox versions (assuming that it's even accepted). Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1337429.
2017-02-15 22:18:42 +09:00
{ "id": "bug1337429",
"file": "pdfs/bug1337429.pdf",
"md5": "4e6e4dfdab884e9465bdce657b590028",
"link": false,
"rounds": 1,
"type": "eq"
},
Prevent textLayer errors in documents with unbalanced beginMarkedContent/endMarkedContent operators (issue 15629)
2022-10-27 00:59:48 +09:00
{ "id": "issue15629",
"file": "pdfs/issue15629.pdf",
"md5": "689771b7f5c86c783c56aa8dedab0057",
"rounds": 1,
"type": "text"
},
Build paths for glyph accents when drawing text as curves
2014-05-04 00:28:30 +09:00
{ "id": "glyph_accent",
"file": "pdfs/glyph_accent.pdf",
"md5": "1526e4edaa3ec439ebf156d0a0b385aa",
"link": false,
"rounds": 1,
"type": "eq",
"about": "Glyph accent drawn as curves."
},
Don't map glyphs to unicode non breaking space.
2014-10-03 02:58:56 +09:00
{ "id": "issue5138",
"file": "pdfs/issue5138.pdf",
"md5": "9931686d7dee0df62640fbf58bed3323",
"link": false,
"rounds": 1,
"type": "eq",
"about": "Glyph that gets mapped to unicode non-breaking-space."
},
Fix canvas state getting out of sync from smasks. (bug 1755507) Soft masks can be enabled/disabled at anytime and at different points in the save/restore stack. This can lead to the amount of save/restores becoming unbalanced across the two canvases. Instead of save/restoring on the temporary canvas change it so we only track state on the main (suspended canvas). I was also getting an out balance stack from patterns, so I've also fixed that and added a warning that will at least show up on chrome. It would be nice to add this so Firefox at some point too. Fixes #11328, #14297 and bug 1755507
2022-02-16 09:44:50 +09:00
{ "id": "issue14297",
"file": "pdfs/issue14297.pdf",
"md5": "46eb3d4d4bc47c8009fc4c699d213a18",
"rounds": 1,
"type": "eq"
},
#502 Adding basic Type3 font support.
2011-10-04 08:36:01 +09:00
{ "id": "simpletype3font",
"file": "pdfs/simpletype3font.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "b374c7543920840c61999e9e86939f99",
#502 Adding basic Type3 font support.
2011-10-04 08:36:01 +09:00
"link": false,
"rounds": 1,
Address pull request feedback.
2011-10-05 01:06:51 +09:00
"type": "eq"
Add the alpha trans test pdf.
2011-10-29 06:11:14 +09:00
},
Fix how patterns are applied to image mask objects. Note, this only really fixes Radial/Axial shading patterns with masks. I'm guessing tiling patterns and mesh patterns would also be broken if applied like the test pdf. Hopefully I'll have some time to make test cases for the other shadings. Fixes #13372
2021-06-15 13:09:45 +09:00
{ "id": "issue13372",
"file": "pdfs/issue13372.pdf",
"md5": "0bc5329623fd554174c5e7653f904e28",
"rounds": 1,
"type": "eq"
},
Support corrupt documents with *empty* `Name`-entries (issue 13610) Apparently some really bad PDF software can create documents with *empty* `Name`-entries, which we thus need to somehow deal with. While I don't know if this patch is necessarily the best solution, it should at least ensure that the *empty* `Name`-instance cannot accidentally match a proper `Name`-instance (and it doesn't require changes to a lot of existing code).[1] --- [1] I briefly considered using a `Symbol` rather than an Object, but quickly decided against that since the former one [is not clonable](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#supported_types) and `Name`-instances may be sent to the API.
2021-06-22 22:44:52 +09:00
{ "id": "issue13610",
"file": "pdfs/issue13610.pdf",
"md5": "5b894c0b1b2279a245c23abd76648ca9",
"link": true,
"rounds": 1,
"type": "eq"
},
Check that TrueType (3, 0) cmap tables, for symbolic fonts, are sorted correctly (issue 13626) According to a comment in `readCmapTable`, we're assuming that the cmap tables (when more than one exist) are sorted in ascending order. If that's not the case, keep checking the following cmap tables in order to fix the referenced issue.
2021-06-25 22:51:08 +09:00
{ "id": "issue13626",
"file": "pdfs/issue13626.pdf",
"md5": "68bc1c2459d56e8c33f5a12a88c9df7d",
"link": true,
"rounds": 1,
"type": "eq"
},
Add test coverage for simpletype3font test PDF
2012-09-15 03:37:00 +09:00
{ "id": "simpletype3font-text",
"file": "pdfs/simpletype3font.pdf",
"md5": "b374c7543920840c61999e9e86939f99",
"link": false,
"rounds": 1,
"type": "text"
},
Support (rare) Type3 fonts which contains image resources (issue 10717) The Type3 font type is not commonly used in PDF documents, as can be seen from telemetry data such as: https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2019-04-09&include_spill=0&keys=__none__!__none__!__none__&max_channel_version=nightly%252F68&measure=PDF_VIEWER_FONT_TYPES&min_channel_version=nightly%252F57&processType=*&product=Firefox&sanitize=1&sort_by_value=0&sort_keys=submissions&start_date=2019-03-18&table=0&trim=1&use_submission_date=0 (see also https://github.com/mozilla/pdf.js/wiki/Enumeration-Assignments-for-the-Telemetry-Histograms#pdf_viewer_font_types). Type3 fonts containing image resources are *very* rare in practice, usually they only contain path rendering operators, but as the issue shows they unfortunately do exist. Currently these Type3-related image resources are not handled in any special way, and given that fonts are document rather than page specific rendering breaks since the image resources are thus not available to the *entire* document. Fortunately fixing this isn't too difficult, but it does require adding a couple of Type3-specific code-paths to the `PartialEvaluator`. In order to keep the implementation simple, particularily on the main-thread, these Type3 image resources are completely decoded on the worker-thread to avoid adding too many special cases. This should not cause any issues, only marginally less efficient code, but given how rare this kind of Type3 font is adding premature optimizations didn't seem at all warranted at this point.
2019-04-11 19:26:15 +09:00
{ "id": "issue10717",
"file": "pdfs/issue10717.pdf",
"md5": "6d2ed03db798cc6beb3c7bdf103f5c1a",
"link": true,
"rounds": 1,
"firstPage": 1,
"lastPage": 2,
"type": "eq",
"about": "Type3 fonts with image resources; both pages need to be tested, otherwise the bug won't manifest."
},
Support (rare) Type3 fonts with Pattern resources (issue 16127) This simply extends the approach in PR 10727 to also cover Patterns, which shouldn't be a common occurrence in Type3 fonts (since this is the first issue we've seen).
2023-03-08 16:45:42 +09:00
{ "id": "issue16127",
"file": "pdfs/issue16127.pdf",
"md5": "42714567a818876f51ef960df21600f5",
"link": true,
"rounds": 1,
"firstPage": 1,
"lastPage": 2,
"type": "eq",
"about": "Type3 fonts with pattern resources; both pages need to be tested, otherwise the bug won't manifest."
},
JS -- Add tests for print/save actions * change PDFDocument::hasJSActions to return true when there are JS actions in catalog.
2020-12-24 02:57:44 +09:00
{ "id": "doc_actions",
"file": "pdfs/doc_actions.pdf",
"md5": "ceae4eb405a0b40394f4d63d7525a870",
"rounds": 1,
"type": "eq"
},
Fix popup for highlights without popup (follow-up of #12505) * remove 1st param of _createPopup (almost useless for a method) * prepend popup div to avoid to have them on top of some highlights (and so "disable" partially mouse events) * add a ref test for issue #12504
2020-11-06 01:49:32 +09:00
{ "id": "issue12504",
"file": "pdfs/issue12504.pdf",
"md5": "04fcc87f3e7e9e925e3ef83cf0bf49f4",
"rounds": 1,
"type": "eq",
"annotations": true
},
Add eq test for close path rendering bug See: 56b9a3543dfd365fb065a85ac056d29064c72797
2011-10-28 22:38:55 +09:00
{ "id": "close-path-bug",
"file": "pdfs/close-path-bug.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "48dd17ef58393857d2d038d33699cac5",
Add eq test for close path rendering bug See: 56b9a3543dfd365fb065a85ac056d29064c72797
2011-10-28 22:38:55 +09:00
"rounds": 1,
"type": "eq"
Merge upstream
2011-11-01 00:51:45 +09:00
},
Add the alpha trans test pdf.
2011-10-29 06:11:14 +09:00
{ "id": "alphatrans",
"file": "pdfs/alphatrans.pdf",
Hash files to make sure they haven't changed.
2011-11-05 01:14:52 +09:00
"md5": "5ca2d3da0c5f20b3a5a14e895ad24b65",
Add the alpha trans test pdf.
2011-10-29 06:11:14 +09:00
"link": false,
"rounds": 1,
"type": "eq"
Add the cmyk jpeg test file.
2011-11-10 02:39:55 +09:00
},
Use the `cidToGidMap`, if it exists, when building the glyph mapping for non-embedded composite fonts (issue 12418)
2020-09-28 21:39:48 +09:00
{ "id": "issue12418",
"file": "pdfs/issue12418_reduced.pdf",
"md5": "596b70f00a5f88ff58f4f4d06fcf75f1",
"rounds": 1,
"type": "eq"
},
Correct PostScript trigonometric operators PDF 32000-1:2008 7.10.5.1 "Type 4 (PostScript Calculator) Functions" defers to the PostScript Language Reference for the description of these functions. The PostScript Language Reference, third edition chapter 8 "Operators" defines the `angle` type as a "number of degrees". Section 8.1 defines "angle `sin` real", "angle `cos` real", and "num den `atan` angle". The documentation for `atan` further states that it will return an angle in degrees between 0 and 360. Handle these operators correctly in `PostScriptEvaluator.execute`. Convert the inputs to `sin` and `cos` from degrees to radians for use with `Math.sin` and `Math.cos`. Correctly pop two values from the stack for `atan`, use `Math.atan2`, and convert from radians to (positive) degrees.
2023-02-28 02:34:12 +09:00
{ "id": "colorspace_cos",
"file": "pdfs/colorspace_cos.pdf",
"md5": "d3703784c2558f33e03b91dccb745b6c",
"rounds": 1,
"type": "eq"
},
Ensure that `Lexer_getName` does not fail if a `Name` contains in invalid usage of the NUMBER SIGN (#) (issue 6692) *This is a regression from PR 3424.* The PDF file in the referenced issue is using `Type3` fonts. In one of those, the `/CharProcs` dictionary contains an entry with the name `/#`. Before the changes to `Lexer_getName` in PR 3424, we were allowing certain invalid `Name` patterns containing the NUMBER SIGN (#). It's unfortunate that this has been broken for close to two and a half years before the bug surfaced, but it should at least indicate that this is not a widespread issue. Fixes 6692.
2015-11-26 21:27:12 +09:00
{ "id": "issue6692",
"file": "pdfs/issue6692.pdf",
"md5": "ba078e0ddd59cda4b6c51ea10599f49a",
"link": true,
"rounds": 1,
"firstPage": 11,
"lastPage": 11,
"type": "eq"
},
Adding multi dimensional interpolation and test file.
2011-11-12 07:44:47 +09:00
{ "id": "devicen",
"file": "pdfs/devicen.pdf",
Update md5.
2011-11-23 02:06:53 +09:00
"md5": "aac6a91725435d1376c6ff492dc5cb75",
Adding multi dimensional interpolation and test file.
2011-11-12 07:44:47 +09:00
"link": false,
"rounds": 1,
"type": "eq"
Merge upstream and change test pdf file.
2011-11-23 03:39:26 +09:00
},
Use the Alternate entry, if it exists, in ICCBased Colour Space dictionaries (issue 5836, issue 5939, issue 6055) Fixes 5836. Fixes 5939. Fixes 6055.
2015-06-14 04:05:13 +09:00
{ "id": "issue5939",
"file": "pdfs/issue5939.pdf",
"md5": "43c61e06ad407c158763f0860c99bb04",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Add the cmyk jpeg test file.
2011-11-10 02:39:55 +09:00
{ "id": "cmykjpeg",
"file": "pdfs/cmykjpeg.pdf",
Merge upstream and change test pdf file.
2011-11-23 03:39:26 +09:00
"md5": "85d162b48ce98503a382d96f574f70a2",
Add the cmyk jpeg test file.
2011-11-10 02:39:55 +09:00
"link": false,
"rounds": 1,
"type": "eq"
Add test case.
2011-11-30 08:47:53 +09:00
},
For CIDFontType2 use CID as glyph ID when missing CID to GID map.
2016-03-02 10:05:33 +09:00
{ "id": "issue4402_reduced",
"file": "pdfs/issue4402_reduced.pdf",
"md5": "6cc7e61a581889eec3ed7402d87161c4",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 7403
2016-06-13 21:22:15 +09:00
{ "id": "issue7403",
"file": "pdfs/issue7403.pdf",
"md5": "0f7bb6b3c58e33bbf76ce5161cd665c3",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 7406 The PDF file contains an image that we're allowed to use, since it's just the PDF.js logo. The logo image was simply inverted (so that it requires a /Decode entry in the image dictionary that triggers the use of `jpg.js` instead of the browser), converted to JPEG, and finally edited by hand to change the order of the DQT/SOF{n} markers.
2016-07-23 20:04:27 +09:00
{ "id": "issue7406",
"file": "pdfs/issue7406.pdf",
"md5": "7a3d322d7c595a36b4470cfb6a54a2b7",
"link": false,
"rounds": 1,
"type": "eq"
},
Allow over-writing entries, in `XRef.indexObjects`, only when the generation number matches (issues 11230, 11139, 9552, 9129, 7303) This patch is making me somewhat worried about future regressions, since it's certainly easy to imagine this completely breaking certain kinds of corrupt/edited PDF documents while fixing others.[1] Obviously it passes all existing reference tests (and even improves one), however compared to many other patches there's no telling how much it could break. The only reason that I'm even submitting this patch, is because of the number of open issues that it would address. Generally speaking though, the best course of action would probably be if `XRef.indexObjects` was re-written to be much more robust (since it currently feels somewhat hand-wavy in parts). E.g. by actually checking/validating more of the objects before committing to them. --- [1] Especially given that it's reverting part of PR 5910, however in the case of issue 5909 it seems that other (more recent) changes have actually made that PR redundant.
2019-10-12 03:39:02 +09:00
{ "id": "issue7303",
"file": "pdfs/issue7303.pdf",
"md5": "3a5a4ab6755d6c3b0c490996b83d69d2",
"link": true,
"rounds": 1,
"lastPage": 2,
"type": "eq"
},
Check that the first page can be successfully loaded, to try and ascertain the validity of the XRef table (issue 7496, issue 10326) For PDF documents with sufficiently broken XRef tables, it's usually quite obvious when you need to fallback to indexing the entire file. However, for certain kinds of corrupted PDF documents the XRef table will, for all intents and purposes, appear to be valid. It's not until you actually try to fetch various objects that things will start to break, which is the case in the referenced issues[1]. Since there's generally a real effort being in made PDF.js to load even corrupt PDF documents, this patch contains a suggested approach to attempt to do a bit more validation of the XRef table during the initial document loading phase. Here the choice is made to attempt to load the *first* page, as a basic sanity check of the validity of the XRef table. Please note that attempting to load a more-or-less arbitrarily chosen object without any context of what it's supposed to be isn't a very useful, which is why this particular choice was made. Obviously, just because the first page can be loaded successfully that doesn't guarantee that the *entire* XRef table is valid, however if even the first page fails to load you can be reasonably sure that the document is *not* valid[2]. Even though this patch won't cause any significant increase in the amount of parsing required during initial loading of the document[3], it will require loading of more data upfront which thus delays the initial `getDocument` call. Whether or not this is a problem depends very much on what you actually measure, please consider the following examples: ```javascript console.time('first'); getDocument(...).promise.then((pdfDocument) => { console.timeEnd('first'); }); console.time('second'); getDocument(...).promise.then((pdfDocument) => { pdfDocument.getPage(1).then((pdfPage) => { // Note: the API uses `pageNumber >= 1`, the Worker uses `pageIndex >= 0`. console.timeEnd('second'); }); }); ``` The first case is pretty much guaranteed to show a small regression, however the second case won't be affected at all since the Worker caches the result of `getPage` calls. Again, please remember that the second case is what matters for the standard PDF.js use-case which is why I'm hoping that this patch is deemed acceptable. --- [1] In issue 7496, the problem is that the document is edited without the XRef table being correctly updated. In issue 10326, the generator was sorting the XRef table according to the offsets rather than the objects. [2] The idea of checking the first page in particular came from the "standard" use-case for the PDF.js library, i.e. the default viewer, where a failure to load the first page basically means that nothing will work; note how `{BaseViewer, PDFThumbnailViewer}.setDocument` depends completely on being able to fetch the *first* page. [3] The only extra parsing is caused by, potentially, having to traverse *part* of the `Pages` tree to find the first page.
2018-12-05 05:51:27 +09:00
{ "id": "issue7496",
"file": "pdfs/issue7496.pdf",
"md5": "b422981ae781166e75c0fb4c3634ed96",
"link": true,
"rounds": 1,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"lastPage": 2,
Allow over-writing entries, in `XRef.indexObjects`, only when the generation number matches (issues 11230, 11139, 9552, 9129, 7303) This patch is making me somewhat worried about future regressions, since it's certainly easy to imagine this completely breaking certain kinds of corrupt/edited PDF documents while fixing others.[1] Obviously it passes all existing reference tests (and even improves one), however compared to many other patches there's no telling how much it could break. The only reason that I'm even submitting this patch, is because of the number of open issues that it would address. Generally speaking though, the best course of action would probably be if `XRef.indexObjects` was re-written to be much more robust (since it currently feels somewhat hand-wavy in parts). E.g. by actually checking/validating more of the objects before committing to them. --- [1] Especially given that it's reverting part of PR 5910, however in the case of issue 5909 it seems that other (more recent) changes have actually made that PR redundant.
2019-10-12 03:39:02 +09:00
"type": "eq",
"annotations": true
},
{ "id": "issue9129",
"file": "pdfs/issue9129.pdf",
"md5": "939ffc8d6d29b1d74e9d0f98b227b97f",
"link": true,
"rounds": 1,
"lastPage": 1,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"type": "eq"
Check that the first page can be successfully loaded, to try and ascertain the validity of the XRef table (issue 7496, issue 10326) For PDF documents with sufficiently broken XRef tables, it's usually quite obvious when you need to fallback to indexing the entire file. However, for certain kinds of corrupted PDF documents the XRef table will, for all intents and purposes, appear to be valid. It's not until you actually try to fetch various objects that things will start to break, which is the case in the referenced issues[1]. Since there's generally a real effort being in made PDF.js to load even corrupt PDF documents, this patch contains a suggested approach to attempt to do a bit more validation of the XRef table during the initial document loading phase. Here the choice is made to attempt to load the *first* page, as a basic sanity check of the validity of the XRef table. Please note that attempting to load a more-or-less arbitrarily chosen object without any context of what it's supposed to be isn't a very useful, which is why this particular choice was made. Obviously, just because the first page can be loaded successfully that doesn't guarantee that the *entire* XRef table is valid, however if even the first page fails to load you can be reasonably sure that the document is *not* valid[2]. Even though this patch won't cause any significant increase in the amount of parsing required during initial loading of the document[3], it will require loading of more data upfront which thus delays the initial `getDocument` call. Whether or not this is a problem depends very much on what you actually measure, please consider the following examples: ```javascript console.time('first'); getDocument(...).promise.then((pdfDocument) => { console.timeEnd('first'); }); console.time('second'); getDocument(...).promise.then((pdfDocument) => { pdfDocument.getPage(1).then((pdfPage) => { // Note: the API uses `pageNumber >= 1`, the Worker uses `pageIndex >= 0`. console.timeEnd('second'); }); }); ``` The first case is pretty much guaranteed to show a small regression, however the second case won't be affected at all since the Worker caches the result of `getPage` calls. Again, please remember that the second case is what matters for the standard PDF.js use-case which is why I'm hoping that this patch is deemed acceptable. --- [1] In issue 7496, the problem is that the document is edited without the XRef table being correctly updated. In issue 10326, the generator was sorting the XRef table according to the offsets rather than the objects. [2] The idea of checking the first page in particular came from the "standard" use-case for the PDF.js library, i.e. the default viewer, where a failure to load the first page basically means that nothing will work; note how `{BaseViewer, PDFThumbnailViewer}.setDocument` depends completely on being able to fetch the *first* page. [3] The only extra parsing is caused by, potentially, having to traverse *part* of the `Pages` tree to find the first page.
2018-12-05 05:51:27 +09:00
},
Allow over-writing entries, in `XRef.indexObjects`, only when the generation number matches (issues 11230, 11139, 9552, 9129, 7303) This patch is making me somewhat worried about future regressions, since it's certainly easy to imagine this completely breaking certain kinds of corrupt/edited PDF documents while fixing others.[1] Obviously it passes all existing reference tests (and even improves one), however compared to many other patches there's no telling how much it could break. The only reason that I'm even submitting this patch, is because of the number of open issues that it would address. Generally speaking though, the best course of action would probably be if `XRef.indexObjects` was re-written to be much more robust (since it currently feels somewhat hand-wavy in parts). E.g. by actually checking/validating more of the objects before committing to them. --- [1] Especially given that it's reverting part of PR 5910, however in the case of issue 5909 it seems that other (more recent) changes have actually made that PR redundant.
2019-10-12 03:39:02 +09:00
{ "id": "issue9552",
"file": "pdfs/issue9552.pdf",
"md5": "7f80fd5b426926f88fd2a9fdc02cd3bd",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq",
"annotations": true
},
Check that the first page can be successfully loaded, to try and ascertain the validity of the XRef table (issue 7496, issue 10326) For PDF documents with sufficiently broken XRef tables, it's usually quite obvious when you need to fallback to indexing the entire file. However, for certain kinds of corrupted PDF documents the XRef table will, for all intents and purposes, appear to be valid. It's not until you actually try to fetch various objects that things will start to break, which is the case in the referenced issues[1]. Since there's generally a real effort being in made PDF.js to load even corrupt PDF documents, this patch contains a suggested approach to attempt to do a bit more validation of the XRef table during the initial document loading phase. Here the choice is made to attempt to load the *first* page, as a basic sanity check of the validity of the XRef table. Please note that attempting to load a more-or-less arbitrarily chosen object without any context of what it's supposed to be isn't a very useful, which is why this particular choice was made. Obviously, just because the first page can be loaded successfully that doesn't guarantee that the *entire* XRef table is valid, however if even the first page fails to load you can be reasonably sure that the document is *not* valid[2]. Even though this patch won't cause any significant increase in the amount of parsing required during initial loading of the document[3], it will require loading of more data upfront which thus delays the initial `getDocument` call. Whether or not this is a problem depends very much on what you actually measure, please consider the following examples: ```javascript console.time('first'); getDocument(...).promise.then((pdfDocument) => { console.timeEnd('first'); }); console.time('second'); getDocument(...).promise.then((pdfDocument) => { pdfDocument.getPage(1).then((pdfPage) => { // Note: the API uses `pageNumber >= 1`, the Worker uses `pageIndex >= 0`. console.timeEnd('second'); }); }); ``` The first case is pretty much guaranteed to show a small regression, however the second case won't be affected at all since the Worker caches the result of `getPage` calls. Again, please remember that the second case is what matters for the standard PDF.js use-case which is why I'm hoping that this patch is deemed acceptable. --- [1] In issue 7496, the problem is that the document is edited without the XRef table being correctly updated. In issue 10326, the generator was sorting the XRef table according to the offsets rather than the objects. [2] The idea of checking the first page in particular came from the "standard" use-case for the PDF.js library, i.e. the default viewer, where a failure to load the first page basically means that nothing will work; note how `{BaseViewer, PDFThumbnailViewer}.setDocument` depends completely on being able to fetch the *first* page. [3] The only extra parsing is caused by, potentially, having to traverse *part* of the `Pages` tree to find the first page.
2018-12-05 05:51:27 +09:00
{ "id": "issue10326",
"file": "pdfs/issue10326.pdf",
"md5": "015c13b09ef735ea1204f38992c60487",
"link": true,
"rounds": 1,
"lastPage": 1,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"type": "eq"
Check that the first page can be successfully loaded, to try and ascertain the validity of the XRef table (issue 7496, issue 10326) For PDF documents with sufficiently broken XRef tables, it's usually quite obvious when you need to fallback to indexing the entire file. However, for certain kinds of corrupted PDF documents the XRef table will, for all intents and purposes, appear to be valid. It's not until you actually try to fetch various objects that things will start to break, which is the case in the referenced issues[1]. Since there's generally a real effort being in made PDF.js to load even corrupt PDF documents, this patch contains a suggested approach to attempt to do a bit more validation of the XRef table during the initial document loading phase. Here the choice is made to attempt to load the *first* page, as a basic sanity check of the validity of the XRef table. Please note that attempting to load a more-or-less arbitrarily chosen object without any context of what it's supposed to be isn't a very useful, which is why this particular choice was made. Obviously, just because the first page can be loaded successfully that doesn't guarantee that the *entire* XRef table is valid, however if even the first page fails to load you can be reasonably sure that the document is *not* valid[2]. Even though this patch won't cause any significant increase in the amount of parsing required during initial loading of the document[3], it will require loading of more data upfront which thus delays the initial `getDocument` call. Whether or not this is a problem depends very much on what you actually measure, please consider the following examples: ```javascript console.time('first'); getDocument(...).promise.then((pdfDocument) => { console.timeEnd('first'); }); console.time('second'); getDocument(...).promise.then((pdfDocument) => { pdfDocument.getPage(1).then((pdfPage) => { // Note: the API uses `pageNumber >= 1`, the Worker uses `pageIndex >= 0`. console.timeEnd('second'); }); }); ``` The first case is pretty much guaranteed to show a small regression, however the second case won't be affected at all since the Worker caches the result of `getPage` calls. Again, please remember that the second case is what matters for the standard PDF.js use-case which is why I'm hoping that this patch is deemed acceptable. --- [1] In issue 7496, the problem is that the document is edited without the XRef table being correctly updated. In issue 10326, the generator was sorting the XRef table according to the offsets rather than the objects. [2] The idea of checking the first page in particular came from the "standard" use-case for the PDF.js library, i.e. the default viewer, where a failure to load the first page basically means that nothing will work; note how `{BaseViewer, PDFThumbnailViewer}.setDocument` depends completely on being able to fetch the *first* page. [3] The only extra parsing is caused by, potentially, having to traverse *part* of the `Pages` tree to find the first page.
2018-12-05 05:51:27 +09:00
},
Hide .notdef glyphs in non-embedded Type1 fonts and don't ignore Widths Fixes #11403 The PDF uses the non-embedded Type1 font Helvetica. Character codes 194 and 160 (`Â` and `NBSP`) are encoded as `.notdef`. We shouldn't show those glyphs because it seems that Acrobat Reader doesn't draw glyphs that are named `.notdef` in fonts like this. In addition to testing `glyphName === ".notdef"`, we must test also `glyphName === ""` because the name `""` is used in `core/encodings.js` for undefined glyphs in encodings like `WinAnsiEncoding`. The solution above hides the `Â` characters but now the replacement character (space) appears to be too wide. I found out that PDF.js ignores font's `Widths` array if the font has no `FontDescriptor` entry. That happens in #11403, so the default widths of Helvetica were used as specified in `core/metrics.js` and `.nodef` got a width of 333. The correct width is 0 as specified by the `Widths` array in the PDF. Thus we must never ignore `Widths`.
2020-01-22 03:36:41 +09:00
{ "id": "issue11403",
"file": "pdfs/issue11403_reduced.pdf",
"md5": "08287b64f442cb7c329b97c4774aa1cd",
"rounds": 1,
"type": "eq"
},
Allow over-writing entries, in `XRef.indexObjects`, only when the generation number matches (issues 11230, 11139, 9552, 9129, 7303) This patch is making me somewhat worried about future regressions, since it's certainly easy to imagine this completely breaking certain kinds of corrupt/edited PDF documents while fixing others.[1] Obviously it passes all existing reference tests (and even improves one), however compared to many other patches there's no telling how much it could break. The only reason that I'm even submitting this patch, is because of the number of open issues that it would address. Generally speaking though, the best course of action would probably be if `XRef.indexObjects` was re-written to be much more robust (since it currently feels somewhat hand-wavy in parts). E.g. by actually checking/validating more of the objects before committing to them. --- [1] Especially given that it's reverting part of PR 5910, however in the case of issue 5909 it seems that other (more recent) changes have actually made that PR redundant.
2019-10-12 03:39:02 +09:00
{ "id": "issue11139",
"file": "pdfs/issue11139.pdf",
"md5": "006dd4f4bb1878bc14a12072d81a4524",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue11230",
"file": "pdfs/issue11230.pdf",
"md5": "db0a1464d8f9f3ce079b52e0cacdccd3",
"link": true,
"rounds": 1,
"firstPage": 100,
"lastPage": 100,
"type": "eq"
},
Add a RTL-text reference test (issue 10301) It seems that issue 10301 was fixed by PR 13424, by combining the spans, however given that we don't have a lot of test coverage for RTL-text I figured that adding a simple reference test wouldn't hurt (rather than just closing the issue as WORKSFORME).
2021-11-01 00:48:53 +09:00
{ "id": "issue10301",
"file": "pdfs/issue10301.pdf",
"md5": "c7ee7ba727969ab3bba12a4d13739303",
"rounds": 1,
"type": "text"
},
Don't duplicate the first entry in the `charCodeToGlyphId` map for CIDFontType2 fonts with a `CIDToGIDMap` that already mapped the first entry to a non-zero `glyphId` (issue 7544) Fixes 7544.
2016-08-16 19:23:53 +09:00
{ "id": "issue7544",
"file": "pdfs/issue7544.pdf",
"md5": "87e3a9fc7d6a6c1bd5b53af6926ce48e",
"link": false,
"rounds": 1,
"type": "eq"
},
Fix Type1 font parsing when .notdef is not at index zero Fixes #11477 The PDF draws many space characters but the embedded fonts don't have a glyph named `space`, so `.notdef` should be drawn instead. PDF.js assumed that Type1 fonts define `.notdef` as the first glyph (index 0). However, now the fonts have the glyph `A` at index 0 and `.notdef` is the last one, so `A` appears where spaces are expected. Because the rest of the font machinery in `core/fonts.js` assumes `.notdef` is at index zero, it's easiest to modify `core/type1_parser.js` so that it "repairs" fonts and makes sure `.notdef` is at index 0.
2020-03-04 04:55:51 +09:00
{ "id": "issue11477",
"file": "pdfs/issue11477_reduced.pdf",
"md5": "f4e5735569afce79e52b3fd56d10ae13",
"rounds": 1,
"type": "eq"
},
Add a reduced `load` test for issue 7665
2016-09-23 21:11:08 +09:00
{ "id": "issue7665",
"file": "pdfs/issue7665.pdf",
"md5": "f1199d16195a61e8232e2d1e742ed46b",
"link": false,
"rounds": 1,
"type": "load",
"about": "Encrypted file with indirect objects in the /Encrypt dictionary."
},
Add test case.
2011-11-30 08:47:53 +09:00
{ "id": "protectip",
"file": "pdfs/protectip.pdf",
"md5": "676e7a7b8f96d04825361832b1838a93",
"link": true,
"rounds": 1,
"type": "eq"
Add paperine test
2011-11-30 13:22:30 +09:00
},
Fixes glyph 0 in CIDTypeFont2
2013-07-30 05:24:32 +09:00
{ "id": "issue3427",
"file": "pdfs/issue3427.pdf",
"md5": "61979ede77f4557c65d4eb3c1a6dceeb",
"link": true,
"lastPage": 1,
"rounds": 1,
"type": "eq"
},
Add paperine test
2011-11-30 13:22:30 +09:00
{ "id": "piperine",
"file": "pdfs/piperine.pdf",
"md5": "603ca43dc5732dbba1579f122958c0c2",
"link": true,
"rounds": 1,
"type": "eq"
Add PDF from the #840 to the reference tests
2011-12-02 21:55:04 +09:00
},
{ "id": "issue840",
"file": "pdfs/issue840.pdf",
"md5": "20d88011dd7e3c4fb5274979094dab93",
"rounds": 1,
"type": "eq"
Use unicode mapping cmap when simple identity cmap was originally used
2011-12-06 11:42:39 +09:00
},
Prevent failures in the "scanning for endstream" code, in `Parser_makeStream`, by handling the case where 'endstream' is split between contiguous chunks (issue 1536)
2016-01-26 06:56:34 +09:00
{ "id": "issue1536",
"file": "pdfs/issue1536.pdf",
"md5": "bcaa52e6216399592ad5aa9fc49f1436",
"rounds": 1,
"link": true,
"firstPage": 6,
"lastPage": 6,
"type": "eq"
},
{ "id": "issue2098",
"file": "pdfs/issue2098.pdf",
"md5": "e9fa2b7cb935ffb95b510322d1e047e1",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
(#906) fixing glyph width defined by glyph name
2011-12-08 14:30:48 +09:00
{ "id": "bpl13210",
"file": "pdfs/bpl13210.pdf",
"md5": "8a08512baa9fa95378d9ad4b995947c7",
"link": true,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 5,
(#906) fixing glyph width defined by glyph name
2011-12-08 14:30:48 +09:00
"rounds": 1,
"type": "eq"
},
Further adjust the heuristics used to detect OpenType font files with CFF data, to ensure that all Type0 fonts are handled the same way regardless of font Subtype (issue 7901) Changing this particular code makes me somewhat nervous about regressions, since PR 5770 necessitated the follow-up PR 6270. However, the patch passes all tests added in those PRs (and obviously all other tests). Furthermore, I've manually checked all the issues/bugs referenced in PRs 5770 and 6270 without finding any issues. **Please note:** This patch fixes *only* the font bug, not the SVG conversion, present on pages two and three of the PDF file in issue 7901.
2016-12-21 00:42:15 +09:00
{ "id": "issue7901",
"file": "pdfs/issue7901.pdf",
"md5": "16059a3af6e81ae9272daa57ea03e6e9",
"rounds": 1,
"link": false,
"type": "eq"
},
Support Blend Modes which are specified in an Array of Names (issue 11279) According to the specification, the first *supported* Blend Mode should be choosen in this case; please see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G10.4848607
2019-10-26 18:57:56 +09:00
{ "id": "issue11279",
"file": "pdfs/issue11279.pdf",
"md5": "03361d24f3ed63b93f77abf731f8fc73",
"rounds": 1,
"link": false,
"type": "eq"
},
Only special-case OpenType fonts with `CFF` data if it's both a composite (i.e. Type0) font and also has a non-default CID to GID map (issue 8480) *As mentioned the last time that I touched this particular part of the font code, I'm sincerely hope that this doesn't cause any regressions!* However, the patch passes all tests added in PRs 5770, 6270, and 7904 (and obviously all other tests as well). Furthermore, I've manually checked all the issues/bugs referenced in those PRs without finding any issues. Fixes 8480.
2017-06-10 01:51:31 +09:00
{ "id": "issue8480",
"file": "pdfs/issue8480.pdf",
"md5": "769bc07bf8041d95667f2d32aaf75665",
"rounds": 1,
Further adjust the heuristics used to detect OpenType font files with CFF data, to ensure that all Type0 fonts are handled the same way regardless of font Subtype (issue 7901) Changing this particular code makes me somewhat nervous about regressions, since PR 5770 necessitated the follow-up PR 6270. However, the patch passes all tests added in those PRs (and obviously all other tests). Furthermore, I've manually checked all the issues/bugs referenced in PRs 5770 and 6270 without finding any issues. **Please note:** This patch fixes *only* the font bug, not the SVG conversion, present on pages two and three of the PDF file in issue 7901.
2016-12-21 00:42:15 +09:00
"link": false,
"type": "eq"
},
Add a reduced, `eq`, test-case for issue 9915
2018-07-27 23:57:58 +09:00
{ "id": "issue9915",
"file": "pdfs/issue9915_reduced.pdf",
"md5": "c56dabe5066a6c821901920e09dffe00",
"rounds": 1,
"link": false,
"type": "eq"
},
Fix how we detect and handle missing glyph data.
2017-06-29 02:34:36 +09:00
{ "id": "issue8570",
"file": "pdfs/issue8570.pdf",
"md5": "0355731adb72df233eaa10464dcc8c51",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a reduced test-case for issue 7696 Issue 7696 was one of the issues fixed by PR 8580. The other ones were all cases of missing glyphs, however in this particular one glyphs did render but every single one was incorrect. Hence it probably cannot hurt to have a small, reduced, reference test for that PDF file as well.
2017-07-24 16:51:40 +09:00
{ "id": "issue7696",
"file": "pdfs/issue7696.pdf",
"md5": "0593f52d03251164caa219d704a15e4c",
"rounds": 1,
"link": false,
"type": "eq"
},
Use unicode mapping cmap when simple identity cmap was originally used
2011-12-06 11:42:39 +09:00
{ "id": "tutorial",
"file": "pdfs/tutorial.pdf",
"md5": "6e122f618c27f3aa9a689423e3be6b8d",
"link": true,
"rounds": 1,
"type": "eq"
adds geothermal.pdf test
2011-12-07 13:33:59 +09:00
},
{ "id": "geothermal.pdf",
"file": "pdfs/geothermal.pdf",
"md5": "ecffc0ce38ffdf1e90dc952f186e9a91",
"rounds": 1,
"link": true,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 5,
adds geothermal.pdf test
2011-12-07 13:33:59 +09:00
"type": "eq"
Fixing TrueType code-glyph assigmnent to pass sanitizer
2011-12-08 11:59:44 +09:00
},
(#919) Fixing toUnicode mapping for TrueType fonts with identity mapping
2011-12-10 12:21:58 +09:00
{ "id": "issue919",
"file": "pdfs/issue919.pdf",
"md5": "3a1716a512aca4d7a8d6106bd4885d14",
"rounds": 1,
"link": true,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 3,
(#919) Fixing toUnicode mapping for TrueType fonts with identity mapping
2011-12-10 12:21:58 +09:00
"type": "eq"
Merge upstream.
2011-12-13 08:34:11 +09:00
},
Update `JpegImage.getData` to support `forceRGBoutput` for images with `numComponents === 1` (issue 6066) *A more robust solution for issue 6066.* As a temporary work-around for (the upstream) [bug 1164199](https://bugzilla.mozilla.org/show_bug.cgi?id=1164199), we parsed *all* images in the Firefox addon during a short time. Doing so uncovered an issue with our image handling (see 6066), for JPEG images with a `DeviceGray` ColorSpace *and* `bpc !== 1` (bits per component). As long as we let the browser handle image decoding in this case, this isn't going to be an issue, but I do think that we should proactively fix this to avoid future issues if we change where the images are decoded (in `jpg.js` vs in browser). Also, we currently don't seem to have a test-case for that kind of image data.
2016-02-08 21:49:30 +09:00
{ "id": "issue6066",
"file": "pdfs/issue6066.pdf",
"md5": "b26eb08fc5ab2518ba8fde603bdfc46b",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
[api-minor] Decode all JPEG images with the built-in PDF.js decoder in `src/core/jpg.js` Currently some JPEG images are decoded by the built-in PDF.js decoder in `src/core/jpg.js`, while others attempt to use the browser JPEG decoder. This inconsistency seem unfortunate for a number of reasons: - It adds, compared to the other image formats supported in the PDF specification, a fair amount of code/complexity to the image handling in the PDF.js library. - The PDF specification support JPEG images with features, e.g. certain ColorSpaces, that browsers are unable to decode natively. Hence, determining if a JPEG image is possible to decode natively in the browser require a non-trivial amount of parsing. In particular, we're parsing (part of) the raw JPEG data to extract certain marker data and we also need to parse the ColorSpace for the JPEG image. - While some JPEG images may, for all intents and purposes, appear to be natively supported there's still cases where the browser may fail to decode some JPEG images. In order to support those cases, we've had to implement a fallback to the PDF.js JPEG decoder if there's any issues during the native decoding. This also means that it's no longer possible to simply send the JPEG image to the main-thread and continue parsing, but you now need to actually wait for the main-thread to indicate success/failure first. In practice this means that there's a code-path where the worker-thread is forced to wait for the main-thread, while the reverse should *always* be the case. - The native decoding, for anything except the *simplest* of JPEG images, result in increased peak memory usage because there's a handful of short-lived copies of the JPEG data (see PR 11707). Furthermore this also leads to data being *parsed* on the main-thread, rather than the worker-thread, which you usually want to avoid for e.g. performance and UI-reponsiveness reasons. - Not all environments, e.g. Node.js, fully support native JPEG decoding. This has, historically, lead to some issues and support requests. - Different browsers may use different JPEG decoders, possibly leading to images being rendered slightly differently depending on the platform/browser where the PDF.js library is used. Originally the implementation in `src/core/jpg.js` were unable to handle all of the JPEG images in the test-suite, but over the last couple of years I've fixed (hopefully) all of those issues. At this point in time, there's two kinds of failure with this patch: - Changes which are basically imperceivable to the naked eye, where some pixels in the images are essentially off-by-one (in all components), which could probably be attributed to things such as different rounding behaviour in the browser/PDF.js JPEG decoder. This type of "failure" accounts for the *vast* majority of the total number of changes in the reference tests. - Changes where the JPEG images now looks *ever so slightly* blurrier than with the native browser decoder. For quite some time I've just assumed that this pointed to a general deficiency in the `src/core/jpg.js` implementation, however I've discovered when comparing two viewers side-by-side that the differences vanish at higher zoom levels (usually around 200% is enough). Basically if you disable [this downscaling in canvas.js](https://github.com/mozilla/pdf.js/blob/8fb82e939cf0c8618a4e775ff17fc96f726872b5/src/display/canvas.js#L2356-L2395), which is what happens when zooming in, the differences simply vanish! Hence I'm pretty satisfied that there's no significant problems with the `src/core/jpg.js` implementation, and the problems are rather tied to the general quality of the downscaling algorithm used. It could even be seen as a positive that *all* images now share the same downscaling behaviour, since this actually fixes one old bug; see issue 7041.
2020-01-20 20:10:16 +09:00
"type": "eq"
Update `JpegImage.getData` to support `forceRGBoutput` for images with `numComponents === 1` (issue 6066) *A more robust solution for issue 6066.* As a temporary work-around for (the upstream) [bug 1164199](https://bugzilla.mozilla.org/show_bug.cgi?id=1164199), we parsed *all* images in the Firefox addon during a short time. Doing so uncovered an issue with our image handling (see 6066), for JPEG images with a `DeviceGray` ColorSpace *and* `bpc !== 1` (bits per component). As long as we let the browser handle image decoding in this case, this isn't going to be an issue, but I do think that we should proactively fix this to avoid future issues if we change where the images are decoded (in `jpg.js` vs in browser). Also, we currently don't seem to have a test-case for that kind of image data.
2016-02-08 21:49:30 +09:00
},
Fix canvas state getting out of sync from smasks. (bug 1755507) Soft masks can be enabled/disabled at anytime and at different points in the save/restore stack. This can lead to the amount of save/restores becoming unbalanced across the two canvases. Instead of save/restoring on the temporary canvas change it so we only track state on the main (suspended canvas). I was also getting an out balance stack from patterns, so I've also fixed that and added a warning that will at least show up on chrome. It would be nice to add this so Firefox at some point too. Fixes #11328, #14297 and bug 1755507
2022-02-16 09:44:50 +09:00
{ "id": "bug1755507",
"file": "pdfs/bug1755507.pdf",
"md5": "319d73b8fd680cdc583d69b7f7ab29e9",
"rounds": 1,
"type": "eq"
},
Support cmaps with only CID characters, when building the ToUnicode-map (issue 9367) In this particular case the `CMap`-data that we create contains only numbers, but no strings, which causes `PartialEvaluator.readToUnicode` to create a ToUnicode-map with only empty strings. *Please note:* This is yet another case where I don't know if it's necessarily the best and most correct solution, but it does fix the referenced issue.
2021-09-18 07:01:24 +09:00
{ "id": "issue9367",
"file": "pdfs/issue9367.pdf",
"md5": "81a2c6f1fe5d1bb00ff0479aa6547155",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Fix copying on supplementary plane characters pdf.js had a problem when copying characters on supplementary planes (0xPPXXXX where PP is nonzero). This is because certain methods of PartialEvaluator use classic String.fromCharCode instead of ES6's String.fromCodePoint. Despite the fact that readToUnicode method *tried* to parse out-of-UCS2 code points by parsing UTF-16BE, it was inadequate because String.fromCharCode only supports UCS-2 range of Unicode.
2019-02-09 15:53:16 +09:00
{ "id": "issue10529",
"file": "pdfs/issue10529.pdf",
"md5": "1a4d404a137c610ff0c747cbea3b8666",
"rounds": 1,
"link": false,
"type": "text"
},
Improve glyph mapping for non-embedded composite standard fonts with a /CIDToGIDMap (issue 11915) *Please note:* All of this feels very handwavy, but at least it passes all tests locally. Hopefully we have enough tests for this part of the font code. For non-embedded composite standard fonts with an "incomplete" /CIDToGIDMap, we'll now fallback to an *explicitly defined* /ToUnicode map even when that one happens to be an /Identity-H or /Identity-V map. The `Font.fallbackToSystemFont` method is unfortunately getting more and more special-cases, however that might be unavoidable given all the weird non-embedded fonts found in the wild :-(
2021-09-15 18:06:25 +09:00
{ "id": "issue11915",
"file": "pdfs/issue11915.pdf",
"md5": "c4f890b4a5b6f21653421856335181d5",
"rounds": 1,
"type": "eq"
},
Handle corrupt ASCII85Decode inline images with whitespace "inside" of the EOD marker (issue 10614) There's a number of things wrong with the PDF document, since its inline images are first all *a lot* larger than the 4 KB limit (as mandated by the specification, see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G7.1852045). Furthermore the actual ASCII85Decode data is interspersed with *a lot* of needless whitespace, in particular also "inside" of the EOD (end-of-data) marker which thus completely breaks the detection. Note that according to the specification, see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G6.1940130, this patch should be safe since it explicitly mentions that *all* whitespace should be ignored.
2019-03-05 07:17:21 +09:00
{ "id": "issue10614",
"file": "pdfs/issue10614.pdf",
"md5": "c41da60ce9af100cb78e1c2a6ba18232",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Render Popup annotations last, once all other annotations have been rendered (issue 11362) In the current `AnnotationLayer` implementation, Popup annotations require that the parent annotation have already been rendered (otherwise they're simply ignored). Usually the annotations are ordered, in the `/Annots` array, in such a way that this isn't a problem, however there's obviously no guarantee that all PDF generators actually do so. Hence we simply ensure, when rendering the `AnnotationLayer`, that the Popup annotations are handled last.
2020-01-26 00:53:34 +09:00
{ "id": "issue11362",
"file": "pdfs/issue11362.pdf",
"md5": "bcb08162d4bff1d32ead8b563e866c93",
"rounds": 1,
"link": false,
"type": "eq",
"annotations": true
},
Handle corrupt ASCII85Decode inline images with truncated EOD markers (issue 11385) In the PDF document in question, there's an ASCII85Decode inline image where the '>' part of EOD (end-of-data) marker is missing; hence the PDF document is corrupt.
2019-12-05 23:44:51 +09:00
{ "id": "issue11385",
"file": "pdfs/issue11385.pdf",
"md5": "cc04b23b845366857426a5aa6acf227b",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Add a test-case for issue 4398 Issue 4398 was fixed by PR 4437, however a test-case wasn't included as far as I can tell. Given that PR 12186 is now in the process of re-factoring that code, adding a test-case cannot hurt as far as I'm concerned.
2020-08-08 18:43:46 +09:00
{ "id": "issue4398",
"file": "pdfs/issue4398.pdf",
"md5": "f3c1f967e99a1f5659e0e196f4293706",
"rounds": 1,
"type": "eq"
},
Fixes issue #6071. Corrects readBlockTiff() case for 1-bit depth and 1 color TIFF images incorporated in the PDF. Adds reference test for PDF used to fix this issue.
2016-12-05 04:44:12 +09:00
{ "id": "issue6071",
"file": "pdfs/issue6071.pdf",
"md5": "2e08526d8e7c9ba4269fc12ef488d3eb",
"rounds": 1,
"link": true,
"type": "eq"
},
Fixes incomplete restore in paintFormXObject
2012-10-27 13:30:01 +09:00
{ "id": "issue1905",
"file": "pdfs/issue1905.pdf",
"md5": "b1bbd72ca6522ae1502aa26320f81994",
"rounds": 1,
"type": "eq"
},
Add reftest for issue #918
2011-12-13 12:42:39 +09:00
{ "id": "issue918",
"file": "pdfs/issue918.pdf",
"md5": "d582cc0f2592ae82936589ced2a47e55",
"rounds": 1,
"type": "eq"
Merge upstream.
2011-12-15 06:41:36 +09:00
},
Fix type3 font loading regression.
2013-05-04 03:13:45 +09:00
{ "id": "issue3188",
"file": "pdfs/issue3188.pdf",
"md5": "161b72604d86f40ab2f765ddd3b61227",
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Don't check gen number for free entry; don't index objects twice
2012-04-24 12:14:58 +09:00
{ "id": "issue1586",
Replacing test with simulated bad pdf
2012-04-25 08:53:11 +09:00
"file": "pdfs/pdfjsbad1586.pdf",
"md5": "793d0870f0b0c613799b0677d64daca4",
Don't check gen number for free entry; don't index objects twice
2012-04-24 12:14:58 +09:00
"rounds": 1,
"type": "load"
},
Issue 6854 - Re-enable testing of 'aboutstacks.pdf' This test was disabled in PR 4732, because the file was no longer available. The motivation being that there were two other files which should be good replacements. However, one of those has since been replaced with a reduced test-case (which doesn't exercise the same code-path), and in the other one the error does not appear to be entirely identical. Hence it seems reasonable to re-add the 'aboutstacks.pdf' test, since it was possible to find it on the Internet Archive (by searching using a different URL, compared to the current one).
2016-01-12 20:55:31 +09:00
{ "id": "aboutstacks",
"file": "pdfs/aboutstacks.pdf",
"md5": "6e7c8416a293ba2d83bc8dd20c6ccf51",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Move char codes from high surrogate pair range into private use. Fixes #2884
2017-10-24 09:25:50 +09:00
{ "id": "issue2884_reduced",
"file": "pdfs/issue2884_reduced.pdf",
"md5": "18386542fc82affa2a5d3722549f8211",
"rounds": 1,
"link": false,
"lastPage": 1,
"type": "eq"
},
Respect the 'ColorTransform' entry in the image dictionary when decoding JPEG images (bug 956965, issue 6574) Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=956965. Fixes 6574.
2016-09-22 21:07:20 +09:00
{ "id": "bug956965",
"file": "pdfs/bug956965.pdf",
"md5": "9b2f1176c797ee84e989a507e745f89d",
"rounds": 1,
"link": true,
"firstPage": 33,
"lastPage": 33,
"type": "eq"
},
Always set a border-radius for RadioButton annotations (issue 15262)
2022-08-02 20:50:40 +09:00
{ "id": "issue15262",
"file": "pdfs/issue15262.pdf",
"md5": "f33f73848cea3c7034457653d5cfb9be",
"rounds": 1,
"type": "eq",
"forms": true
},
Add test case for smasks.
2011-12-17 03:54:31 +09:00
{ "id": "smaskdim",
"file": "pdfs/smaskdim.pdf",
Change test case.
2011-12-19 10:28:25 +09:00
"md5": "de80aeca7cbf79940189fd34d59671ee",
Add test case for smasks.
2011-12-17 03:54:31 +09:00
"rounds": 1,
"type": "eq"
Adds the missing test pdf to the manifest.
2011-12-30 05:39:00 +09:00
},
Adds endchar with 4 arguments test.
2013-03-05 05:28:04 +09:00
{ "id": "endchar",
"file": "pdfs/endchar.pdf",
"md5": "90a59acdd62252fdb4fefa482e12d6b3",
"rounds": 1,
"type": "eq"
},
Don’t skip glyph 0 in cmap.
2017-04-06 07:16:48 +09:00
{ "id": "issue8234",
"file": "pdfs/issue8234.pdf",
"md5": "32650fc60c51a9813b98bc9876dc15af",
"rounds": 1,
"type": "eq"
},
Cache JPEG images, just as we do for other image formats, in `evaluator.js` (issue 8380) For some reason, we're putting all kind of images *except* JPEG into the `imageCache` in `evaluator.js`.[1] This means that in the PDF file in issue 8380, we'll keep sending the *same* two small images[2] to the main-thread and decoding them over and over. This is obviously hugely inefficient! As can be seen from the discussion in the issue, the performance becomes *extremely* bad if the user has the addon "Adblock Plus" installed. However, even in a clean Firefox profile, the performance isn't that great. This patch not only addresses the performance implications of the "Adblock Plus" addon together with that particular PDF file, but it *also* improves the rendering times considerably for *all* users. Locally, with a clean profile, the rendering times are reduced from `~2000 ms` to `~500 ms` for my setup! Obviously, the general structure of the PDF file and its operator sequence is still hugely inefficient, however I'd say that the performance with this patch is good enough to consider the issue (as it stands) resolved.[3] Fixes 8380. --- [1] Not technically true, since inline images are cached from `parser.js`, but whatever :-) [2] The two JPEG images have dimensions 1x2, respectively 4x2. [3] To make this even more efficient, a new state would have to be added to the `QueueOptimizer`. Given that PDF files this stupid fortunately aren't too common, I'm not convinced that it's worth doing.
2017-05-07 19:34:47 +09:00
{ "id": "issue8380",
"file": "pdfs/issue8380.pdf",
"md5": "2782af6a4d0540fcea3897560f842094",
"rounds": 1,
"link": true,
"type": "eq"
},
Use correct matrix for patterns with showText. We were incorrectly using the transform in the pattern before it had been adjusted causing the pattern to be misplaced relative to the page. Fixes: ShowText-ShadingPattern.pdf (already in corpus) Fixes: #8111 Fixes: #9243
2021-11-05 08:45:48 +09:00
{ "id": "issue9243",
"file": "pdfs/issue9243.pdf",
"md5": "f6b8c5c62b8875f7d9dfcd2b25d3aab8",
"rounds": 1,
"type": "eq"
},
Don't map glyphs to the HANGUL FILLER (0x3164) Unicode location (issue 8424) *This patch follows a similar pattern as previous ones, by skipping certain problematic Unicode locations.* According to http://searchfox.org/mozilla-central/rev/6c2dbacbba1d58b8679cee700fd0a54189e0cf1b/gfx/harfbuzz/src/hb-unicode-private.hh#136, it seems that the HANGUL FILLER (0x3164) location is "special". Fixes 8424.
2017-05-23 23:08:02 +09:00
{ "id": "issue8424",
"file": "pdfs/issue8424.pdf",
"md5": "3de1ea4c085e8fe8e156153418058955",
"rounds": 1,
"link": false,
"type": "eq"
},
Address Yury's PR comments.
2011-12-31 02:24:13 +09:00
{ "id": "type4psfunc",
Adds the missing test pdf to the manifest.
2011-12-30 05:39:00 +09:00
"file": "pdfs/type4psfunc.pdf",
"md5": "7e6027a02ff78577f74dccdf84e37189",
"rounds": 1,
"type": "eq"
Add load test
2012-01-05 10:55:04 +09:00
},
Ensure that `TilingPattern`s have valid (non-zero) /BBox arrays (issue 8330) Fixes 8330.
2017-05-24 19:12:14 +09:00
{ "id": "issue8330",
"file": "pdfs/issue8330.pdf",
"md5": "9010093d07dd62d3b49378fd48cf45f9",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Include and use the 14 standard fonts files.
2020-12-11 10:32:18 +09:00
{ "id": "standard_fonts_system_fonts",
"file": "pdfs/standard_fonts.pdf",
"md5": "bb3a9ab3322328be983e8b4e8089843a",
"rounds": 1,
"type": "eq",
"useSystemFonts": true
},
{ "id": "standard_fonts_no_system_fonts",
"file": "pdfs/standard_fonts.pdf",
"md5": "bb3a9ab3322328be983e8b4e8089843a",
"rounds": 1,
"type": "eq",
"useSystemFonts": false
},
{ "id": "standard_fonts_main_thread_fetch",
"file": "pdfs/standard_fonts.pdf",
"md5": "bb3a9ab3322328be983e8b4e8089843a",
"rounds": 1,
"type": "eq",
"useSystemFonts": false,
"useWorkerFetch": false
},
Fix seac regression.
2014-04-12 01:55:39 +09:00
{ "id": "issue4573",
"file": "pdfs/issue4573.pdf",
"md5": "34b0c4fdee19e57033275b766c5f57a3",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"about": "Seac with differences array that messes up mapping."
},
Use |toUnicode| when creating the glyph map for standard CIDFontType2 fonts without embedded font file
2014-09-27 20:14:25 +09:00
{ "id": "issue2840",
"file": "pdfs/issue2840.pdf",
"md5": "d9df49f6d62668d099e0fb7e74f8f337",
"rounds": 1,
"link": false,
"type": "eq"
},
Apply Patterns, if necessary, when rendering text Currently we're not applying Patterns for text, but only for graphics. This patch is unfortunately not a complete solution, but rather a step on the way, since there are still some PDF files where the Patterns look more like a solid colour, rather than the intended gradient. I've been unable to fix these issues completely, and I've not managed to determine if the remaining issues are caused either by the pattern code, the canvas code, or perhaps both. However, given that even this simple patch improves the current situation quite a bit, I figured that it couldn't hurt to submit it as-is. - Fixes 5804. - Fixes 6130. - Improves 3988 a lot, since the text is now visible. However, it looks like the text is *one* solid colour, instead of the correct gradient. - Improves 5432, since the text is no longer gray. (This file also suffers from the same problem as the previous one.)
2015-12-30 01:57:10 +09:00
{ "id": "issue5804",
"file": "pdfs/issue5804.pdf",
"md5": "442f27939edb6aaf173ceff38d69bb14",
"rounds": 1,
"link": false,
"type": "eq"
},
Prevent errors when parsing Annotations with missing (or invalid) /Subtype entries (issue 7446) Note that I used a separate warning message for this case, instead of utilizing the same one as in the unsupported subtype case, to more clearly indicate that the PDF file itself is to blame rather than PDF.js. Fixes 7446.
2016-07-24 21:32:48 +09:00
{ "id": "issue7446",
"file": "pdfs/issue7446.pdf",
"md5": "1b5bdd8a806e6ab9eda7c1c707b75fc6",
"rounds": 1,
"link": false,
"type": "load",
"about": "Annotation without the required /Subtype."
},
Catch errors and continue parsing in `parseCMap` (issue 7492) After PR 7039, the PDF file in issue 7492 no longer renders at all, but note that text selection wasn't working correctly previously. The problem with the PDF file in issue 7492 is that the `cMap`, in the `toUnicode` entry in the font, contains an invalid name: ``` /CMapName /-usr-share-fonts-truetype-Panton-Panton Family-Fontfabric - Panton.otf,000-UTF16 def ``` When we parse that line, things obviously break because there are spaces present in the wrong places. To avoid that issue, the patch simply lets `parseCMap` continue when errors are encountered, to try and recover usable data. Note that by not aborting immediatly when an error is encountered, we are also able to fix the text selection. Obviously, it could be argued that we should just immediatly reject a corrupt `cMap`. But given that they usually are correct, it seems that trying to recover as much data as possible from corrupt one can only be a good thing for both glyph mapping and text selection. Fixes 7492.
2016-07-18 23:01:02 +09:00
{ "id": "issue7492-eq",
"file": "pdfs/issue7492.pdf",
"md5": "7b0b28919c1088a2a5a0aeedbaa4c3ca",
"rounds": 1,
"link": false,
"type": "eq"
},
{ "id": "issue7492-text",
"file": "pdfs/issue7492.pdf",
"md5": "7b0b28919c1088a2a5a0aeedbaa4c3ca",
"rounds": 1,
"link": false,
"type": "text"
},
Build a fallback `ToUnicode` map for simple fonts (issue 8229) In some fonts, the included `ToUnicode` data is incomplete causing text-selection to not work properly. For simple fonts that contain encoding data, we can manually build a `ToUnicode` map to attempt to improve things. Please note that since we're currently using the `ToUnicode` data during glyph mapping, in an attempt to avoid rendering regressions, I purposely didn't want to amend to original `ToUnicode` data for this text-selection edge-case. Instead, I opted for the current solution, which will (hopefully) give slightly better text-extraction results in PDF file with incomplete `ToUnicode` data. According to the PDF specification, see [section 9.10.2](http://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1873172): > A conforming reader can use these methods, in the priority given, to map a character code to a Unicode value. > ... Reading that paragraph literally, it doesn't seem too unreasonable to use *different* methods for different charcodes. Fixes 8229.
2017-11-26 21:29:43 +09:00
{ "id": "issue8229",
"file": "pdfs/issue8229.pdf",
"md5": "a729f663782e87ebc1efad0755ebf6a5",
"rounds": 1,
"link": false,
"type": "text"
},
Apply Patterns, if necessary, when rendering text Currently we're not applying Patterns for text, but only for graphics. This patch is unfortunately not a complete solution, but rather a step on the way, since there are still some PDF files where the Patterns look more like a solid colour, rather than the intended gradient. I've been unable to fix these issues completely, and I've not managed to determine if the remaining issues are caused either by the pattern code, the canvas code, or perhaps both. However, given that even this simple patch improves the current situation quite a bit, I figured that it couldn't hurt to submit it as-is. - Fixes 5804. - Fixes 6130. - Improves 3988 a lot, since the text is now visible. However, it looks like the text is *one* solid colour, instead of the correct gradient. - Improves 5432, since the text is no longer gray. (This file also suffers from the same problem as the previous one.)
2015-12-30 01:57:10 +09:00
{ "id": "ShowText-ShadingPattern",
"file": "pdfs/ShowText-ShadingPattern.pdf",
"md5": "fe683725db037ffe19d390969610a652",
"rounds": 1,
"link": false,
"type": "eq",
"about": "Please note that this file currently renders incorrectly."
},
Fix invalid `XUID` entries in CFF fonts In CFF fonts, entry `XUID` should be an array that has no more than 16 elements. In the issue, the length is 20, which causes the fonts to fail. See Appendix B, "Implementation Limits" in PostScript Language Reference Manual https://web.archive.org/web/20170218093716/https://www.adobe.com/products/postscript/pdfs/PLRM.pdf Actually entries `XUID` and `UniqueID` are obsolete altogether. https://blogs.adobe.com/CCJKType/2016/06/no-more-xuid-arrays.html
2020-10-05 23:38:01 +09:00
{ "id": "issue12399",
"file": "pdfs/issue12399_reduced.pdf",
"md5": "01bdd258be93e10f8399708eecedbfd6",
"rounds": 1,
"type": "eq"
},
Attempt to ignore multiple identical Tf (setFont) commands in `PartialEvaluator_getTextContent` (issue 5808) This patch improves the performance of issue 5808, but I'm not sure if it's enough to call it fixed. On average, this patch reduces the number of textLayer div's by a factor of 3, and it also reduces the time spend in `getTextContent` by a factor of ~2. The PDF file is generated by `Scribus PDF`, which for reasons I cannot understand is placing redundant `Tf` commands before *every* showText command. Note how the PDF file also contains lots of (basically) identical fonts, but with slightly different names, which causes unnecessary font-switching. This causes some unnecessary breaking of textLayer div's, but this issue cannot be easily worked around.
2016-06-01 06:01:35 +09:00
{ "id": "issue5808-text",
"file": "pdfs/issue5808.pdf",
"md5": "e0584dd540d7859d6c191aa53379692e",
"rounds": 1,
"link": false,
"type": "text"
},
Improve text-selection for Type3 fonts with bogus /FontBBox-entries (issue 14999) This extends PR 13461, by also building a fallback bounding box for Type3 fonts that contain a much too small /FontBBox-entry. *Please note:* While this patch improves things overall, copy-and-pasting still doesn't work perfectly for this document. In particular the lowercase letter "c" cannot be selected/copied, however this can be reproduced in both Adobe Reader and PDFium (in Google Chrome) too, which is caused by a lack of proper /ToUnicode-data in the PDF document.
2022-07-05 21:08:53 +09:00
{ "id": "issue14999",
"file": "pdfs/issue14999_reduced.pdf",
"md5": "a4e664e734f6869aa66245e72d448874",
"rounds": 1,
"type": "text"
},
For embedded Type1 fonts without included `ToUnicode`/`Encoding` data, attempt to improve text selection by using the `builtInEncoding` to amend the `toUnicode` map (issue 6901, issue 7182, issue 7217, bug 917796, bug 1242142) Note that in order to prevent any possible issues, this patch does *not* try to amend the `toUnicode` data for Type1 fonts that contain either `ToUnicode` or `Encoding` entries in the font dictionary. Fixes, or at least improves, issues/bugs such as e.g. 6658, 6901, 7182, 7217, bug 917796, bug 1242142.
2016-08-18 01:33:06 +09:00
{ "id": "issue6901-eq",
"file": "pdfs/issue6901.pdf",
"md5": "1a0604b1a7a3aaf2162b425a9a84230b",
"rounds": 1,
"link": false,
"type": "eq"
},
{ "id": "issue6901-text",
"file": "pdfs/issue6901.pdf",
"md5": "1a0604b1a7a3aaf2162b425a9a84230b",
"rounds": 1,
"link": false,
"type": "text"
},
Don't allow `adjustToUnicode` to extend a built-in /ToUnicode map (issue 15352) Given that the change in PR 13393 was slightly speculative, given the lack of test-cases, let's just revert part of that to fix the referenced issue. Based on a quick look at old issues and existing test-cases, it seems that most (if not all) PDF documents that benefit from using the font-data in this way lack any /ToUnicode maps which should mean that they're unaffected by these changes.
2022-09-04 05:55:24 +09:00
{ "id": "issue15352",
"file": "pdfs/issue15352.pdf",
"md5": "d0edf452a85821acf41cbfa0a6f2f2ac",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "text"
},
Attempt to combine text runs positioned with `setTextMatrix`
2016-05-15 05:13:12 +09:00
{ "id": "issue6962",
"file": "pdfs/issue6962.pdf",
"md5": "d40e871ecca68baf93114bd28c782148",
"rounds": 1,
"link": false,
"type": "text"
},
Avoid getting stuck in empty nodes in the Pages tree when calling |Catalog_getPageDict| (issue 5644)
2015-01-17 20:53:32 +09:00
{ "id": "issue5644",
"file": "pdfs/issue5644.pdf",
"md5": "6f9313c5043b3ecb0ab2df321d3e1847",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 6,
"type": "eq"
},
Always check all Kids nodes, in `Catalog.getPageDict`, to avoid getting stuck in an empty node further down in the Pages tree (issue 8088) As discussed on IRC, we need to check all nodes at the *bottom* of the tree to ensure that we find the correct `Page` dict. Furthermore, this patch also gets rid of the caching present in a previous version, since it's not clear if that really helps. Note that this patch purposely adds an `eq` test, using a reduced test-case, so that we can be sure that the algorithm actually finds the correct `Page` dict for each `pageIndex`. Fixes 8088.
2017-02-23 21:28:50 +09:00
{ "id": "issue8088",
"file": "pdfs/issue8088.pdf",
"md5": "5bbc33c7433799487518eb0d8094348c",
"rounds": 1,
"link": false,
"firstPage": 1,
"lastPage": 3,
"type": "eq"
},
Fix loading of fonts with empty font files (bug 866395 and issue 3522)
2014-05-18 07:57:06 +09:00
{ "id": "bug866395",
"file": "pdfs/bug866395.pdf",
"md5": "f03bc77e84637241980b09a0a220f575",
"link": false,
"rounds": 1,
"type": "eq",
"about": "Font with an empty font file."
},
Ignore 'endobj' commands inside of `ObjStm` streams (issue 5241, bug 898610, bug 1037816) According to an example in the PDF specification, see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=56, an `ObjStm` stream should not contain 'endobj' commands. Fixes 5241. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=898610. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1037816.
2016-05-09 01:28:18 +09:00
{ "id": "bug1037816",
"file": "pdfs/bug1037816.pdf",
"md5": "8a45299d7b102a9c1cadb8883b8debc9",
"rounds": 1,
"link": true,
"lastPage": 1,
Skip extra objects in object stream in using offsets
2021-03-28 02:45:48 +09:00
"type": "eq",
Ignore 'endobj' commands inside of `ObjStm` streams (issue 5241, bug 898610, bug 1037816) According to an example in the PDF specification, see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=56, an `ObjStm` stream should not contain 'endobj' commands. Fixes 5241. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=898610. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1037816.
2016-05-09 01:28:18 +09:00
"about": "ObjStm stream containing 'endobj' commands."
},
Add load test
2012-01-05 10:55:04 +09:00
{ "id": "ocs",
"file": "pdfs/ocs.pdf",
"md5": "2ade57e954ae7632749cf328daeaa7a8",
"rounds": 1,
"link": true,
"type": "load"
Merge branch 'master' of git://github.com/mozilla/pdf.js.git into tree-53 Conflicts: test/test_manifest.json
2012-01-05 10:57:08 +09:00
},
JBIG2: finds end of segment when length is not specified
2013-02-23 23:04:17 +09:00
{ "id": "issue2139",
"file": "pdfs/issue2139.pdf",
"md5": "ee4072992e7c5ffd5063181916a2fcae",
"rounds": 1,
"link": true,
"type": "eq"
},
Ref test for #1010
2012-01-12 13:19:21 +09:00
{ "id": "issue1010",
"file": "pdfs/issue1010.pdf",
"md5": "f991ef093484a107fe9f59dff18fc155",
"rounds": 1,
"link": true,
"type": "eq"
},
Adjusts MacRoman switch heuristics threshold
2012-05-19 01:14:09 +09:00
{ "id": "issue1709",
"file": "pdfs/issue1709.pdf",
"md5": "84497bd23b7c82d03d2681a1cb1d9ed0",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 10,
Adjusts MacRoman switch heuristics threshold
2012-05-19 01:14:09 +09:00
"link": true,
"type": "eq"
},
Ensure that the /Annots-entry, on /Page-instances, is actually an Array (issue 12714) In the referenced PDF document, the second and third page has *corrupt* /Annots-entries which contain /Dict-data rather than the intended Arrays.
2020-12-10 19:31:46 +09:00
{ "id": "issue12714",
"file": "pdfs/issue12714.pdf",
"md5": "f9ee31c74f9e342e95122b0b3bc84fa0",
"rounds": 1,
"firstPage": 2,
"lastPage": 2,
"link": true,
"type": "eq"
},
Ignore, rather than throwing on, unsupported Coding style default (COD) options in JPEG 2000 images (issue 11004) Similar to other markers that we currently skip, by ignoring unsupported Coding style default (COD) options we'll at least render *something* here (although some JPEG 2000 images may look slightly wrong). Note that if the unsupported COD options lead to additional errors, during parsing, we'll still abort parsing of the JPEG 2000 image.
2020-12-22 04:24:13 +09:00
{ "id": "issue11004",
"file": "pdfs/issue11004.pdf",
"md5": "25d79508f2c9ef0e2327564966138fc1",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Ignore, rather than throwing on, Coding style component (COC) markers in JPEG 2000 images (issue 12752) Similar to other markers that we currently skip, by ignoring the Coding style component (COC) marker we'll at least prevent outright errors (although some JPEG 2000 images may look slightly wrong).
2020-12-18 23:42:28 +09:00
{ "id": "issue12752",
"file": "pdfs/issue12752.pdf",
"md5": "9f8ada17a613d18919714baf684e165f",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Fallback to using the `name` table to infer the encoding for TrueType fonts missing such data (issue 15910) The relevant TrueType font is missing both /ToUnicode *and* /Encoding entires, either of which would have prevented the (current) broken textLayer rendering. My first idea was that we could use the `post` table in the TrueType font, see https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6post.html, to get the actual glyphNames and amend the fallback ToUnicode-map that way. Unfortunately that didn't work, since the `post` table only contained ".notdef" and "" (i.e. empty string) entries. Instead we try to use the `name` table in the TrueType font, see https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6name.html, to determine if the platform is Windows and thus fallback to generate a ToUnicode-map from the `WinAnsiEncoding`.
2023-01-17 23:26:58 +09:00
{ "id": "issue15910",
"file": "pdfs/issue15910.pdf",
"md5": "6429d8490e11e226b1cbdf2033c04237",
"rounds": 1,
"type": "text"
},
Add a parameter to `Page_getInheritedPageProp` to make it possible to fetch (and dereference) Arrays, and use that for the `MediaBox`/`CropBox` getters (issue 7872)
2016-12-06 18:21:42 +09:00
{ "id": "issue7872",
"file": "pdfs/issue7872.pdf",
"md5": "81781dfecfcb7e9cd9cc7e60f8b747b7",
"rounds": 1,
"link": false,
"type": "eq",
"about": "MediaBox and CropBox with indirect objects."
},
Fix handling of symbolic fonts and unicode cmaps. In issue 12120, the font has a 1,0 cmap and is marked symbolic which according to the spec means we should directly use the cmap instead of the extra steps that are defined in 9.6.6.4. However, just fixing that caused bug 1057544 to break. The font in bug 1057544 has a 0,1 cmap (Unicode 1.1) which we were not using, but is easy to support. We're also easily able to support some of the other unicode cmaps, so I added those as well. There was also a second issue with bug 1057544, the cmap doesn't have a mapping for the "quoteright" glyph, but it is defined in the post table. To handle this, I've moved post table as a fallback for any font that has an encoding.
2020-08-22 07:25:07 +09:00
{ "id": "bug1057544",
"file": "pdfs/bug1057544.pdf",
"md5": "49ad71b82ead1ee0fe4ddb41aa9e30b4",
"rounds": 1,
"type": "eq"
},
Add a *linked* test-case for issue 2618 Given that this PDF document is an interesting test-case for performance reasons, w.r.t. inline image caching, it probably can't hurt to add it to the test-suite to make it more readily available. Considering the contents of that PDF document I'm not sure if we can include it directly in the repository, hence why a *linked* test-case was choosen here.
2022-11-13 00:20:19 +09:00
{ "id": "issue2618",
"file": "pdfs/issue2618.pdf",
"md5": "2c554a99a52288ca1a44a422eeafb8fb",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Fixes symbols positioning in JBIG2
2013-02-23 13:08:46 +09:00
{ "id": "issue2642",
"file": "pdfs/issue2642.pdf",
"md5": "b6679861fdce3bbab0c1fa51bb7f5077",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Don't traverse all pages to get a single page.
2013-11-14 08:27:46 +09:00
{ "id": "issue3848",
"file": "pdfs/issue3848.pdf",
"md5": "2498cf0650cc97ceca3e24dfa0425a73",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "load",
"about": "Document tree with pages and page nodes on the same level."
},
Adding test PDF
2012-01-05 04:49:37 +09:00
{ "id": "issue1015",
"file": "pdfs/issue1015.pdf",
"md5": "b61503d1b445742b665212866afb60e2",
"rounds": 1,
"link": true,
"type": "eq"
add liveprogramming as load test
2012-01-10 11:37:39 +09:00
},
Changing glyphNameMap and GlyphUnicode lookup order
2012-01-22 08:18:36 +09:00
{ "id": "issue1096",
"file": "pdfs/issue1096.pdf",
"md5": "7f75d2b4b93c78d401ff39e8c1b00612",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 9,
Changing glyphNameMap and GlyphUnicode lookup order
2012-01-22 08:18:36 +09:00
"link": true,
"type": "eq"
},
Fixing standard encoding mapping
2012-01-27 09:51:58 +09:00
{ "id": "issue1127",
"file": "pdfs/issue1127.pdf",
"md5": "4fb2be5ffefeafda4ba977de2a1bb4d8",
"rounds": 1,
"link": true,
"type": "eq"
},
Add support for the /Catalog Base-URI when resolving URLs (issue 14802) As far as I can tell, this is actually the very first time that we've seen a PDF document with a Base-URI specified in the /Catalog; please refer to the specification: https://web.archive.org/web/20220309040754if_/https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G11.2097122 To simplify the overall implementation, this new parameter is accessed via the existing `BasePdfManager.docBaseUrl`-getter and will thus override any user-specified `docBaseUrl` API-parameter.
2022-04-19 23:53:44 +09:00
{ "id": "issue14802",
"file": "pdfs/issue14802.pdf",
"md5": "c1e774945fee539c7fcfec00b36dd4e6",
"rounds": 1,
"type": "eq",
"annotations": true,
"about": "LinkAnnotation with a relative link, and a /Catalog Base-URI."
},
Ensure that worker-thread image caching doesn't break optional content (issue 14824) Currently we only insert optionalContent-data into the operatorList the first time that an image is parsed, which will (in hindsight) obviously cause problems for cached images. Hence we also need to insert the optionalContent-data in the various worker-thread image caches, such that it can be accessed in the fast-paths that are used to skip re-parsing of images. In order to reduce the amount of repeated code, this patch also adds a new `OperatorList`-method that takes care of inserting the necessary data in the operatorList.
2022-04-22 21:30:25 +09:00
{ "id": "issue14824",
"file": "pdfs/issue14824.pdf",
"md5": "7b8d061ab0a342e3606a3b3ba1925d5b",
"rounds": 1,
"link": true,
"lastPage": 4,
"type": "eq",
"optionalContent": {
"7R": false
},
"about": "Need to test *at least* three pages, since the `GlobalImageCache` is involved."
},
Adjust the heuristics for handling of incomplete path operators (issue 14917) This limits the heuristics for handling of incomplete path operators, see PR 9838, to only apply to *sequences* of such operators. In practice a couple of invalid path operators are (hopefully) unlikely to completely break rendering, whereas a sequence of them will easily lead to fairly chaotic rendering artifacts.
2022-05-15 18:12:00 +09:00
{ "id": "issue14917",
"file": "pdfs/issue14917.pdf",
"md5": "12201b35853f78a501ac46b91608f8b6",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Add a couple more, mostly `text`, reference tests for non-embedded symbolic fonts without included encoding information I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones. Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts. To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases. However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly. Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite. Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-10 20:10:15 +09:00
{ "id": "issue1127-text",
"file": "pdfs/issue1127.pdf",
"md5": "4fb2be5ffefeafda4ba977de2a1bb4d8",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "text"
},
Add load test for Issue #4461
2014-03-18 22:07:54 +09:00
{ "id": "issue4461-load",
"file": "pdfs/issue4461.pdf",
"md5": "9df4ecaae429adb5dc93d9342a53159d",
"rounds": 1,
"type": "load",
"about": "Document without /Resources entry in page dictionary"
},
Check if glyph are stored outside the glyf table
2012-02-20 11:12:57 +09:00
{ "id": "issue1249-load",
"file": "pdfs/issue1249.pdf",
"md5": "4f81339fa09422a7db980f34ea963609",
"rounds": 1,
"type": "load"
},
add liveprogramming as load test
2012-01-10 11:37:39 +09:00
{ "id": "liveprogramming",
"file": "pdfs/liveprogramming.pdf",
"md5": "7bd4dad1188232ef597d36fd72c33e52",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 3,
add liveprogramming as load test
2012-01-10 11:37:39 +09:00
"link": true,
"type": "load"
Add example PDF from #268
2012-01-12 11:14:49 +09:00
},
Avoid floating point inaccuracy in gradient color stops
2019-09-18 03:01:17 +09:00
{ "id": "issue7339",
"file": "pdfs/issue7339_reduced.pdf",
"md5": "7092ab6a1acc31db9d1caaa0447334a0",
"rounds": 1,
"type": "eq"
},
Skip mapping of CIDFontType2 glyphs in fonts with a |IdentityToUnicodeMap|, unless |properties.widths| is defined for the glyph Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1142033. Also fixes issue 5874.
2015-04-30 19:40:54 +09:00
{ "id": "bug1142033",
"file": "pdfs/bug1142033.pdf",
"md5": "1d9afd397e89a0f52c056f449ec93daa",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Ignore line-breaks between operator and digit in `Lexer.getNumber` This is consistent with the behaviour in Adobe Reader (and PDFium), and it fixes the display of page 30 in https://bug1354114.bmoattachments.org/attachment.cgi?id=8855457 (taken from https://bugzilla.mozilla.org/show_bug.cgi?id=1354114). The patch also makes the `error` message for invalid numbers slightly more useful, by including the charCode as well. (Having that information available would have reduced the time spent on debugging the PDF file above.)
2017-05-02 21:14:03 +09:00
{ "id": "bug1354114",
"file": "pdfs/bug1354114.pdf",
"md5": "ad718d04702d29a37792c7f222fe1fa6",
"rounds": 1,
"firstPage": 30,
"link": true,
"type": "eq"
},
Skip mapping of CIDFontType2 glyphs in fonts with a |IdentityToUnicodeMap|, unless |properties.widths| is defined for the glyph Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1142033. Also fixes issue 5874.
2015-04-30 19:40:54 +09:00
{ "id": "issue5874",
"file": "pdfs/issue5874.pdf",
"md5": "25922edf223aa91bc259663d0a34a6ab",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a (linked) `load` test for PR 4731 Re: PR 4731. Since the URL points to the Internet Archive, I think that adding a linked test-case should be OK. (Also, it's difficult to create reduced, or even `unit`, tests that accurately captures the brokenness of real-world PDF files.) *Please note:* Since this is a `load` test, `makeref`ing won't be needed.
2015-08-31 23:55:25 +09:00
{ "id": "pr4731",
"file": "pdfs/pr4731.pdf",
"md5": "0121642027e525c4b95357f1b5669e64",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "load"
},
Add support of Ink annotation
2018-09-30 23:29:16 +09:00
{ "id": "annotation-caret-ink",
"file": "pdfs/annotation-caret-ink.pdf",
"md5": "6218ca235580d1975474c979e0128c2d",
"rounds": 1,
"type": "eq",
"annotations": true
},
Include a reduced test case for annotations without a `Border`/`BS` entry (PR 6180 follow-up)
2019-11-10 22:37:42 +09:00
{ "id": "issue6179_reduced",
"file": "pdfs/issue6179_reduced.pdf",
"md5": "457ff3561b83346ae3caf91acd252040",
"rounds": 1,
"type": "eq",
"annotations": true
},
[api-minor] Always allow e.g. rendering to continue even if there are errors, and add a `stopAtErrors` parameter to `getDocument` to opt-out of this behaviour (issue 6342, issue 3795, bug 1130815) Other PDF readers, e.g. Adobe Reader and PDFium (in Chrome), will attempt to render as much of a page as possible even if there are errors present. Currently we just bail as soon the first error is hit, which means that we'll usually not render anything in these cases and just display a blank page instead. NOTE: This patch changes the default behaviour of the PDF.js API to always attempt to recover as much data as possible, even when encountering errors during e.g. `getOperatorList`/`getTextContent`, which thus improve our handling of corrupt PDF files and allow the default viewer to handle errors slightly more gracefully. In the event that an API consumer wishes to use the old behaviour, where we stop parsing as soon as an error is encountered, the `stopAtErrors` parameter can be set at `getDocument`. Fixes, inasmuch it's possible since the PDF files are corrupt, e.g. issue 6342, issue 3795, and [bug 1130815](https://bugzilla.mozilla.org/show_bug.cgi?id=1130815) (and probably others too).
2017-02-19 22:03:08 +09:00
{ "id": "bug1130815-eq",
"file": "pdfs/bug1130815.pdf",
"md5": "3ff3b550c3af766991b2a1b11d00de85",
"rounds": 1,
"link": true,
"type": "eq"
},
{ "id": "bug1130815-text",
"file": "pdfs/bug1130815.pdf",
"md5": "3ff3b550c3af766991b2a1b11d00de85",
"rounds": 1,
"link": true,
"type": "text"
},
Add a (linked) test-case for issue 3248
2016-04-21 22:27:18 +09:00
{ "id": "issue3248",
"file": "pdfs/issue3248.pdf",
"md5": "970767ed68de46c316d74de67965999b",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "load"
},
Allow `getOperatorList`/`getTextContent` to skip errors when parsing broken XObjects (issue 8702, issue 8704) This patch makes use of the existing `ignoreErrors` property in `src/core/evaluator.js`, see PRs 8240 and 8441, thus allowing us to attempt to recovery as much as possible of a page even when it contains broken XObjects. Fixes 8702. Fixes 8704.
2017-09-17 20:35:18 +09:00
{ "id": "issue8702-eq",
"file": "pdfs/issue8702.pdf",
"md5": "59d501ed1518d78ef6ee442cf824b0f6",
"rounds": 1,
"link": false,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue8702-text",
"file": "pdfs/issue8702.pdf",
"md5": "59d501ed1518d78ef6ee442cf824b0f6",
"rounds": 1,
"link": false,
"lastPage": 1,
"type": "text"
},
Add a (linked) test-case for PR 4897 Re: PR 4897.
2015-10-04 20:45:07 +09:00
{ "id": "pr4897",
"file": "pdfs/pr4897.pdf",
"md5": "26897633eea5e6d10345a130b1c1777c",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Work-around for HighlightAnnotations without a top-level /ExtGState-entry (issue 13242) For HighlightAnnotations with a built-in appearance stream, we still rely on it to specify the opacity correctly via a suitable blend mode. However, if the Annotation-drawing operators are placed *within* a /XObject of the /Form-type, the /ExtGState won't apply to the final rendering and the result is that the highlighting obscures the underlying text. The more *correct* and general solution would likely be to somehow modify the implementation in `src/display/canvas.js`, to special-case handling of /Form-type /XObjects when rendering Annotations. Since we can very easily work-around this problem for now by using the "no appearance stream" code-path, doing *something* here ought to be preferable. This patch is (obviously) merely a work-around, but given that the referenced issue is (as far as I know) the first case we've seen of this problem a simple solution will hopefully suffice for now.
2021-05-28 20:30:18 +09:00
{ "id": "issue13242",
"file": "pdfs/issue13242.pdf",
"md5": "ceb2da908c972087eb90e6bae240bce9",
"rounds": 1,
"type": "eq",
"annotations": true
},
Adjust incorrect first obj number of "free" xref entry in `XRef_readXRefTable` (issue 7229) Fixes 7229.
2016-04-21 22:10:40 +09:00
{ "id": "issue7229",
"file": "pdfs/issue7229.pdf",
"md5": "480e51aae0ac271780e4603d1561d15e",
"rounds": 1,
"link": false,
"lastPage": 1,
"type": "load"
},
Add (linked) ´load` tests for PR 1976 and 4606 Adds a couple of `load` tests for the `XRef` parsing part of the code-base, see PR 1976 and 4606.
2015-09-04 20:19:32 +09:00
{ "id": "issue1940",
"file": "pdfs/issue1940.pdf",
"md5": "4f0a0b92c1b5e6e86e1a82490087e6e5",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "load"
},
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
{ "id": "160F-2019",
"file": "pdfs/160F-2019.pdf",
"md5": "71591f11ee717e12887f529c84d5ae89",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"427R": {
"hidden": false,
"value": "hello world"
}
}
},
[api-minor] Always allow e.g. rendering to continue even if there are errors, and add a `stopAtErrors` parameter to `getDocument` to opt-out of this behaviour (issue 6342, issue 3795, bug 1130815) Other PDF readers, e.g. Adobe Reader and PDFium (in Chrome), will attempt to render as much of a page as possible even if there are errors present. Currently we just bail as soon the first error is hit, which means that we'll usually not render anything in these cases and just display a blank page instead. NOTE: This patch changes the default behaviour of the PDF.js API to always attempt to recover as much data as possible, even when encountering errors during e.g. `getOperatorList`/`getTextContent`, which thus improve our handling of corrupt PDF files and allow the default viewer to handle errors slightly more gracefully. In the event that an API consumer wishes to use the old behaviour, where we stop parsing as soon as an error is encountered, the `stopAtErrors` parameter can be set at `getDocument`. Fixes, inasmuch it's possible since the PDF files are corrupt, e.g. issue 6342, issue 3795, and [bug 1130815](https://bugzilla.mozilla.org/show_bug.cgi?id=1130815) (and probably others too).
2017-02-19 22:03:08 +09:00
{ "id": "issue6342-eq",
"file": "pdfs/issue6342.pdf",
"md5": "2ea85ca8d17117798f105be88bdb2bfd",
"rounds": 1,
"link": false,
"type": "eq"
},
{ "id": "issue6342-text",
"file": "pdfs/issue6342.pdf",
"md5": "2ea85ca8d17117798f105be88bdb2bfd",
"rounds": 1,
"link": false,
"type": "text"
},
Use widths defined by font for standard fonts. There doesn't seem to be anything definitive about this in the spec, but from experimenting, it seems acrobat lets PDFs override the widths of the standard fonts.
2020-12-11 08:29:07 +09:00
{ "id": "bug1671312_reduced",
"file": "pdfs/bug1671312_reduced.pdf",
"md5": "db13fe3f03a7d0bd0e248f5c2bcb2a5d",
"rounds": 1,
"type": "eq"
},
Always re-measure non-embedded ArialNarrow fonts (bug 1671312, PR 12725 follow-up) While PR 12725 fixed bug 1671312 as reported, i.e. the "In the upper right corner "Purposes' has bad kerning."-part, it however broke other parts of the text rendering. Note in particular the tables, e.g. on page 2 and beyond, where the glyphs are now rendered too close together. The reason for this is that the fonts in question are non-embedded ArialNarrow, which we just replace with Helvetica which obviously is not narrow. Given that the font replacement isn't a perfect fit for non-embedded ArialNarrow, we still need to re-measure the glyph widths in this case.
2021-01-14 23:34:44 +09:00
{ "id": "bug1671312_ArialNarrow",
"file": "pdfs/bug1671312_ArialNarrow.pdf",
"md5": "f4f0a0d1dc9276bd6e3402165ecdc3d7",
"rounds": 1,
"type": "eq"
},
Avoid accidentally getting the entire font file in `readNameTable` (issue 7020) In the PDF file in question, some of the 'name' table entries have `record.length === 0`. This becomes problematic in the non-unicode case, since `font.getBytes(0)` will fetch the *entire* stream. Given that OTS rejects 'name' entries larger than `2^16`, this thus explain the sanitizer errors. Fixes 7020.
2016-03-02 05:39:33 +09:00
{ "id": "issue7020",
"file": "pdfs/issue7020.pdf",
"md5": "93b464e21c649e64ae92eeafe99fc31b",
"link": false,
"rounds": 1,
"type": "eq"
},
Handle ranges that "overflow" the last byte in `CMap.mapBfRange` (bug 1627427)
2021-10-24 18:51:57 +09:00
{ "id": "bug1627427",
"file": "pdfs/bug1627427_reduced.pdf",
"md5": "3ff75fcf455af49803f0f04eb071bdc3",
"link": false,
"rounds": 1,
"type": "text"
},
Attempt to improve non-embedded Wingdings font support (bug 1652224) Now that font-substitution has been implemented, we should be able to do much a better job at supporting non-embedded Wingdings fonts. Given that this is a Windows-specific font, see https://en.wikipedia.org/wiki/Wingdings, this is however not guaranteed to work (well) on other platforms.
2023-05-22 01:15:45 +09:00
{ "id": "issue11451",
"file": "pdfs/issue11451.pdf",
"md5": "a2fd3c4596ad75562df83a2494263802",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
{ "id": "bug1652224",
"file": "pdfs/bug1652224.pdf",
"md5": "0e1bb427f32e83dc8f091842f7a11ac4",
"rounds": 1,
"link": true,
"firstPage": 5,
"lastPage": 5,
"type": "eq"
},
Fix missing notdef in expert encoding.
2017-06-30 03:52:49 +09:00
{ "id": "issue8586",
"file": "pdfs/issue8586.pdf",
"md5": "16b5230364017d3b0d2d65978eb35816",
"link": false,
"rounds": 1,
"type": "eq"
},
Keep track of the character to glyph mapping in font_renderer.js, to prevent errors when different characters point to the same glyph (issue 7101) Fixes 7101.
2016-03-23 21:52:30 +09:00
{ "id": "issue7101",
"file": "pdfs/issue7101.pdf",
"md5": "cc9cabe12ac9ad49e5372ef33d10aeb4",
"link": false,
"rounds": 1,
"type": "eq"
Ensure that the `params` parameter of the `PredictorStream` is a dictionary (issue 7200) Fixes 7200.
2016-04-15 21:22:36 +09:00
},
{ "id": "issue7200",
"file": "pdfs/issue7200.pdf",
"md5": "ddae17424ea23930eecf8b612a66ed0f",
"link": false,
"rounds": 1,
"type": "eq"
Keep track of the character to glyph mapping in font_renderer.js, to prevent errors when different characters point to the same glyph (issue 7101) Fixes 7101.
2016-03-23 21:52:30 +09:00
},
Enforce line width to be at least 1px after applied transform * add a comment to explain how minimal linewidth is computed. * when context.linewidth < 1 after transform, firefox and chrome don't render in the same way (issue #12810). * set lineWidth to 1 after transform and before stroking - aims fix issue #12295 - a pixel can be transformed into a rectangle with both heights < 1. A single rescale leads to a rectangle with dim equals to 1 and the other to something greater than 1. * change the way to render rectangle with null dimensions: - right now we rely on the lineWidth set before "re" but it can be set after "re" and before "S" and in this case the rendering will be wrong. - render such rectangles as a single line.
2021-01-04 22:25:30 +09:00
{ "id": "issue12810",
"file": "pdfs/issue12810.pdf",
"md5": "585e19781308603dd706f941b1ace774",
"rounds": 1,
"type": "eq"
},
Add (linked) ´load` tests for PR 1976 and 4606 Adds a couple of `load` tests for the `XRef` parsing part of the code-base, see PR 1976 and 4606.
2015-09-04 20:19:32 +09:00
{ "id": "pr4606",
"file": "pdfs/pr4606.pdf",
"md5": "6574fde2314648600056bd0e229df98c",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "load"
},
Add example PDF from #268
2012-01-12 11:14:49 +09:00
{ "id": "S2-eq",
"file": "pdfs/S2.pdf",
"md5": "d0b6137846df6e0fe058f234a87fb588",
"rounds": 1,
"type": "eq"
Merge branch 'master' of git://github.com/mozilla/pdf.js.git into jpx6 Conflicts: test/test_manifest.json
2012-01-19 11:14:43 +09:00
},
Fixes #1055 by falling back to page resources
2012-01-18 04:40:52 +09:00
{ "id": "issue1055",
Replace the unavailable linked test-case for issue 1055 with a reduced test-case Re: issue 1055 and PR 1095.
2015-11-18 21:47:56 +09:00
"file": "pdfs/issue1055r.pdf",
"md5": "4aa72bb4779e3f301c45492f2a590459",
"rounds": 1,
"link": false,
"type": "eq"
Fix zero width lines.
2012-01-18 13:50:49 +09:00
},
Reference test for 1629
2012-05-18 08:34:31 +09:00
{ "id": "issue1629",
"file": "pdfs/issue1629.pdf",
"md5": "0f2cbbf268383a377e95e6bbe36c6a9a",
"rounds": 1,
"link": true,
"type": "eq"
},
Only choose a (3, 1) cmap table for TrueType fonts that have an encoding specified (issue 6410) For (1, 0) cmaps, we have two different codepaths depending on whether the font has/hasn't got an encoding. But with (3, 1) cmaps we don't have a good fallback when the encoding is missing, hence this patch changes `readCmapTable` to only choose a (3, 1) cmap table if the font is non-symbolic *and* an encoding exists. Without this, we'll not be able to successfully create a working glyph map for some TrueType fonts with (3, 1) cmap tables. Fixes 6410.
2015-09-07 00:16:31 +09:00
{ "id": "issue6410",
"file": "pdfs/issue6410.pdf",
"md5": "fd5c5898d5b9754bb546724b7d31bf59",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a reduced test-case for issue 6413
2015-09-04 05:29:12 +09:00
{ "id": "issue6413",
"file": "pdfs/issue6413.pdf",
"md5": "08926ac7a46e27a4abbb31256b3a7b29",
"rounds": 1,
"link": false,
"type": "eq"
},
Discards invalid values for Blues
2012-08-12 13:05:41 +09:00
{ "id": "issue1685",
"file": "pdfs/issue1685.pdf",
"md5": "b22c3741e6bd0e613d3eb3325ad31f7d",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Discards invalid values for Blues
2012-08-12 13:05:41 +09:00
"link": true,
Reference test for 1629
2012-05-18 08:34:31 +09:00
"type": "eq"
},
Browser minimal font adjustment
2012-02-05 03:45:18 +09:00
{ "id": "issue1169",
"file": "pdfs/issue1169.pdf",
"md5": "3df3ed21fd43ac7fdb21e2015c8a7809",
"rounds": 1,
"link": true,
"type": "eq"
},
Add a couple more, mostly `text`, reference tests for non-embedded symbolic fonts without included encoding information I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones. Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts. To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases. However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly. Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite. Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-10 20:10:15 +09:00
{ "id": "issue2017-eq",
"file": "pdfs/issue2017r.pdf",
"md5": "5d2bc43b386496cfb8841ca677db7046",
"rounds": 1,
"link": false,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue2017-text",
"file": "pdfs/issue2017r.pdf",
"md5": "5d2bc43b386496cfb8841ca677db7046",
"rounds": 1,
"link": false,
"lastPage": 1,
"type": "text"
},
Ignore .notdef in the `differences` array when building a fallback `toUnicode` map in `PartialEvaluator_buildToUnicode` (issue 5256) Fixes 5256.
2016-06-27 20:51:11 +09:00
{ "id": "issue5256",
"file": "pdfs/issue5256.pdf",
"md5": "9383e17ced31f9afc940fb7898df8e68",
"rounds": 1,
"link": false,
"type": "eq"
},
Also check `maybeLength` when deciding if a stream is empty in `Parser_makeFilter` (issue 6360) The problem with the PDF files in the issue, besides the obviously broken XRef tables which we're able to recover from, is that many/most of the streams have Dictionaries where the `Length` entry is set to `0`. This causes us to return `NullStream`, instead of the appropriate one in `Parser_makeFilter`. Fixes 6360.
2015-08-21 06:01:48 +09:00
{ "id": "issue6360",
"file": "pdfs/issue6360.pdf",
"md5": "58c5455ffd84b1c07ad2d0fa90cd5e26",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Avoid infinite loop when getting annotation field name - aims to fix issue #12963; - use a Set to track already visited objects; - remove the loop limit in getInheritableProperty and use a RefSet too.
2021-02-06 20:23:35 +09:00
{ "id": "issue12963",
"file": "pdfs/issue12963.pdf",
"md5": "2590047a2ef0113e698d888c29918008",
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"annotations": true
},
Only skip parsing a stream in `Parser_makeFilter` when we know for sure that it is empty (PR 6372 follow-up) For PDF files with multiple `/Filter`s, where the `/Length` entry is zero, we fail to render the file correctly. The reason is that `maybeLength` is `null` for the every filter except the first, and `!maybeLength` is thus truthy. Hence it seems that we should completely ignore the `/Length` entry and also explicitly check `maybeLength === 0`. Note that I've not (yet) come across a PDF file with this issue in the wild, but given all the stupid things PDF generators do I wouldn't be surprised if such a file actually exists. In order to prevent a possible future bug, I'm submitting this patch which includes a hand-edited PDF file that we currently cannot render correctly (but e.g. Adobe Reader can).
2016-09-25 19:19:22 +09:00
{ "id": "multiple-filters-length-zero",
"file": "pdfs/multiple-filters-length-zero.pdf",
"md5": "c273c3a6fb79cbf3034fe1b62b204728",
"rounds": 1,
"link": false,
"type": "eq"
},
Make `XRef_indexObjects` more robust against bad PDF files (issue 5752) This patch improves the detection of `xref` in files where it is followed by an arbitrary whitespace character (not just a line-breaking char). It also adds a check for missing whitespace, e.g. `1 0 obj<<`, to speed up `readToken` for the PDF file in the referenced issue. Finally, the patch also replaces a bunch of magic numbers with suitably named constants. Fixes 5752. Also improves 6243, but there are still issues.
2015-08-21 23:57:08 +09:00
{ "id": "issue5752",
"file": "pdfs/issue5752.pdf",
"md5": "aa20ad7cff71e9481c0cd623ddbff3b7",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Add a couple of reduced test-cases for PR 4259 PR 4259 fixed a large number of font bugs, but none of those where added as test-cases. This was, in my opinion, unfortunate since it increases the risk of regressions in the future when other font bugs are fixed. This PR simply adds a few more test-cases, to improve our test coverage somewhat.
2014-07-31 20:46:11 +09:00
{ "id": "issue2931",
"file": "pdfs/issue2931.pdf",
"md5": "ea40940eaf3541b312bda9329167da11",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 4260 (PR 4521 follow-up)
2020-06-30 16:24:01 +09:00
{ "id": "issue4260",
"file": "pdfs/issue4260_reduced.pdf",
"md5": "6b39ebc8c4dddc41f1b031c070c212ad",
"rounds": 1,
"type": "eq"
},
Add ZapfDingbats testcase
2014-09-04 04:57:57 +09:00
{ "id": "ZapfDingbats",
"file": "pdfs/ZapfDingbats.pdf",
"md5": "980df9b1c86715a3d8aa2d3c807a2b2c",
"link": false,
"rounds": 1,
"type": "eq"
},
Prevent `readCmapTable` from failing if the `cmap` is missing in TrueType fonts Fixes http://arrow.dit.ie/cgi/viewcontent.cgi?article=1000&context=aaschadpoth#page=3.
2015-11-08 21:18:23 +09:00
{ "id": "TrueType_without_cmap",
"file": "pdfs/TrueType_without_cmap.pdf",
"md5": "afca8bb11f2e1f7298b4e5dd85785fb0",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a fallback for non-embedded SegoeUISymbol font (issue 8697) The PDF file uses a non-embedded SegoeUISymbol font, which is *not* a standard font (and is mainly used by Microsoft, see https://en.wikipedia.org/wiki/Segoe). Fixes 8697.
2017-07-25 18:57:38 +09:00
{ "id": "issue8697",
"file": "pdfs/issue8697.pdf",
"md5": "65c6f0d861d49fa685051a64c3f78694",
"link": false,
"rounds": 1,
"type": "eq"
},
Improve rendering of non-embedded NuptialScript font *This patch fixes something that I noticed while debugging https://bugzilla.mozilla.org/show_bug.cgi?id=1308536.* The PDF file contains a font called "NuptialScript", which unfortunately is not embedded. Since that is a non-standard font we will not be able to render it entirely correct. However, by adding "NuptialScript" to the `getNonStdFontMap`, we can at least improve the rendering slightly by using an italic (serif) fallback font.
2016-10-08 21:06:28 +09:00
{ "id": "non-embedded-NuptialScript",
"file": "pdfs/non-embedded-NuptialScript.pdf",
"md5": "94225085d3fbf5d2d12b8be1c52bb3c1",
"link": false,
"rounds": 1,
"type": "eq"
},
Enable/disable image smoothing based on image interpolate value. (bug 1722191) While some of the output looks worse to my eye, this behavior more closely matches what I see when I open the PDFs in Adobe acrobat. Fixes: #4706, #9713, #8245, #1344
2021-09-09 09:31:10 +09:00
{ "id": "issue4706",
"file": "pdfs/issue4706.pdf",
"md5": "f3e90a3cf52550583fa2a07a138b8660",
"rounds": 1,
"type": "eq"
},
Add a fallback for non-embedded *composite* Tahoma fonts (issue 15719)
2022-11-23 23:51:18 +09:00
{ "id": "issue15719",
"file": "pdfs/issue15719.pdf",
"md5": "4a58dbe725897e787a93e26abc621191",
"link": true,
"rounds": 1,
"type": "eq",
"optionalContent": {
"37R": false
}
},
Always parse the entire `startXRefQueue` in `XRef.readXRef` (issue 15833) Previously we'd abort all parsing if an Error was encountered, despite the fact that multiple `startXRefQueue`-entries may be available and that continued parsing could thus eventually be able to find usable data. Note that in the referenced PDF document the `startxref`-operator, at the end of the file, points to a position in the middle of an arbitrary `stream` which is why things break.
2022-12-15 21:35:39 +09:00
{ "id": "issue15833",
"file": "pdfs/issue15833.pdf",
"md5": "9562d027b980ea2779dcfb1669f9cf7e",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Add a fallback for non-embedded *composite* Verdana fonts (issue 11242) Obviously this won't look exactly right, but considering that the PDF file doesn't bother embedding non-standard fonts this is the best that we can do here.
2019-10-15 21:06:54 +09:00
{ "id": "issue11242",
"file": "pdfs/issue11242_reduced.pdf",
"md5": "ba50b6ee537f3e815ccfe0c99e598e05",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a couple of reduced test-cases for PR 4259 PR 4259 fixed a large number of font bugs, but none of those where added as test-cases. This was, in my opinion, unfortunate since it increases the risk of regressions in the future when other font bugs are fixed. This PR simply adds a few more test-cases, to improve our test coverage somewhat.
2014-07-31 20:46:11 +09:00
{ "id": "issue3323",
"file": "pdfs/issue3323.pdf",
"md5": "1a14ff574013caeafa9d598269988764",
"link": false,
"rounds": 1,
"type": "eq"
},
Fix several issues with radial/axial shadings and tiling patterns. Previously, we set the base transformation and pattern matrix directly to the main rendering ctx of the page, however doing this caused the current transform to be lost. This would cause issues with things like shear missing so the pattern was misaligned or when stroke was used the scale of the line width or dash would be wrong. Instead we should leave the current transform and use setTransfrom on the pattern so it is applied correctly. For axial and radial shadings I had to create a temporary canvas to draw the shading so I could in turn use setTransform. Fixes: #13325, #6769, #7847, #11018, #11597, #11473 The following already in the corpus are improved: issue8078-page1 issue1877-page1
2021-05-11 09:43:37 +09:00
{ "id": "issue6769",
"file": "pdfs/issue6769.pdf",
"md5": "724b94d6bd1e8010403328446d0ab061",
"rounds": 1,
"type": "eq"
},
Add a couple of reduced test-cases for PR 4259 PR 4259 fixed a large number of font bugs, but none of those where added as test-cases. This was, in my opinion, unfortunate since it increases the risk of regressions in the future when other font bugs are fixed. This PR simply adds a few more test-cases, to improve our test coverage somewhat.
2014-07-31 20:46:11 +09:00
{ "id": "issue4304",
"file": "pdfs/issue4304.pdf",
"md5": "1b1205bf0d7c1ad22a154b60da8e694d",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a reduced test case for issue 4379 This should have been part of PR 5136. Based on comments https://github.com/mozilla/pdf.js/issues/4379#issuecomment-51221787 and https://github.com/mozilla/pdf.js/issues/4379#issuecomment-51475463, it should be OK to include the PDF file in the repo.
2014-12-30 00:28:23 +09:00
{ "id": "issue4379",
"file": "pdfs/issue4379.pdf",
"md5": "09715ec1a7b0f3a7ae02b3046f627b9f",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a (linked) load test for issue 4387 Re: PR 4404 and issue 4387.
2015-10-04 20:12:07 +09:00
{ "id": "issue4387",
"file": "pdfs/issue4387.pdf",
"md5": "e06da177b5b9e36016fa2442510d62da",
"rounds": 1,
"link": true,
"type": "load"
},
JS - Handle correctly hierarchy of fields (#13133) * JS - Handle correctly hierarchy of fields - it aims to fix #13132; - annotations can inherit their actions from the parent field; - there are some fields which act as a container for other fields: - they can be access through js so need to add them with an empty type (nothing in the spec about that but checked in Acrobat); - calculation order list (CO) can reference them so need make them through this.getField; - getArray method must return kids. - field values are number, string, ... depending of their type but nothing in the spec on how to know what's the type: - according to the comment for Canonical Format: https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#page=461 - it seems that this "type" can be guessed from js action Format (when setting a type in Acrobat DC, the only affected thing is this action). - util.scand with an empty string returns the current date.
2021-03-31 00:50:35 +09:00
{ "id": "issue13132",
"file": "pdfs/issue13132.pdf",
"md5": "1b28964b9188047bc6c786302c95029f",
"link": true,
"type": "other"
},
Add fallback for non-embedded "Century Gothic" CIDFontType2 font (issue 4722 and bug 879561) According to practical experiments, falling back to "Helvetica" when we encounter a non-embedded "[Century Gothic](http://en.wikipedia.org/wiki/Century_Gothic)" `CIDFontType2` font seems to work well. (Also, the section on Wikipedia about "Printer ink usage" *might* provide some anecdotal evidence that Century Gothic is a fairly standard sans-serif font.) Obviously this patch doesn't make "Century Gothic" fonts render perfectly, as is often the case with non-embedded fonts, but all the text is now legible in the referenced issues. Fixes 4722. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=879561.
2014-12-12 01:29:26 +09:00
{ "id": "issue4722",
"file": "pdfs/issue4722.pdf",
"md5": "a42ca858af7d179358f92f47e57c0fed",
"link": false,
"rounds": 1,
"type": "eq"
},
Replace command with not enough args by an endchar in CFF font - Right now, a glyph with an erroneous outline is replaced by an empty glyph if the error is far enough from the start there's likely something to render so the idea is to replace a command with args by an endchar when no args are on the stack: this way OTS is likely happy (no remaining args on stack) and we can draw something which is likely better than nothing.
2021-05-14 20:38:26 +09:00
{ "id": "issue6132",
"file": "pdfs/issue6132.pdf",
"md5": "bd1e6252ca642acf2cd05db1748a073c",
"rounds": 1,
"type": "eq"
},
Add reduced test-cases for issues 4875 and 4881
2014-08-04 01:34:52 +09:00
{ "id": "issue4875",
"file": "pdfs/issue4875.pdf",
"md5": "9a558e18029a42c0ef4e9a8755e24733",
"link": false,
"rounds": 1,
"type": "eq"
},
{ "id": "issue4881",
"file": "pdfs/issue4881.pdf",
"md5": "e1f06be05eda4ddf734e9764f3f067f1",
"link": false,
"rounds": 1,
"type": "eq"
},
Add a reduced test case for issue 5291
2014-10-25 18:35:13 +09:00
{ "id": "issue5291",
"file": "pdfs/issue5291.pdf",
"md5": "edae085495c702069ffdbf785a826556",
"link": false,
"rounds": 1,
"type": "eq"
},
Further amend GlyphMapForStandardFonts (issue 5244)
2014-08-29 21:15:19 +09:00
{ "id": "issue5244",
"file": "pdfs/issue5244.pdf",
"md5": "a50cd364c3976c744627b4b9bb90c761",
"link": false,
"rounds": 1,
"type": "eq"
},
Don't map glyphs to certain problematic Thai/Lao Unicode locations (issue 5994) *This patch depends on PR 5990.* According to https://dxr.mozilla.org/mozilla-central/source/gfx/harfbuzz/src/hb-ot-shape-fallback.cc#38, certain Thai/Lao characters are treated as special by the font shaping code in Firefox. Further down in that file, https://dxr.mozilla.org/mozilla-central/source/gfx/harfbuzz/src/hb-ot-shape-fallback.cc#216, the vertical position of glyphs is modified, which should thus explain why some glyphs end up in the wrong position in the PDF file. Fixes 5994.
2015-05-11 04:48:17 +09:00
{ "id": "issue5994",
"file": "pdfs/issue5994.pdf",
"md5": "6799733a39d29b3828d6628bf2c5c382",
"rounds": 1,
"link": false,
"type": "eq"
},
Consume the current character when encountering illegal characters in `Lexer.getObject`, in order to prevent infinite loops during reading of streams (issue 8061) *Please note:* The rendering of the PDF file in issue 8061 first regressed in PR 7039, and then PR 7493 exacerbated the problem even further by causing an infinite loop. In this particular case, when errors were encountered inside of the `Lexer.getObject` method *itself*, we didn't advance the stream position. This thus caused an inifinite loop in `parseCMap`, since the exact same character was then parsed over and over again. Fixes 8061.
2017-02-12 03:11:52 +09:00
{ "id": "issue8061",
"file": "pdfs/issue8061.pdf",
"md5": "d61fe1dcdcd55bca00b351b2fc2c6dc7",
"rounds": 1,
"link": false,
"type": "eq"
},
Fallback to the `StandardEncoding` for Nonsymbolic fonts without `/Encoding` entry (issue 7580) Even though this patch passes all tests (unit/font/reference) locally, including the new ones that I added in PR 7621, I'm still a bit nervous about modifying the code that choose the fallback encoding for fonts without an `/Encoding` entry. Note that over the years this code has been changed on a number of occasions, see a possibly incomplete [list here], to deal with various cases of incorrect font data. According to the PDF specification, see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1904184, it seems that we should fallback to the `StandardEncoding` for Nonsymbolic fonts. There's obviously a risk that fixing this particular issue *could* break other PDF files for which we don't have tests. However I've tried to change the logic as little as possible in this patch, to hopefully reduce possible breakage. Based on debugging numerous font issue, it seems that a lot of fonts actually set the Symbolic flag, even when they are in fact *not* Symbolic. Fonts actually marked as Nonsymbolic seem to be somewhat less common, which I hope should reduce the risk of the patch somewhat. Fixes 7580.
2016-09-13 20:43:23 +09:00
{ "id": "issue7580-eq",
"file": "pdfs/issue7580.pdf",
"md5": "44dd5a9b4373fcab9890cf567722a766",
"rounds": 1,
"link": false,
"type": "eq"
},
Implement visibility expressions for optional content
2021-04-14 20:58:43 +09:00
{ "id": "visibility_expressions",
"file": "pdfs/visibility_expressions.pdf",
"md5": "bc530d90984ddaa2cc7e0cd53fc2cf34",
"rounds": 1,
"type": "eq"
XFA - Add Liberation-Sans font as a substitution for some missing fonts - Some js files contain scale factors for each glyph in order to rescale Liberation to have a final font with the correct width. - A lot of XFA have some containers where their dimensions are based on their text content, so using default font from browser can lead to an almost unreadable pdf.
2021-06-09 03:50:31 +09:00
},
XFA - Add support for reftests
2021-06-07 22:20:29 +09:00
{ "id": "hsbc",
"file": "pdfs/hsbc.pdf",
"md5": "34a63a9ed9cdf3790562a3dfd1703e48",
"rounds": 1,
"link": true,
"enableXfa": true,
"type": "eq"
},
XFA - Flush contents when breakBefore target is 'auto' - some page can be missed in the final document because of that (see pdf in the test case which has 4 pages (when only 3 are rendered right now)
2021-06-11 00:00:27 +09:00
{ "id": "hsbc_closure",
"file": "pdfs/xfa_hsbc_closure.pdf",
"md5": "7d101861d6232fe5f658e8aeca5c9891",
"rounds": 1,
"link": true,
"enableXfa": true,
"type": "eq"
},
XFA - Add Liberation-Sans font as a substitution for some missing fonts - Some js files contain scale factors for each glyph in order to rescale Liberation to have a final font with the correct width. - A lot of XFA have some containers where their dimensions are based on their text content, so using default font from browser can lead to an almost unreadable pdf.
2021-06-09 03:50:31 +09:00
{ "id": "xfa_imm1344e",
"file": "pdfs/xfa_imm1344e.pdf",
"md5": "f9b8b6e7d385691efdea2544576f5eb2",
"rounds": 1,
"link": true,
"enableXfa": true,
"type": "eq"
},
Fallback to the `StandardEncoding` for Nonsymbolic fonts without `/Encoding` entry (issue 7580) Even though this patch passes all tests (unit/font/reference) locally, including the new ones that I added in PR 7621, I'm still a bit nervous about modifying the code that choose the fallback encoding for fonts without an `/Encoding` entry. Note that over the years this code has been changed on a number of occasions, see a possibly incomplete [list here], to deal with various cases of incorrect font data. According to the PDF specification, see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1904184, it seems that we should fallback to the `StandardEncoding` for Nonsymbolic fonts. There's obviously a risk that fixing this particular issue *could* break other PDF files for which we don't have tests. However I've tried to change the logic as little as possible in this patch, to hopefully reduce possible breakage. Based on debugging numerous font issue, it seems that a lot of fonts actually set the Symbolic flag, even when they are in fact *not* Symbolic. Fonts actually marked as Nonsymbolic seem to be somewhat less common, which I hope should reduce the risk of the patch somewhat. Fixes 7580.
2016-09-13 20:43:23 +09:00
{ "id": "issue7580-text",
"file": "pdfs/issue7580.pdf",
"md5": "44dd5a9b4373fcab9890cf567722a766",
"rounds": 1,
"link": false,
"type": "text"
},
[api-minor] Add a parameter to `PDFPageProxy_getTextContent` that enables replacing of all whitespace with standard spaces in the textLayer (issue 6612) This patch goes a bit further than issue 6612 requires, and replaces all kinds of whitespace with standard spaces. When testing this locally, it actually seemed to slightly improve two existing test-cases (`tracemonkey-text` and `taro-text`). Fixes 6612.
2015-11-24 00:57:43 +09:00
{ "id": "issue6612-text",
"file": "pdfs/issue6612.pdf",
"md5": "657f33236496916597cd70ef1222509a",
"rounds": 1,
"link": false,
"type": "text"
},
Fix zero width lines.
2012-01-18 13:50:49 +09:00
{ "id": "zerowidthline",
"file": "pdfs/zerowidthline.pdf",
"md5": "295d26e61a85635433f8e4b768953f60",
"rounds": 1,
"link": false,
"type": "eq"
Lab color space, closes #1133
2012-02-02 07:48:44 +09:00
},
Only mask char codes of (3, 0) cmap tables in the range of 0xF000 to 0xF0FF.
2017-06-30 09:14:58 +09:00
{ "id": "issue8187",
"file": "pdfs/issue8187.pdf",
"md5": "1724dcada47b90c9217ee0139d8352a8",
"rounds": 1,
"link": false,
"type": "eq"
},
Parse Type1 font files to determine the various `Length{n}` properties, instead of trusting the PDF file (issue 5686, issue 3928) Fixes 5686. Fixes 3928.
2016-03-06 06:32:54 +09:00
{ "id": "issue5686",
"file": "pdfs/issue5686.pdf",
"md5": "78d16b9df07a355ad00d70504a9194f8",
"rounds": 1,
"link": false,
"type": "eq",
"about": "Type1 font where Length1/Length2 are slightly incorrect."
},
{ "id": "issue3928",
"file": "pdfs/issue3928.pdf",
"md5": "1963493f843e981cbe768b707ef7f08a",
"rounds": 1,
"link": false,
"type": "eq",
"about": "Type1 font where Length1/Length2 are several orders of magnitude too large."
},
Fix inverted 1-bit images in SVG backend
2017-11-29 04:24:27 +09:00
{ "id": "images_1bit_grayscale",
"file": "pdfs/images_1bit_grayscale.pdf",
"md5": "e1c36a19563944891bd30cfc0199d07f",
"rounds": 1,
"type": "eq"
},
Sanitizing the glyphs to avoid OTS rejections
2012-02-13 12:11:44 +09:00
{ "id": "html5checker",
"file": "pdfs/html5checker.pdf",
"md5": "74bbd80d1e7eb5f2951582233ef9ebab",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 7,
Sanitizing the glyphs to avoid OTS rejections
2012-02-13 12:11:44 +09:00
"link": true,
"type": "eq"
},
Try to skip mapping of missing TrueType glyphs Also don't skip mapping of glyphs which are empty, if the corresponding charCode is included in toUnicode.
2015-02-07 08:13:41 +09:00
{ "id": "issue5704",
"file": "pdfs/issue5704.pdf",
"md5": "6e0b62585feef24dff2d7e7687cd8128",
"rounds": 1,
"link": false,
"type": "eq"
},
Fetch parameters if they are a |Ref| in CalGray/CalRGB color spaces (issue 5747)
2015-02-20 19:19:21 +09:00
{ "id": "issue5747",
"file": "pdfs/issue5747.pdf",
"md5": "5c36afc931dd1a3321ffa2e88952d174",
"rounds": 1,
"link": false,
Try to skip mapping of missing TrueType glyphs Also don't skip mapping of glyphs which are empty, if the corresponding charCode is included in toUnicode.
2015-02-07 08:13:41 +09:00
"type": "eq"
},
Add a test-case for issue 6099 - CalRGB color space where the parameters are a |Ref| The issue is already fixed by PR 5748, but we didn't have access to a suitable test-case. Thanks to issue 6099, we are now able to add one!
2015-06-10 00:52:36 +09:00
{ "id": "issue6099",
"file": "pdfs/issue6099.pdf",
"md5": "f8e9a26637c1b0d35f2bc653122a9c73",
"rounds": 1,
"link": false,
"type": "eq"
},
Add upper-case `I` as a possible space replacement fallback in `Font.spaceWidth` to improve text-selection (issue 7180) In fonts with only upper-case glyphs, that are also missing a space glyph, `get spaceWidth` won't be able to return anything useful. By adding upper-case `I` as a fallback, we can thus improve text-selection in some PDF files. Note that locally, the patch causes slight movement in a few existing `text` tests, but in my opinion this actually looks like slight improvements. Fixes 7180.
2016-06-08 05:40:06 +09:00
{ "id": "issue7180-text",
"file": "pdfs/issue7180.pdf",
"md5": "73ed92d7ca55475f1f31d1d75fee3283",
"rounds": 1,
"link": false,
"type": "text"
},
Fixes canvas state after smask group ends.
2015-12-04 05:34:12 +09:00
{
Replaces test for #6720 to fix botio-linux slow script.
2015-12-06 03:33:25 +09:00
"id": "bug1123803",
"file": "pdfs/bug1123803.pdf",
"md5": "0f3870ac5ad8899aec34d734e045a514",
Fixes canvas state after smask group ends.
2015-12-04 05:34:12 +09:00
"rounds": 1,
"link": true,
"type": "eq"
},
Always skip over any additional, unexpected, RSTx (restart) markers in corrupt JPEG images (issue 11794)
2020-04-12 19:27:11 +09:00
{ "id": "issue11794",
"file": "pdfs/issue11794.pdf",
"md5": "00d17b10a5fd7c06cddd7a0d2066ecdd",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Adds more SMask tests.
2016-04-11 06:39:15 +09:00
{
"id": "bug852992",
"file": "pdfs/bug852992_reduced.pdf",
"md5": "c11439fe3b7f8bc39d89dcff58c50a0c",
"rounds": 1,
"type": "eq"
},
Correct PostScript trigonometric operators PDF 32000-1:2008 7.10.5.1 "Type 4 (PostScript Calculator) Functions" defers to the PostScript Language Reference for the description of these functions. The PostScript Language Reference, third edition chapter 8 "Operators" defines the `angle` type as a "number of degrees". Section 8.1 defines "angle `sin` real", "angle `cos` real", and "num den `atan` angle". The documentation for `atan` further states that it will return an angle in degrees between 0 and 360. Handle these operators correctly in `PostScriptEvaluator.execute`. Convert the inputs to `sin` and `cos` from degrees to radians for use with `Math.sin` and `Math.cos`. Correctly pop two values from the stack for `atan`, use `Math.atan2`, and convert from radians to (positive) degrees.
2023-02-28 02:34:12 +09:00
{ "id": "colorspace_atan",
"file": "pdfs/colorspace_atan.pdf",
"md5": "ec310d65a1849a39ae57d0d16b17261d",
"rounds": 1,
"type": "eq"
},
Adds more SMask tests.
2016-04-11 06:39:15 +09:00
{
"id": "bug1199237",
"file": "pdfs/bug1199237.pdf",
"md5": "e9a63d3207ccc65a4955d5723546e962",
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Use a new method for handling soft masks. The old method of handling soft masks had a number of issues where the temporary drawing canvas and the suspended main canvas could get out of sync (e.g. mismatched save/restores or clip state) or we could end up compositing at the wrong time. A good example of things getting out sync is the reduced test case in #9017. To fix this I've changed two big things: 1) Duplicate all the needed graphics state from the temporary canvas to the suspended main canvas. This ensure the canvases stay in sync so that when we switch back to the main canvas the graphics state stack is the same (e.g. transforms, clip paths). 2) Immediately composite after each drawing operation. This ensures that if there's an active clip region that we'll still be able to composite the correct portions of the canvas. Note: This solution could be avoided by using getImageData and putImageData since those ignore clipping region, but this is very very slow. Note2: I also think the old way of only compositing at the end of the soft mask is incorrect and can lead to wrong colors if drawing over the same region, but in practice this doesn't seem to matter much. Fixes: #5781 Fixes: #5853 Fixes: #7267 Fixes: #7891 Fixes: #8403 Fixes: #8624 Fixes: #12798 Fixes: #13891 Fixes: #9017 (reduced test case) Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1703683
2021-10-20 12:14:48 +09:00
{ "id": "issue7891_bc0",
"file": "pdfs/issue7891_bc0.pdf",
"md5": "744a22244a4e4708b7f1691eec155fc8",
"rounds": 1,
"type": "eq"
},
Ignore invalid /Encoding-entries when parsing fonts (issue 14821) In the referenced PDF document the fonts have /Encoding-entries that are Streams (containing completely bogus data), which are thus obviously not valid here. Hence, only when `ignoreErrors` is set, we'll now ignore these corrupt /Encoding-entries and fallback to the existing code to try and infer a usable encoding. Given that this is *clearly* a case of corrupt PDF documents, there's no guarantee that this will "fix" all such cases, however it's the best that we do here and shouldn't really be worse than ignoring an entire font.
2022-04-22 18:40:13 +09:00
{ "id": "issue14821",
"file": "pdfs/issue14821.pdf",
"md5": "ae77afb0f98c62e6b7fe7f912c84a75c",
"rounds": 1,
"type": "eq"
},
Adds more SMask tests.
2016-04-11 06:39:15 +09:00
{
"id": "issue6165",
"file": "pdfs/issue6165.pdf",
"md5": "84ebde43b9121aa2ef8026388a4f4244",
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Test case from #6019.
2015-11-04 00:03:08 +09:00
{
"id": "issue6019-text",
"file": "pdfs/issue6019.pdf",
"md5": "7a2e5dda3b0fc5c2e9060e378a8cdc4e",
"rounds": 1,
"type": "text"
},
Try to skip mapping of missing TrueType glyphs Also don't skip mapping of glyphs which are empty, if the corresponding charCode is included in toUnicode.
2015-02-07 08:13:41 +09:00
{ "id": "bug893730",
"file": "pdfs/bug893730.pdf",
"md5": "2587379fb1b3bbff89c14f0863e78383",
"rounds": 1,
"link": false,
"type": "eq"
},
Adjust which TrueType (3, 1) glyphs we attempt to skip mapping of (issue 6336) Fixes 6336.
2015-08-09 19:31:05 +09:00
{ "id": "issue6336",
"file": "pdfs/issue6336.pdf",
"md5": "1c457c12b3606e1de610235d6768bd78",
"rounds": 1,
"link": false,
"type": "eq"
},
Normalize blend mode names.
2017-04-11 03:58:02 +09:00
{ "id": "issue6652",
"file": "pdfs/issue6652.pdf",
"md5": "1c8e2953f84623bc773eb720c87a9331",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a reduced test-case for issue 5801
2015-03-07 19:39:10 +09:00
{ "id": "issue5801",
"file": "pdfs/issue5801.pdf",
"md5": "e9548650ad40e13e00d2a486bbc2bb1b",
"rounds": 1,
"link": false,
"type": "eq"
},
Correctly detect more cases of non-embedded Arial Black fonts (issue 7835) This patch adds support for non-embedded Arial Black fonts, that use a `Arial-Black...` format for the font names. Also, this patch changes `canvas.js` such that we always render Arial Black fonts with the maximum weight, which actually improves a number of existing test-cases. This should thus explain the test "failures", which are clear improvements compared with e.g. Adobe Reader. Fixes 7835.
2016-11-22 21:48:06 +09:00
{ "id": "issue7835",
"file": "pdfs/issue7835.pdf",
"md5": "afb3206a83ee3fd19f3dea0480f942ec",
"rounds": 1,
"link": false,
"type": "eq"
},
Apply char spacing only when there are chars.
2015-05-10 18:28:15 +09:00
{ "id": "issue5972",
"file": "pdfs/issue5972.pdf",
"md5": "51f03e1d38410b04c9dda7e75fe8a0a3",
"rounds": 1,
"link": false,
"type": "text"
},
Add and fix pdfkit_compressed.pdf
2012-03-02 12:23:36 +09:00
{ "id": "pdfkit_compressed",
"file": "pdfs/pdfkit_compressed.pdf",
"md5": "ffe9c571d0a1572e234253e6c7cdee6c",
"rounds": 1,
"type": "eq"
},
Normalize the `BBox` entry in Tiling Pattern dictionaries (issue 8117) According to the PDF specification, see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G7.3982967, the `BBox` entry should have the form `[left, bottom, right, top]`. Since some PDF generators apparently violates the specification, we normalize the `BBox` to ensure that the pattern is (correctly) rendered. Fixes 8117.
2017-03-17 05:41:13 +09:00
{ "id": "issue8117",
"file": "pdfs/issue8117.pdf",
"md5": "0c805ae480dd523148a16fe7ed0fc867",
"rounds": 1,
"link": true,
"type": "eq"
},
Ensure that `PartialEvaluator_extractWidths` is able to handle indirect objects in all kinds of "width" data (issue 7855) Fixes 7855.
2016-11-30 02:28:32 +09:00
{ "id": "issue7855",
"file": "pdfs/issue7855.pdf",
"md5": "290d4d5da041ffbcb1ea5d3b0ed8ee91",
"rounds": 1,
"link": false,
"type": "eq"
},
Map missing glyphs to the notdef glyph for TrueType (3, 1) fonts (issue 6068) Fixes 6068. The most notable issue with the font in question is that the `differences` array contains lots of strange entries (of the type `uniXXXX`, instead of proper glyph names).
2015-06-07 01:00:14 +09:00
{ "id": "issue6068",
"file": "pdfs/issue6068.pdf",
"md5": "bbcedb94776b40352729c16940a5b2bd",
"rounds": 1,
"link": false,
"type": "eq"
},
Map missing glyphs to the `notdef` glyph for TrueType (3, 1) fonts regardless if the 'post' table is defined or not (issue 6889)
2016-01-18 06:03:21 +09:00
{ "id": "issue6889",
"file": "pdfs/issue6889.pdf",
"md5": "397fa92da1a8bfa83dc8c20287854d15",
"rounds": 1,
"link": false,
"type": "eq"
},
Add 'Indexed' cs abbreviation
2012-03-18 07:35:04 +09:00
{ "id": "tamreview",
"file": "pdfs/TAMReview.pdf",
"md5": "8039aba56790d3597d2bc8c794a51301",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 5,
Add 'Indexed' cs abbreviation
2012-03-18 07:35:04 +09:00
"type": "eq"
},
Use FDSelect and FDArray when converting CFF CID font to paths
2018-04-10 22:44:42 +09:00
{ "id": "text_clip_cff_cid",
"file": "pdfs/text_clip_cff_cid.pdf",
"md5": "92d4920586f177cc0e83326e5b5d2ee1",
"rounds": 1,
"type": "eq"
},
Pass the `ignoreErrors` API option to the `FontFaceObject` constructor, and utilize it in `getPathGenerator` to ignore missing glyphs Obviously it's still not possible to render non-embedded fonts as paths, but in this way the rest of the page will at least be allowed to continue rendering. *Please note:* Including the 14 standard fonts in PDF.js probably wouldn't be *that* difficult to implement. (I'm not a lawyer, but the fonts from PDFium could probably be used given their BSD license.) However, the main blocker ought to be the total size of the necessary font data, since I cannot imagine people being OK with shipping ~5 MB of (additional) font data with Firefox. (Based on the reactions when the CMap files were added, and those are only ~1 MB in size.)
2018-06-13 18:02:06 +09:00
{ "id": "issue4244",
"file": "pdfs/issue4244.pdf",
"md5": "26845274a32a537182ced1fd693a38b2",
"rounds": 1,
"link": true,
"type": "eq"
},
Support Type1 font files with incomplete /CharStrings definitions (issue 14462) Please refer to https://www.pdfa.org/norm-refs/Type1Fonts.pdf#page=15 for the expected format for the /CharStrings entries. In the referenced PDF document the /CharStrings are missing the expected end-token, which causes us to swallow the start of the next glyph name.
2022-01-18 02:53:03 +09:00
{ "id": "issue14462",
"file": "pdfs/issue14462_reduced.pdf",
"md5": "afe38169322f8e124eaeae00f94ea596",
"rounds": 1,
"type": "eq"
},
Checking if it's a true symbolic truetype font
2012-03-26 06:30:44 +09:00
{ "id": "preistabelle",
"file": "pdfs/preistabelle.pdf",
"md5": "d2f0b2086160d4f3d325c79a5dc1fb4d",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Checking if it's a true symbolic truetype font
2012-03-26 06:30:44 +09:00
"link": true,
"type": "eq"
},
Add a default DA for textfield to avoid issues when printing or saving * it aims to fix issue #12750
2020-12-18 21:17:23 +09:00
{ "id": "issue12750",
"file": "pdfs/issue12750.pdf",
"md5": "47a39ef5d6ae2e4f52887c477cfdfc9e",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"12R": {
"value": "foobar"
}
}
},
Add a couple more, mostly `text`, reference tests for non-embedded symbolic fonts without included encoding information I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones. Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts. To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases. However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly. Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite. Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-10 20:10:15 +09:00
{ "id": "preistabelle-text",
"file": "pdfs/preistabelle.pdf",
"md5": "d2f0b2086160d4f3d325c79a5dc1fb4d",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "text"
},
Pass commonObjs to TilingPattern constructor Broken example: http://www.eiken.or.jp/eiken/apply/private/flow/pdf/ichiji.pdf
2013-03-03 21:36:44 +09:00
{ "id": "ichiji",
"file": "pdfs/ichiji.pdf",
"md5": "66b645802d33513cd598886e017392b8",
"rounds": 1,
"link": true,
"type": "eq"
},
Add test file for string font name.
2012-03-20 01:09:42 +09:00
{ "id": "issue1350",
"file": "pdfs/issue1350.pdf",
"md5": "92f72a04a4d9d05b2dd433b51f32ab1f",
"rounds": 1,
"type": "eq"
},
Adjusts heuristic for disabling Symbol encoding
2014-01-03 09:44:11 +09:00
{ "id": "bug864847",
"file": "pdfs/bug864847.pdf",
"md5": "2b62cbba5d40a769be8e611eb5b61bfe",
"rounds": 1,
"type": "eq"
},
Add a couple more, mostly `text`, reference tests for non-embedded symbolic fonts without included encoding information I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones. Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts. To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases. However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly. Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite. Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-10 20:10:15 +09:00
{ "id": "bug864847-text",
"file": "pdfs/bug864847.pdf",
"md5": "2b62cbba5d40a769be8e611eb5b61bfe",
"rounds": 1,
"lastPage": 1,
"type": "text"
},
Fix bad chars in Type2CFF font names.
2012-02-20 15:12:22 +09:00
{ "id": "issue925",
"file": "pdfs/issue925.pdf",
"md5": "f58fe943090aff89dcc8e771bc0db4c2",
"rounds": 1,
"type": "eq"
},
Add a fallback for non-embedded LucidaSans-Demi fonts (issue 9291) The PDF file in the issue uses a number of *embedded* versions of Lucida fonts, but for some reason does *not* embed the LucidaSans-Demi font. According to https://en.wikipedia.org/wiki/Lucida#Usages that one should be bold, so we can at least improve rendering here (even though it won't look perfect). Fixes 9291.
2017-12-25 01:25:43 +09:00
{ "id": "issue9291",
"file": "pdfs/issue9291.pdf",
"md5": "8c3f4edff54c1ca0b67700a05ea0ccee",
"rounds": 1,
"link": false,
"type": "eq"
},
Guess CIDFontType0 subtype based on font file contents (issue 5751)
2015-02-24 00:01:08 +09:00
{ "id": "issue5751",
"file": "pdfs/issue5751.pdf",
"md5": "9334a52dc85747f1e3422767e0cd3ee9",
"rounds": 1,
"link": false,
"type": "eq"
},
Don't map glyphs to the Lepcha Unicode block (issue 7426) In the PDF file in the issue, some of the glyphs end up being mapped to the Lepcha Unicode block; see https://en.wikipedia.org/wiki/Lepcha_(Unicode_block). This didn't use to matter, but after HarfBuzz updates that improved support for Lepcha fonts, in particular https://bugzilla.mozilla.org/show_bug.cgi?id=1249861, some glyphs are now moved horizontally. To avoid that, this patch adds the Lepcha block to the list of Unicode ranges that we skip when building the glyph mapping. Fixes 7426.
2016-07-17 23:41:53 +09:00
{ "id": "issue7426",
"file": "pdfs/issue7426.pdf",
"md5": "304e6cae18fdc07f66bd621fbe16b6cb",
"link": false,
"rounds": 1,
"type": "eq"
},
Check that CIDFontType0 fonts does not actually contain OpenType font files (issue 6782) *This patch follows a similar idea as PR 5756.* The patch is based on the nice debugging done by Brendan in the referenced issue 6782. A better way to handle this, and similar issues, would probably be to completely ignore what the PDF file claims about font type/subtype, and just check the actual data. But until that kind of rewrite happens, this patch should help. Fixes 6782.
2016-01-06 10:07:21 +09:00
{ "id": "issue6782",
"file": "pdfs/issue6782.pdf",
"md5": "b423f709600daa5745cc6d8234f7c608",
"rounds": 1,
"link": false,
"type": "eq"
Check that Type1C fonts does not actually contain OpenType font files (issue 7598) This patch is yet another instalment in the (never ending) series of patches for PDF files that specify completely incorrect Type/Subtype for its fonts. In this case Type1/Type1C, when in fact OpenType would have been correct. Fixes 7598.
2016-09-06 16:56:18 +09:00
},
Adjust the heuristics used when dealing with rectangles, i.e. `re` operators, with zero width/height (issue 12010)
2020-06-30 19:18:06 +09:00
{ "id": "issue12010",
"file": "pdfs/issue12010_reduced.pdf",
"md5": "8894ec63069dcf92c9f56baec05c0425",
"rounds": 1,
"type": "eq"
},
Ensure that all necessary /Font resources are included when saving a `WidgetAnnotation`-instance (issue 12294) This patch contains a possible approach for fixing issue 12294, which compared to other PRs is purposely limited to the affected `WidgetAnnotation` code. As mentioned elsewhere, considering that we're (at least for now) trying to fix *one specific* case, I think that we should avoid modifying the `Dict` primitive[1] and/or avoid a solution that (indirectly) modifies an existing `Dict`-instance[2]. This patch simply fixes the issue at hand, since that seems easiest for now, and I'd suggest that we worry about a more general approach if/when that actually becomes necessary. Hence the solution implemented here, for `WidgetAnnotation`, is to simply use a combination of the local *and* AcroForm /DR resources during OperatorList-parsing to ensure that things work correctly regardless of where a particular /Font resource is found. For saving of form-data, on the other hand, we want to avoid increasing the file-size unnecessarily and need to be smarter than just merging all of the available resources. To achive this, a new `WidgetAnnotation._getSaveFieldResources` method will when necessary produce a combined resources `Dict` with only the minimum amount of data from the AcroForm /DR resources included. --- [1] You want to avoid anything that could cause the general `Dict` implementation to become slower, or more complex, just for handling an edge-case in my opinion. [2] If an existing `Dict`-instance is modified unexpectedly, that could very easily lead to problems elsewhere since e.g. `Dict`-instances created during parsing are not expected to be changed.
2020-09-10 17:21:34 +09:00
{ "id": "issue12294-print",
"file": "pdfs/issue12294.pdf",
"md5": "a0ac5e03be38b5fb7a7a615e30024b28",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"2795R": {
"value": "氏 名 又 は 名 称 Full name"
}
Ensure that all necessary /Font resources are included when saving a `WidgetAnnotation`-instance (issue 12294) This patch contains a possible approach for fixing issue 12294, which compared to other PRs is purposely limited to the affected `WidgetAnnotation` code. As mentioned elsewhere, considering that we're (at least for now) trying to fix *one specific* case, I think that we should avoid modifying the `Dict` primitive[1] and/or avoid a solution that (indirectly) modifies an existing `Dict`-instance[2]. This patch simply fixes the issue at hand, since that seems easiest for now, and I'd suggest that we worry about a more general approach if/when that actually becomes necessary. Hence the solution implemented here, for `WidgetAnnotation`, is to simply use a combination of the local *and* AcroForm /DR resources during OperatorList-parsing to ensure that things work correctly regardless of where a particular /Font resource is found. For saving of form-data, on the other hand, we want to avoid increasing the file-size unnecessarily and need to be smarter than just merging all of the available resources. To achive this, a new `WidgetAnnotation._getSaveFieldResources` method will when necessary produce a combined resources `Dict` with only the minimum amount of data from the AcroForm /DR resources included. --- [1] You want to avoid anything that could cause the general `Dict` implementation to become slower, or more complex, just for handling an edge-case in my opinion. [2] If an existing `Dict`-instance is modified unexpectedly, that could very easily lead to problems elsewhere since e.g. `Dict`-instances created during parsing are not expected to be changed.
2020-09-10 17:21:34 +09:00
}
},
Check that Type1C fonts does not actually contain OpenType font files (issue 7598) This patch is yet another instalment in the (never ending) series of patches for PDF files that specify completely incorrect Type/Subtype for its fonts. In this case Type1/Type1C, when in fact OpenType would have been correct. Fixes 7598.
2016-09-06 16:56:18 +09:00
{ "id": "issue7598",
"file": "pdfs/issue7598.pdf",
"md5": "c5bc5a779bfcb4b234f853231b56cf60",
"rounds": 1,
"link": false,
"type": "eq"
Check that CIDFontType0 fonts does not actually contain OpenType font files (issue 6782) *This patch follows a similar idea as PR 5756.* The patch is based on the nice debugging done by Brendan in the referenced issue 6782. A better way to handle this, and similar issues, would probably be to completely ignore what the PDF file claims about font type/subtype, and just check the actual data. But until that kind of rewrite happens, this patch should help. Fixes 6782.
2016-01-06 10:07:21 +09:00
},
Fallback to attempt to recover standard glyph names when amending the `charCodeToGlyphId` with entries from the `differences` array in `type1FontGlyphMapping` (issue 7439) Fixes 7439.
2016-06-25 19:41:26 +09:00
{ "id": "issue7439",
"file": "pdfs/issue7439.pdf",
"md5": "56682657990a894c66db26560d3039d7",
"rounds": 1,
"link": false,
"type": "eq"
},
Fixes missing compressed object detection
2013-06-22 08:02:58 +09:00
{ "id": "bug867484",
"file": "pdfs/bug867484.pdf",
"md5": "347af7b0ef7279b1a7f43b03bfda4548",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "load"
},
Workaround for some bad Type1 data
2013-10-31 23:10:08 +09:00
{ "id": "bug860632",
"file": "pdfs/bug860632.pdf",
"md5": "b3cabf9249c8fee76f61f6b3b7fdd5fd",
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Fix the `charCodeOf` method in `IdentityToUnicodeMap` in order to prevent text selection from breaking After PR 6590, `font.spaceWidth` is now called in more cases than before (in `PartialEvaluator_getTextContent`), which exposed an underlying issue with `IdentityToUnicodeMap_charCodeOf` throwing an error. This breaks text-selection in some PDF files found in the wild, hence this patch replaces the `error` with an actual function instead (modelled after `IdentityCMap_charCodeOf`).
2015-12-05 20:22:09 +09:00
{ "id": "IdentityToUnicodeMap_charCodeOf",
"file": "pdfs/IdentityToUnicodeMap_charCodeOf.pdf",
"md5": "da030686418c5e37d889127a05dafb83",
"rounds": 1,
"link": false,
"type": "text"
},
Add different code-paths to `{CMap, ToUnicodeMap}.charCodeOf` depending on length, since `Array.prototype.indexOf` can be extremely inefficient for very large arrays (issue 8372) Fixes 8372.
2017-05-25 00:36:39 +09:00
{ "id": "issue8372-text",
"file": "pdfs/issue8372.pdf",
"md5": "b02fb07364dd00ad5044bd259860da97",
"rounds": 1,
"link": false,
"type": "text"
},
Map all glyphs to the private use area and duplicate the first glyph. There have been lots of problems with trying to map glyphs to their unicode values. It's more reliable to just use the private use areas so the browser's font renderer doesn't mess with the glyphs. Using the private use area for all glyphs did highlight other issues that this patch also had to fix: * small private use area - Previously, only the BMP private use area was used which can't map many glyphs. Now, the (much bigger) PUP 16 area can also be used. * glyph zero not shown - Browsers will not use the glyph from a font if it is glyph id = 0. This issue was less prevalent when we mapped to unicode values since the fallback font would be used. However, when using the private use area, the glyph would not be drawn at all. This is illustrated in one of the current test cases (issue #8234) where there's an "ä" glyph at position zero. The PDF looked like it rendered correctly, but it was actually not using the glyph from the font. To properly show the first glyph it is always duplicated and appended to the glyphs and the maps are adjusted. * supplementary characters - The private use area PUP 16 is 4 bytes, so String.fromCodePoint must be used where we previously used String.fromCharCode. This is actually an issue that should have been fixed regardless of this patch. * charset - Freetype fails to load fonts when the charset size doesn't match number of glyphs in the font. We now write out a fake charset with the correct length. This also brought up the issue that glyphs with seac/endchar should only ever write a standard charset, but we now write a custom one. To get around this the seac analysis is permanently enabled so those glyphs are instead always drawn as two glyphs.
2018-01-05 07:43:07 +09:00
{ "id": "issue9278",
"file": "pdfs/issue9278.pdf",
"md5": "9819c3a5715c1a46ea5a6740f9ead3da",
"rounds": 1,
"type": "eq"
},
Only skip the |!isSymbolicFont| check for TrueType (3, 1) cmap tables if no previous cmap table was found (PR 5703 followup) Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=894572.
2015-02-19 21:58:03 +09:00
{ "id": "bug894572",
"file": "pdfs/bug894572.pdf",
"md5": "e54a6b0451939f685ed37e3d46e16158",
"rounds": 1,
"link": false,
"type": "eq"
},
Don't map glyphs to Unicode "Dotted circle" combining mark (bug 1108301) It seems that `0x25CC` is another bad spot for charCodes. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1108301.
2015-02-07 05:58:01 +09:00
{ "id": "bug1108301",
"file": "pdfs/bug1108301.pdf",
"md5": "cc94cc7e5f5e281dfa7e21020dd90cc7",
"rounds": 1,
"link": false,
"type": "eq"
},
Add a reduced load test-case for bug 1020858 Re: PR 4907 and https://bugzilla.mozilla.org/show_bug.cgi?id=1020858. *Note:* Since this is a `load` test, `makeref` won't be necessary.
2015-10-05 06:47:03 +09:00
{ "id": "bug1020858",
"file": "pdfs/bug1020858.pdf",
"md5": "cde53bcf75df14ff59c8a5a96fe437b9",
"rounds": 1,
"link": false,
"type": "load"
},
Handle the Encoding being a dictionary in PartialEvaluator_preEvaluateFont (bug 1157493) *This is a regression from PR 4423.* Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1157493.
2015-04-25 20:27:10 +09:00
{ "id": "bug1157493",
"file": "pdfs/bug1157493.pdf",
"md5": "df96eddacf186c28a91e699800180c4f",
"rounds": 1,
"link": false,
"type": "eq"
},
Take the `FirstChar`/`LastChar` properties into account when computing the hash in `PartialEvaluator.preEvaluateFont` (issue 10665) Without this some fonts may incorrectly end up with matching `hash`es, thus breaking rendering since we'll not actually try to load/parse some of the fonts.
2019-03-27 08:25:34 +09:00
{ "id": "issue10665",
"file": "pdfs/issue10665_reduced.pdf",
"md5": "4c8938c808153f6b3840e8a5eb68b804",
"rounds": 1,
"link": false,
"type": "eq"
},
Ensure that `MurmurHash3_64.update` handles `ArrayBuffer` input correctly, to avoid hash-collisions (issue 12533) Different fonts incorrectly end up with *identical* hashes, despite having different /ToUnicode data. The issue, and it's very interesting that we've apparently not seen it before, appears to be caused by the fact that different /ToUnicode entries share the *same* underlying `ArrayBuffer`, which thus becomes problematic at the `const dataUint32 = new Uint32Array(data.buffer, 0, blockCounts);` line. The simplest solution thus seem to be to just *copy* the input, when it's an `ArrayBuffer`, rather than using it as-is. (Note that if we'd stringified the input, when calling `MurmurHash3_64.update`, the issue would also have been fixed. In this case, we're already creating an unique TypedArray.)
2020-10-27 00:20:55 +09:00
{ "id": "issue12533",
"file": "pdfs/issue12533.pdf",
"md5": "9824904320f884eee20d4e4573008e6f",
"rounds": 1,
"link": true,
"firstPage": 17,
"lastPage": 18,
"type": "eq"
},
Improving invalid operations syntax recovery (#1466) (see also #589)
2012-04-05 01:50:20 +09:00
{ "id": "issue1466",
"file": "pdfs/issue1466.pdf",
"md5": "8a8877432e5bb10cfd50d60488d947bb",
"rounds": 1,
"link": true,
"type": "eq"
},
Add a (linked) test case for bug 1064894 This should have been part of PR 5284.
2014-12-06 22:12:37 +09:00
{ "id": "bug1064894",
"file": "pdfs/bug1064894.pdf",
"md5": "22971b6a24912bca9c773379c10ef18a",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Add a reduced test case for PR 5286
2014-10-09 04:11:41 +09:00
{ "id": "bug1065245",
"file": "pdfs/bug1065245.pdf",
"md5": "844b3af0a1d338a2e1bbe742f474bbb7",
"rounds": 1,
"link": false,
"type": "eq",
"about": "Inline JPEG images."
},
Don't read past the EOI marker for JPEG images with non-default restart interval (issue 7828) *After browsing through (a version of) the JPEG specification, see https://www.w3.org/Graphics/JPEG/itu-t81.pdf, I hope that this patch makes sense.* Note that while issue 7828 became a problem after PR 7661, it isn't really a regression from than PR. The explanation is rather that we're now relying on `core/jpg.js` instead of the Native Image decoder in more situations than before, which thus exposed an *existing* issue in our JPEG decoder. Another factor also seems to be that in many JPEG images, the DRI (Define Restart Interval) marker isn't present, in which case this bug won't manifest either. According to https://www.w3.org/Graphics/JPEG/itu-t81.pdf#page=89 (at the bottom of the page): "NOTE – The final restart interval may be smaller than the size specified by the DRI marker segment, as it includes only the number of MCUs remaining in the scan." Furthermore, according to https://www.w3.org/Graphics/JPEG/itu-t81.pdf#page=39 (in the middle of the page): "[...] If restart is enabled and the restart interval is defined to be Ri, each entropy-coded segment except the last one shall contain Ri MCUs. The last one shall contain whatever number of MCUs completes the scan." Based on the above, it thus seem to me that we should simply ensure that we're not attempting to continue to parse Scan data once we've found all MCUs (Minimum Coded Unit) of the image. Fixes 7828.
2017-03-16 00:36:28 +09:00
{ "id": "issue7828",
"file": "pdfs/issue7828.pdf",
"md5": "462f96c877f5761fc3176156e3526184",
"rounds": 1,
"link": true,
"type": "eq"
},
Fuzzy-match the fontName, for TrueType Collection fonts, where the "name"-table is wrong (issue 13193) The fontName, as defined in the PDF document, cannot be found in *any* of the "name"-tables in the TrueType Collection font. To work-around that, this patch adds a *fallback* code-path to allow using an approximately matching fontName rather than outright failing.
2021-04-07 21:06:22 +09:00
{ "id": "issue13193",
"file": "pdfs/issue13193.pdf",
"md5": "38cf058f58b7dc5dc54e1602580936a7",
"rounds": 1,
"type": "eq"
},
Prevent breaking errors when an optional content group is undefined (issue 13851) In the referenced PDF document *most* of the form `/Form` XObjects don't have an `/OC` entry, which thus causes the runtime failure during rendering.
2021-08-03 22:50:25 +09:00
{ "id": "issue13851",
"file": "pdfs/issue13851.pdf",
"md5": "d933d397c4efc80faba856bf8deafc1a",
"rounds": 1,
"link": true,
"type": "eq"
},
Treat all content as visible when no optional content groups are defined (issue 13971) In the referenced PDF document the /Contents stream contains MarkedContent-operators, however no optional content dictionary exists; according to [the specification](https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G7.3883825): > Null values or references to deleted objects shall be ignored. If this entry is not present, is an empty array, or contains references only to null or deleted objects, the membership dictionary shall have no effect on the visibility of any content.
2021-09-04 14:56:04 +09:00
{ "id": "issue13971",
"file": "pdfs/issue13971.pdf",
"md5": "50fbf6b9f26ea0e4427f33bae62a4d77",
"rounds": 1,
"link": true,
Prevent breaking errors when an optional content group is undefined (issue 13851) In the referenced PDF document *most* of the form `/Form` XObjects don't have an `/OC` entry, which thus causes the runtime failure during rendering.
2021-08-03 22:50:25 +09:00
"type": "eq"
},
Fixes bias calculation for type2 subr
2012-08-12 10:10:31 +09:00
{ "id": "issue1655",
Replace the unavailable linked test-case for issue 1655 with a reduced test-case Re: issue 1655 and PR 1978.
2015-11-15 23:32:11 +09:00
"file": "pdfs/issue1655r.pdf",
"md5": "569f48449ba57c15c4f9ade151a651c5",
"rounds": 1,
"link": false,
"type": "eq"
Fixes bias calculation for type2 subr
2012-08-12 10:10:31 +09:00
},
Fixes text clipping
2012-10-13 12:33:56 +09:00
{ "id": "issue1687",
"file": "pdfs/issue1687.pdf",
"md5": "ea79d83821d1dd0663414b037080add5",
"rounds": 1,
"link": true,
"type": "eq"
},
Lab color space, closes #1133
2012-02-02 07:48:44 +09:00
{ "id": "issue1133",
"file": "pdfs/issue1133.pdf",
"md5": "d1b61580cb100e3df93d33703af1773a",
"rounds": 1,
"link": true,
"type": "eq"
Merge remote-tracking branch 'mozilla/master' into issue1133 Conflicts: src/util.js test/test_manifest.json
2012-02-07 09:11:52 +09:00
},
Copy decoded image data and keeps non-decoded pixes as transparent
2012-08-21 05:57:21 +09:00
{ "id": "issue1658",
"file": "pdfs/issue1658.pdf",
"md5": "b71a0f641e83ad427b8bcfc180899a05",
"rounds": 1,
Replace a couple of `skipPages` annotations with `firstPage` in `test/test_manifest.json` Originally only `skipPages` existed, but given that `firstPage`/`lastPage` has existed for a long time now using them whenever possible looks simpler overall.
2019-10-17 20:15:59 +09:00
"firstPage": 10,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 10,
Copy decoded image data and keeps non-decoded pixes as transparent
2012-08-21 05:57:21 +09:00
"link": true,
"type": "eq"
},
setFont() supports negative size, closes #1049
2012-01-21 08:41:01 +09:00
{ "id": "issue1049",
"file": "pdfs/issue1049.pdf",
"md5": "15473fffcdde9fb8f3756a4cf1aab347",
"rounds": 1,
"link": true,
"type": "eq"
Adding regression test
2012-02-15 04:55:39 +09:00
},
Clear the |getSinglePixelWidth| cache when rendering Type3 fonts (issue 6117) Fixes 6117.
2015-06-16 19:47:50 +09:00
{ "id": "issue6117",
"file": "pdfs/issue6117.pdf",
"md5": "691f5f8268e07f3831e8293258a68da7",
"rounds": 1,
"link": true,
"firstPage": 6,
"lastPage": 6,
"type": "eq"
},
Check if the `Decode` entry is non-default when deciding if JPEG images are natively supported/decodable (issue 6238) Tentatively fixes 6238.
2015-07-21 06:30:05 +09:00
{ "id": "issue6238",
"file": "pdfs/issue6238.pdf",
"md5": "6d7731ee22fbbdf746c8da01b8922d50",
"rounds": 1,
"link": true,
"firstPage": 3,
"lastPage": 3,
"type": "eq"
},
Add back cid cff font test.
2013-03-14 04:06:09 +09:00
{ "id": "cid_cff",
"file": "pdfs/cid_cff.pdf",
"md5": "a19a18eaa626262cc45e0760004d6de9",
"rounds": 1,
"type": "eq"
},
Adding regression test
2012-02-15 04:55:39 +09:00
{ "id": "issue1155",
Replace the linked test-case for issue 1155 with a reduced one As part of the link cleanup in issue 6854, obtaining this file through the Internet Archive didn't work. However, given that the file was added in order to test an issue with `CropBox/MediaBox`, a reduced test-case should do just fine instead. Please refer to issue 1155, and PR 1212.
2016-01-16 23:51:10 +09:00
"file": "pdfs/issue1155r.pdf",
"md5": "8d772a3c6109bda860b8d80d42d4c08c",
Adding regression test
2012-02-15 04:55:39 +09:00
"rounds": 1,
Replace the linked test-case for issue 1155 with a reduced one As part of the link cleanup in issue 6854, obtaining this file through the Internet Archive didn't work. However, given that the file was added in order to test an issue with `CropBox/MediaBox`, a reduced test-case should do just fine instead. Please refer to issue 1155, and PR 1212.
2016-01-16 23:51:10 +09:00
"link": false,
Adding regression test
2012-02-15 04:55:39 +09:00
"type": "eq"
Sets proper unicode range for symbols; sanitize no-glyphs fonts
2012-02-19 06:01:53 +09:00
},
Support borders for link annotations
2013-03-26 18:41:56 +09:00
{ "id": "link-annotation-border",
"file": "pdfs/link-annotation-border.pdf",
Adds missing link-annotation-border file and lint error
2013-05-29 07:31:54 +09:00
"md5": "a0550889b010df9fabe4e2107662c8c4",
Support borders for link annotations
2013-03-26 18:41:56 +09:00
"rounds": 1,
"lastPage": 1,
"link": true,
Implement annotation layer regression testing
2015-12-19 06:29:22 +09:00
"type": "eq",
"annotations": true
Support borders for link annotations
2013-03-26 18:41:56 +09:00
},
Let non-viewable Popup Annotations inherit the parent's Annotation Flags if the parent is viewable Fixes http://www.pdf-archive.com/2013/09/30/file2/file2.pdf. Note how it's not possible to show the various Popup Annotations in the above document. To fix that, this patch lets the Popup inherit the flags of the parent, in the special case where the parent is `viewable` *and* the Popup is not. In general, I don't think that a Popup must have the same flags set as the parent. However, it seems very strange to have a `viewable` parent annotation, and then not being able to view the Popup. Annoyingly the PDF specification doesn't, as far as I can find, mention anything about how this case should be handled, but this patch seem consistent with the actual behaviour in Adobe Reader.
2016-05-25 00:35:45 +09:00
{ "id": "pr7352",
"file": "pdfs/pr7352.pdf",
"md5": "336abca4b313cb215b0569883f1f683d",
"link": false,
"rounds": 1,
"type": "eq",
"annotations": true
},
fix for lines (stroke) are rendered too thick (Bug 1743245) This commit fixes Bug 1743245 (Grided PDF file lines rendered too thick) which was created by a fix for #12868 . The lineWidth was set to round(1 * this._combinedScaleFactor) when the pixel is drawn as a parallelorgam with a height <1. This fix changes this to floor(1*this._combinedScaleFactor) . This change shows a visual result comparable to Chrome and Acrobat. Regarding the last PR 3 statements in canvas.js are affected and will change with this commit (stroke and paintChar). renaming the reference files to naming comvention
2022-01-25 08:26:45 +09:00
{ "id": "bug1743245",
"file": "pdfs/bug1743245.pdf",
"md5": "01eadf118ec05fe02e91db63536d50f6",
"rounds": 1,
"type": "eq"
},
CFF Parser and Compiler.
2012-03-11 12:12:33 +09:00
{ "id": "issue1002",
"file": "pdfs/issue1002.pdf",
"md5": "af62d6cd95079322d4af18edd960d15c",
"rounds": 1,
"link": false,
"type": "eq"
},
Implement Decode entry in Indexed images
2019-01-23 02:59:36 +09:00
{ "id": "issue10339",
"file": "pdfs/issue10339_reduced.pdf",
"md5": "e34ef74f188080f8194c7d8e8b68c562",
"rounds": 1,
"type": "eq"
},
Adjust heuristic to properly handle unicode characters
2012-05-22 12:15:09 +09:00
{ "id": "issue1721",
"file": "pdfs/issue1721.pdf",
"md5": "b47177f9e5197a76ec498733ecab60e6",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Adjust heuristic to properly handle unicode characters
2012-05-22 12:15:09 +09:00
"link": true,
"type": "eq"
},
Implement Huffman coding in JBIG2
2018-01-24 00:04:07 +09:00
{ "id": "jbig2_huffman_1",
"file": "pdfs/jbig2_huffman_1.pdf",
"md5": "93ccd85c5686bea27d3e6c3b41921b21",
"lastPage": 1,
"rounds": 1,
"link": true,
"type": "eq"
},
{ "id": "jbig2_huffman_2",
"file": "pdfs/jbig2_huffman_2.pdf",
"md5": "f019e2722bd64684e2093a0933e390f4",
"firstPage": 7,
"lastPage": 7,
"rounds": 1,
"link": true,
"type": "eq"
},
Use CMap in Type0 fonts when CFF is not a CID font
2019-03-27 02:38:44 +09:00
{ "id": "issue9534_reduced",
"file": "pdfs/issue9534_reduced.pdf",
"md5": "f9a47805555de5bc0f9f5f5188df6bad",
"rounds": 1,
"type": "eq"
},
Suppresses useless for PDF rendering font tables
2012-10-14 01:41:44 +09:00
{ "id": "issue1233",
"file": "pdfs/issue1233.pdf",
"md5": "2d3565b0a286e29955796c37c66326c1",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 1,
Suppresses useless for PDF rendering font tables
2012-10-14 01:41:44 +09:00
"link": true,
"type": "eq"
},
Sets proper unicode range for symbols; sanitize no-glyphs fonts
2012-02-19 06:01:53 +09:00
{ "id": "issue1243",
"file": "pdfs/issue1243.pdf",
"md5": "130c849b83513d5ac5e03c6421fc7489",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Sets proper unicode range for symbols; sanitize no-glyphs fonts
2012-02-19 06:01:53 +09:00
"link": true,
"type": "eq"
Moving all symbolic font glyphs into 0xF000 - 0xF0FF range
2012-02-21 08:19:12 +09:00
},
Fix loading of PDF files with invalid or missing Type3 characters (issue 5039)
2014-07-24 21:59:21 +09:00
{ "id": "issue5039",
"file": "pdfs/issue5039.pdf",
"md5": "5c131f458ee6b65cc096ccaf0474ee3a",
"link": false,
"rounds": 1,
"type": "eq"
},
Adjust the heuristics to recognize more cases of unknown glyphs for |toUnicode| (issue 5070)
2014-07-29 01:41:47 +09:00
{ "id": "issue5070",
"file": "pdfs/issue5070.pdf",
"md5": "ec2ca0b4954c8390a5b3b0ffd79a8e92",
"link": false,
"rounds": 1,
"type": "eq"
},
Moving all symbolic font glyphs into 0xF000 - 0xF0FF range
2012-02-21 08:19:12 +09:00
{ "id": "issue1257",
"file": "pdfs/issue1257.pdf",
"md5": "9111533826bc21ed774e8e01603a2f54",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Moving all symbolic font glyphs into 0xF000 - 0xF0FF range
2012-02-21 08:19:12 +09:00
"link": true,
"type": "eq"
Add tests from #1309 and #1317
2012-03-18 13:13:54 +09:00
},
{ "id": "issue1309",
"file": "pdfs/issue1309.pdf",
"md5": "e835fb7f3dab3073ad37d0bd3c6399fa",
"rounds": 1,
"link": true,
"type": "eq"
},
apply transformation matrix to RadialGradient radiuses, not only to circle origin points fix for #6006
2015-11-16 08:26:42 +09:00
{
"id": "issue6006",
"file": "pdfs/issue6006.pdf",
"md5": "65558dcdd2f20d4372458419c10bfa72",
"rounds": 1,
"type": "eq"
},
jbig2 ref test
2012-06-22 19:59:53 +09:00
{ "id": "issue1810",
"file": "pdfs/issue1810.pdf",
"md5": "b173a9dfb7bf00e1a298c6e8cb95c03e",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 3,
jbig2 ref test
2012-06-22 19:59:53 +09:00
"link": true,
"type": "eq"
},
Simplify the handling of unsupported/incorrect markers in `src/core/jpg.js` - Re-factor the "incorrect encoding" check, since this can be easily achieved using the general `findNextFileMarker` helper function (with a suitable `startPos` argument). - Tweak a condition, to make it easier to see that the end of the data has been reached. - Add a reference test for issue 1877, since it's what prompted the "incorrect encoding" check.
2020-01-13 21:32:23 +09:00
{ "id": "issue1877",
"file": "pdfs/issue1877.pdf",
"md5": "feac01f414f2e6792e4d3174944622f5",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Subtract the X/Y offsets when decoding refinement regions of JBIG2 images (issue 7145, 7308, 7401, 7850, 8270) Please refer to the JBIG2 standard, see https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.88-200002-I!!PDF-E&type=items. In particular, section "6.3.5.3 Fixed templates and adaptive templates" mentions that the offsets should be *subtracted*; where the offsets are defined according to "Table 6" under section "6.3.2 Input parameters". Fixes 7145. Fixes 7308. Fixes 7401. Fixes 7850. Fixes 8270.
2017-04-26 22:47:59 +09:00
{ "id": "issue7308",
"file": "pdfs/issue7308.pdf",
"md5": "ba2e23d3af93ac2c634d77ccbe2e79d5",
"rounds": 1,
"link": true,
"type": "eq"
},
Improve handling of JPEG images without an EOI marker (issue 12841) Given that the PDF document in the issue contains the same very large JPEG image *three* times, this patch includes a test-case where only the first page has been extracted from it.
2021-01-10 04:07:08 +09:00
{ "id": "issue12841",
"file": "pdfs/issue12841_reduced.pdf",
"md5": "5c645897c652853ad86b59df5fc6cce0",
"rounds": 1,
"type": "eq"
},
Add ref test
2012-04-24 07:50:02 +09:00
{ "id": "issue1597",
"file": "pdfs/issue1597.pdf",
"md5": "a5ebef467fd6e2fc0aeb56c9eb725ae3",
"rounds": 1,
"link": true,
"type": "eq"
},
Add reftest for undefined colorspace.
2012-07-20 02:58:07 +09:00
{ "id": "issue1419.pdf",
"file": "pdfs/issue1419.pdf",
"md5": "b5b6c6405d7b48418bccf97277957664",
"rounds": 1,
"link": true,
Replace a couple of `skipPages` annotations with `firstPage` in `test/test_manifest.json` Originally only `skipPages` existed, but given that `firstPage`/`lastPage` has existed for a long time now using them whenever possible looks simpler overall.
2019-10-17 20:15:59 +09:00
"firstPage": 2,
Fix typo in `test_manifest.json` that prevents test-case `issue1419.pdf` from running Currently we only attempt to test the *first* page, since `lastPage == 1`, but given that it's subsequently skipped we end up not testing anything. *Note:* I've verified that the *second* page actually contains the kind of Colour space that the test was intended to check for.
2015-08-28 23:05:34 +09:00
"lastPage": 2,
Add reftest for undefined colorspace.
2012-07-20 02:58:07 +09:00
"type": "eq"
},
Add tests from #1309 and #1317
2012-03-18 13:13:54 +09:00
{ "id": "issue1317",
"file": "pdfs/issue1317.pdf",
"md5": "6fb46275b30c48c8985617d4f86199e3",
"rounds": 1,
"link": true,
"type": "eq"
Fix gradients for fill and stroke.
2012-03-30 00:53:51 +09:00
},
Only take the fast-path in `PDFImage_createImageData` for un-masked JPEG images with "standard" colour spaces (issue 6364) Fixes 6364.
2015-08-19 05:25:37 +09:00
{ "id": "issue6364",
"file": "pdfs/issue6364.pdf",
"md5": "b290328531ecdddf6b4c794b4b2fec28",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Fix text spacing with vertical fonts (#6387) According to the PDF spec 5.3.2, a positive value means in horizontal, that the next glyph is further to the left (so narrower), and in vertical that it is further down (so wider). This change fixes the way PDF.js has interpreted the value.
2015-08-28 20:42:01 +09:00
{ "id": "issue6387-canvas",
"file": "pdfs/issue6387.pdf",
"md5": "08c39ac6d0aab1596e6e59793eaf3ee4",
"rounds": 1,
"type": "eq"
},
{ "id": "issue6387-text",
"file": "pdfs/issue6387.pdf",
"md5": "08c39ac6d0aab1596e6e59793eaf3ee4",
"rounds": 1,
"type": "text",
"about": "Note that the text layer seems to be off to the right."
},
Repair CFF fonts if stem hints are in wrong order
2018-11-21 01:50:37 +09:00
{ "id": "issue10084",
"file": "pdfs/issue10084_reduced.pdf",
"md5": "ae37cf36f2e319688c608e4086836824",
"rounds": 1,
"type": "eq"
Support corrupt PDF files with invalid/non-existent Group /CS entries (issue 11045) The PDF file in question tries to reference a non-existent ColorSpace, which should be quite rare in practice.
2019-08-05 21:40:48 +09:00
},
Handle non-integer Annotation border widths correctly (issue 14203) The existing code appears to be wrong, since according to the PDF specification the border width of an Annotation only has to be a number and not specifically an integer. Please see: - https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#page=392 - https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G11.2096210 - https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G6.1965562
2021-12-24 22:10:19 +09:00
{ "id": "issue14203",
"file": "pdfs/issue14203.pdf",
"md5": "26c1c1e7341bc23fb28d805fa516dbbe",
"link": true,
"rounds": 1,
"firstPage": 11,
"lastPage": 11,
"type": "eq"
},
Support corrupt PDF files with invalid/non-existent Group /CS entries (issue 11045) The PDF file in question tries to reference a non-existent ColorSpace, which should be quite rare in practice.
2019-08-05 21:40:48 +09:00
{ "id": "issue11045",
"file": "pdfs/issue11045.pdf",
"md5": "101d4cb649cc006e0f2b14923e8d97d6",
"rounds": 1,
"link": false,
"type": "eq"
Repair CFF fonts if stem hints are in wrong order
2018-11-21 01:50:37 +09:00
},
Improve glyph mapping for non-embedded composite standard fonts (issue 11088) For non-embedded CIDFontType2 fonts with a non-/Identity encoding, use the /ToUnicode data to improve the glyph mapping.
2021-09-08 21:46:39 +09:00
{ "id": "issue11088",
"file": "pdfs/issue11088.pdf",
"md5": "c46e7d81197fae61a52e00efb30dd7ce",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Allow skipping of errors when parsing broken/unsupported ColorSpaces (issue 6707, issue 11287) This will allow us to attempt to recover as much as possible of a page, rather than immediately failing, when a broken/unsupported ColorSpace is encountered. This patch thus extends the framework added in PRs such as e.g. 8240 and 8922, to also cover parsing of ColorSpaces.
2019-10-31 23:53:51 +09:00
{ "id": "issue11287",
"file": "pdfs/issue11287.pdf",
"md5": "d7d6a7c124fad7b00f79112b71ee09d6",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
[FIX] fix jpx tag tree decode (issue 11957)
2021-08-31 12:44:26 +09:00
{ "id": "issue12579",
"file": "pdfs/issue12579.pdf",
"md5": "a56f6c7b6ebe0008bd6215b9a4dc3cca",
"link": true,
"firstPage": 3,
"lastPage": 3,
"rounds": 1,
"type": "eq"
},
Subtract `stream.start` when getting the `startXRef` property for documents with a Linearization dictionary (issue 11330) For documents with a Linearization dictionary the computed `startXRef` position will be relative to the raw file, rather than the actual PDF document itself (which begins with `%PDF-`). Hence it's necessary to subtract `stream.start` in this case, since otherwise the `XRef.readXRef` method will increment the position too far resulting in parsing errors.
2019-11-16 10:07:02 +09:00
{ "id": "issue11330",
"file": "pdfs/issue11330.pdf",
"md5": "03a8a53d4b0dc825e08554f5c0178308",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Ignore spaces when normalizing the font name in `Font.fallbackToSystemFont` (issue 11578)
2020-02-09 03:51:16 +09:00
{ "id": "issue11578",
"file": "pdfs/issue11578_reduced.pdf",
"md5": "6cefb4bdfae2fa25e5585374735e321f",
"rounds": 1,
"link": false,
"type": "eq"
},
Prevent lookup errors in `PartialEvaluator.hasBlendModes` from breaking all parsing/rendering of a page (issue 11678) The PDF document in question is *corrupt*, since it contains an XObject with a truncated dictionary and where the stream contents start without a "stream" operator.
2020-03-09 19:37:33 +09:00
{ "id": "issue11678",
"file": "pdfs/issue11678.pdf",
"md5": "e2efadeb91932f4c21e4fc682cce7de9",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq"
},
Add a linked test-case for issue 4890
2015-08-19 05:33:09 +09:00
{ "id": "issue4890",
"file": "pdfs/issue4890.pdf",
"md5": "1666feb4cd26318c2bdbea6a175dce87",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Read multi-byte character codes based on codespace ranges.
2013-09-26 02:32:04 +09:00
{ "id": "bug898853.pdf",
"file": "pdfs/bug898853.pdf",
"md5": "37c37702bf98d33f9f74e2380c4d1a3f",
"rounds": 1,
"type": "eq",
"about": "Has a multi-byte char codes."
},
[TrueType] Recover from a missing "glyf" table by replacing it with dummy data, utilizing the existing code in `sanitizeGlyphLocations` It seems to be fairly common for OCR software to include incomplete TrueType fonts, notable missing the "glyf" table, in PDF files. Since we currently reject such fonts, the result is that text-selection/copying is broken. This patch contains a suggested approach to try and use these kind of broken fonts, by using existing code in `sanitizeGlyphLocations` to replace a missing "glyf" table with dummy data. Fixes 4684. Fixes 6007. Fixes 6829.
2016-01-09 19:50:48 +09:00
{ "id": "issue4684-text",
"file": "pdfs/issue4684.pdf",
"md5": "af5056fcdfb08bd7adc1710d36e4b5b5",
"link": false,
"rounds": 1,
"type": "text",
"about": "Invisible (and broken) TrueType font used for text-selection."
},
Attempt to detect inline images which contain "EI" sequence in the actual image data (issue 11124) This should reduce the possibility of accidentally truncating some inline images, while *not* causing the "EI" detection to become significantly slower.[1] There's obviously a possibility that these added checks are not sufficient to catch *every* single case of "EI" sequences within the actual inline image data, but without specific test-cases I decided against over-engineering the solution here. *Please note:* The interpolation issues are somewhat orthogonal to the main issue here, which is the truncated image, and it's already tracked elsewhere. --- [1] I've looked at the issue a few times, and this is the first approach that I was able to come up with that didn't cause *unacceptable* performance regressions in e.g. issue 2618.
2020-06-26 19:36:28 +09:00
{ "id": "issue11124",
"file": "pdfs/issue11124.pdf",
"md5": "9bde831515dc6b8bb2c7c00c8189aca9",
"rounds": 1,
"type": "eq"
},
A couple of small `String.fromCodePoint` improvements (PR 11698 and 11769 follow-up) - Add a reduced test-case for issue 11768, to prevent future regressions. (Given that PR 11769 is only a work-around, rather than a proper solution, it may not be entirely accurate for the issue to be closed as fixed.) - Add more validation of the charCode, as found by the heuristics, in `PartialEvaluator._buildSimpleFontToUnicode` to prevent future issues.
2020-04-15 20:34:13 +09:00
{ "id": "issue11768",
"file": "pdfs/issue11768_reduced.pdf",
"md5": "0cafde97d78bb6883531a325a996a5ef",
"rounds": 1,
"type": "eq"
},
Fixes reading CFF with two .notdef in charset
2012-10-14 05:35:23 +09:00
{ "id": "issue1912",
"file": "pdfs/issue1912.pdf",
"md5": "15305b7c2cba971e7423de3f6ad38fef",
"rounds": 1,
"link": true,
"type": "eq"
},
Fix gradients for fill and stroke.
2012-03-30 00:53:51 +09:00
{ "id": "gradientfill",
"file": "pdfs/gradientfill.pdf",
"md5": "cbc1988e4803f647fa83467a85f0e231",
"rounds": 1,
"type": "eq"
Added new test pdf to manifest
2012-06-14 02:29:02 +09:00
},
{ "id": "issue1796",
"file": "pdfs/issue1796.pdf",
"md5": "9b9b60dc2a4cc3ea05932785d71304fe",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Added new test pdf to manifest
2012-06-14 02:29:02 +09:00
"link": true,
"type": "eq"
Add support for type 1 seac charstring command.
2012-07-12 08:29:07 +09:00
},
Recognizes ascii type1 encoding
2014-04-17 21:52:33 +09:00
{ "id": "issue4630",
"file": "pdfs/issue4630.pdf",
"md5": "46690a12b953c9ad660f3f6453f8785c",
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 5734
2015-02-14 19:59:10 +09:00
{ "id": "issue5734-text",
"file": "pdfs/issue5734.pdf",
"md5": "2cf88f1786b039ba080623085c87beb9",
"link": false,
"rounds": 1,
"type": "text"
},
Add a reduced test-case for issue 5896 This should have been part of PR 5898.
2015-05-14 21:08:43 +09:00
{ "id": "issue5896-text",
"file": "pdfs/issue5896.pdf",
"md5": "08f69084d72dabc5dfdcf5c1ff2a719f",
"link": false,
"rounds": 1,
"type": "text"
},
Add support for Optional Content in TilingPatterns (issue 15716) This can't be a particularly common feature, since we've supported Optional Content for over two years and this is the very first TilingPattern-case we've seen.
2022-11-23 20:58:00 +09:00
{ "id": "issue15716",
"file": "pdfs/issue15716.pdf",
"md5": "4d89aabeb97fcb181662406f092bbeb0",
"rounds": 1,
"type": "eq"
},
{ "id": "issue15716-no-red-oc",
"file": "pdfs/issue15716.pdf",
"md5": "4d89aabeb97fcb181662406f092bbeb0",
"rounds": 1,
"type": "eq",
"optionalContent": {
"1001R": false
}
},
Adds callothersubr support
2012-08-12 01:57:42 +09:00
{ "id": "issue845",
Replace the unavailable linked test-case for issue 845 with a reduced test-case Re: issue 845 and PR 1977.
2015-11-17 07:38:23 +09:00
"file": "pdfs/issue845r.pdf",
"md5": "b5f8fe4005cf3fb685fdb4a4c44ee4a2",
"rounds": 1,
"link": false,
"type": "eq"
Adds callothersubr support
2012-08-12 01:57:42 +09:00
},
Stops objects indexing at the end
2013-08-24 02:57:11 +09:00
{ "id": "helloworld-bad",
"file": "pdfs/helloworld-bad.pdf",
"md5": "bf5ab1cf7fe3a502c3754f55e6ceeabd",
"rounds": 1,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"type": "eq"
Stops objects indexing at the end
2013-08-24 02:57:11 +09:00
},
Resets canvas 2d context to the default state.
2017-05-24 00:57:26 +09:00
{ "id": "issue8047",
"file": "pdfs/issue8047.pdf",
"md5": "83f1b9f7e95caa8e2625390afd7c7276",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Fix bad truetype loca tables. Some fonts have loca tables that aren't sorted or use 0 as an offset to signal a missing glyph. This fixes the bad loca tables by sorting them and then rewriting the loca table and potentially re-ordering the glyf table to match. Fixes #11131 and bug 1650302.
2020-08-08 05:04:53 +09:00
{ "id": "issue11131_reduced",
"file": "pdfs/issue11131_reduced.pdf",
"md5": "004b7e7d2b133a8dc4fe64aaf3dc9533",
"rounds": 1,
"type": "eq"
},
Add support for type 1 seac charstring command.
2012-07-12 08:29:07 +09:00
{ "id": "issue818",
"file": "pdfs/issue818.pdf",
"md5": "dd2f8a5bd65164ad74da2b45a6ca90cc",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 1,
Add support for type 1 seac charstring command.
2012-07-12 08:29:07 +09:00
"link": true,
"type": "eq"
Sanitize the document info.
2012-08-04 08:11:43 +09:00
},
Avoiding 'pc is undefined' failures
2013-10-31 00:54:19 +09:00
{ "id": "issue3405",
Replace the unavailable linked test-case for issue 3405 with a reduced test-case Re: issue 3405 and PR 3861.
2015-11-17 01:03:59 +09:00
"file": "pdfs/issue3405r.pdf",
"md5": "12e8c6b3437e659f9138d892d10c7d3d",
"rounds": 1,
"link": false,
"type": "eq"
Avoiding 'pc is undefined' failures
2013-10-31 00:54:19 +09:00
},
Attempt to also cache images at the "page"-level (issue 16263) Currently we have two separate image-caches on the worker-thread: - A local one, which is unique to each `PartialEvaluator.getOperatorList` invocation. This one caches both names *and* references, since image-resources may be accessed in either way. - A global one, which applies to the entire PDF documents and all its pages. This one only caches references, since nothing else would work. This patch introduces a third image-cache, which essentially sits "between" the two existing ones. The new `RegionalImageCache`[1] will be usable throughout a `PartialEvaluator` instance, and consequently it *only* caches references, which thus allows us to keep track of repeated image-resources found in e.g. different /Form and /SMask objects. --- [1] For lack of a better word, since naming things is hard...
2023-04-10 18:00:35 +09:00
{ "id": "issue16263",
"file": "pdfs/issue16263.pdf",
"md5": "93c3e7884f1f2d072442898127e0a6fd",
"rounds": 1,
"type": "eq"
},
Fixes function array support for radial/axial pattern
2012-11-25 06:13:13 +09:00
{ "id": "issue2006",
"file": "pdfs/issue2006.pdf",
"md5": "71ec73831ece9b508ad20efa6ff28642",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 1,
Fixes function array support for radial/axial pattern
2012-11-25 06:13:13 +09:00
"link": true,
"type": "eq"
},
Sanitize the document info.
2012-08-04 08:11:43 +09:00
{ "id": "issue1729",
"file": "pdfs/issue1729.pdf",
"md5": "29b0eddc3e1dcb23a44384037032d470",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 1,
Sanitize the document info.
2012-08-04 08:11:43 +09:00
"link": true,
"type": "load"
Stop streams from being sent from worker for indexed color spaces.
2012-08-17 07:22:28 +09:00
},
{ "id": "issue1985",
"file": "pdfs/issue1985.pdf",
"md5": "2ac7c68e26a8ef797aead15e4875cc6d",
"rounds": 1,
"type": "load"
Adds support for color key mask.
2012-08-29 09:19:31 +09:00
},
Fix loca table when offsets aren't in ascending order.
2017-12-14 09:10:14 +09:00
{ "id": "issue7074_reduced",
"file": "pdfs/issue7074_reduced.pdf",
"md5": "46893f8aa33620a05acdc27e3b79469d",
"rounds": 1,
"type": "eq"
},
Adds more characters to the PUA range
2015-07-03 06:47:47 +09:00
{ "id": "issue5540",
"file": "pdfs/issue5540.pdf",
"md5": "12b69b19e366232422812ad8b2534f37",
"rounds": 1,
"type": "eq"
},
Fix cff private dictionary key.
2012-12-15 05:44:39 +09:00
{ "id": "issue2176",
"file": "pdfs/issue2176.pdf",
"md5": "ca5cbbc7e2b717997f0b24ffa485eac6",
"rounds": 1,
"type": "eq"
},
Add support for hmoveto and vmoveto during flex.
2012-12-21 04:14:10 +09:00
{ "id": "issue1453",
"file": "pdfs/issue1453.pdf",
"md5": "cee0ee8ea3a0643cbd716d57fd44f628",
"rounds": 1,
"type": "eq"
},
Fix pattern-filled text
2017-11-29 02:40:22 +09:00
{ "id": "pattern_text_embedded_font",
"file": "pdfs/pattern_text_embedded_font.pdf",
"md5": "763b1b9efaecb2b5aefea71c39233f56",
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 6113 As promised in PR 6125, here's a reduced test-case that should (hopefully) avoid the intermittent failure of the previous one.
2015-08-30 08:23:52 +09:00
{ "id": "issue6113",
"file": "pdfs/issue6113.pdf",
"md5": "365fa2d369c51ee3ff195dae907b6e25",
"rounds": 1,
"link": false,
"type": "eq"
},
TilingPattern: Reverse transform after painting This transform resulted in an incorrectly positioned object when the bounding box's upper-left corner did not start at (0,0), because the translation was not reverted. This patch adds the missing transform. The test file (tiling-pattern-box.pdf) is based on the PDF from #2825. All but the first cube (including the PDF data) have been removed. To trigger the bug that is fixed by this commit, I changed the BBox of the first pattern from "[ 0 0 596 842]" to "[90 0 596 842]". Without this patch, the dashed vertical line that intersects the corners at A and E would disappear.
2015-11-07 23:02:37 +09:00
{
"id": "tiling-pattern-box",
"file": "pdfs/tiling-pattern-box.pdf",
"md5": "09100872824fc14012bd8f9bf4dbc632",
"rounds": 1,
"link": false,
"type": "eq"
},
Avoid extreme sizing / scaling in tiling pattern The new test file (tiling-pattern-large-steps.pdf) was manually created, to have the following characteristics: - Large xstep and ystep (90000) - Page width is 4000 (which is larger than MAX_PATTERN_SIZE) - Visually, the page consists of a red rectangle with a black border, surrounded by a 50 unit white padding. - Before patch: blurry; After patch: sharp Fixes #6496 Fixes #5698 Fixes #1434 Fixes #2825
2015-10-04 00:02:19 +09:00
{
"id": "tiling-pattern-large-steps",
"file": "pdfs/tiling-pattern-large-steps.pdf",
"md5": "569aac1303c97004aab6a720d9b259b4",
"rounds": 1,
"link": false,
"type": "eq"
},
XFA subform with occur min=0 and no bound data displaying Subfrom nomin displays even though it's subform is set to <occur max=-1 min=0> If we look through specs of XFA 3.3 : https://www.pdfa.org/norm-refs/XFA-3_3.pdf - The min attribute is used when processing a form that contains data. Regardless of the data at least this number of instances is included. It is permissible to set this value to zero, in which case the container is entirely excluded if there is no data for it. However, in our case it doesn't happen, because we let our empty dataNode get through. Though by setting a clause: - eliminate unmatched data with occur min=0 we are checking our empty data and sending it to uselessNode array where at the end it gets removed;
2021-11-02 14:35:08 +09:00
{ "id": "issue14130",
"file": "pdfs/issue14130.pdf",
"md5": "82e7efb0a10122e793fc64348d93dc4e",
"enableXfa": true,
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 6151 Re: issue 6151 and PR 6193. *Note:* Since this is a `load` test, `makeref` won't be necessary.
2015-10-24 01:20:57 +09:00
{ "id": "issue6151",
"file": "pdfs/issue6151.pdf",
"md5": "926f8c6b25e6f0978759f7947d70e079",
"rounds": 1,
"link": false,
"type": "load"
},
Fix bad truetype loca tables. Some fonts have loca tables that aren't sorted or use 0 as an offset to signal a missing glyph. This fixes the bad loca tables by sorting them and then rewriting the loca table and potentially re-ordering the glyf table to match. Fixes #11131 and bug 1650302.
2020-08-08 05:04:53 +09:00
{ "id": "bug1650302_reduced",
"file": "pdfs/bug1650302_reduced.pdf",
"md5": "d918c9ec936486e8b6656e10dd909014",
"rounds": 1,
"type": "eq"
},
Tweak how fonts with an /Encoding are handled in `adjustToUnicode` (issue 14048, PR 13277 follow-up) Currently we only exclude /Encoding entries that also contains a /Differences array, which is the cause of the text-selection problem in the referenced issue. In order to address this we'll now also exclude /Encoding entries that contain one of the predefined *named* encodings, and no longer require that it also contains a /Differences array. *Please note:* This patch cases a small "regression" in the `bug1130815-text` test-case, however this is actually an improvement when compared with Adobe Reader and PDFium (in Google Chrome).
2021-09-19 05:28:23 +09:00
{ "id": "issue14048",
"file": "pdfs/issue14048.pdf",
"md5": "770026875a93dc44a187905f4dcd3de2",
"rounds": 1,
"type": "text"
},
Add support for blend modes.
2013-03-12 02:23:47 +09:00
{ "id": "blendmode",
"file": "pdfs/blendmode.pdf",
Update MD5 for blendmode.pdf
2013-04-03 00:23:25 +09:00
"md5": "5a86e7e9333e93c58abc3f382e1e6ea2",
Add support for blend modes.
2013-03-12 02:23:47 +09:00
"rounds": 1,
"type": "eq",
"about": "Every blend mode that PDF supports."
},
Add basic support for transparency groups.
2013-03-13 09:20:38 +09:00
{ "id": "transparency_group",
"file": "pdfs/transparency_group.pdf",
"md5": "10391f76434128e5da70cff5fc485ff0",
"rounds": 1,
"type": "eq",
"about": "Rotated transparency group with blend mode."
},
Convert UTF8 encoded passwords to ISO-8859-1 for |R = 6| encryption (issue 6010) For passwords where the encoding already is correct, the conversion is a no-op. Also, since `encodeURIComponent` might throw, we need to make sure that we handle that case too. Fixes 6010.
2015-05-14 00:25:42 +09:00
{ "id": "issue6010_1",
"file": "pdfs/issue6010_1.pdf",
"md5": "b58adce5dbb08936ddb0d904f0da8716",
"rounds": 1,
"link": false,
"type": "load",
"password": "abc"
},
{ "id": "issue6010_2",
"file": "pdfs/issue6010_2.pdf",
"md5": "73a8091d0ab2a47af5ca45047f04da99",
"rounds": 1,
"link": false,
"type": "load",
"password": "\u00E6\u00F8\u00E5",
Cleans test manifest from absent files.
2016-01-14 00:40:21 +09:00
"about": "The password (æøå) is UTF8 encoded."
Convert UTF8 encoded passwords to ISO-8859-1 for |R = 6| encryption (issue 6010) For passwords where the encoding already is correct, the conversion is a no-op. Also, since `encodeURIComponent` might throw, we need to make sure that we handle that case too. Fixes 6010.
2015-05-14 00:25:42 +09:00
},
Add support for TrueType format 12 `cmap`s (issue 14881) This is, as far as I can tell, the first case we've seen of a format 12 `cmap`. Please see https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6cmap.html
2022-05-06 18:11:38 +09:00
{ "id": "issue14881",
"file": "pdfs/issue14881.pdf",
"md5": "1aa3f2c7929eaf4502fcf6488ff31b5f",
"rounds": 1,
"type": "eq"
},
Ensure that the `baseTransform` is always defined for TilingPatterns Fixes http://www2.emersonprocess.com/siteadmincenter/PM%20Micro%20Motion%20Documents/High-Pressure-Measurement-WP-001287.pdf#page=3.
2015-09-28 05:43:23 +09:00
{ "id": "High-Pressure-Measurement-WP-001287",
"file": "pdfs/High-Pressure-Measurement-WP-001287.pdf",
"md5": "aeba7e47bbe50cbf08bb8bdff78fec8c",
"rounds": 1,
"link": true,
"firstPage": 3,
"lastPage": 3,
"type": "eq"
},
Add an additional test-case for circular references in Type3 fonts The PDF document in this patch already worked *without* the previous patch, but I wanted to improve our test-coverage for the Type3-parsing. The attached PDF document was also found in https://github.com/pdf-association/safedocs/tree/main/Miscellaneous%20Targeted%20Test%20PDFs
2022-01-14 01:53:22 +09:00
{ "id": "ContentStreamNoCycleType3insideType3",
"file": "pdfs/ContentStreamNoCycleType3insideType3.pdf",
"md5": "fbf258be0fed9756cbc714f4be6626ff",
"rounds": 1,
"type": "eq"
},
Prevent circular references in Type3 fonts In corrupt PDF documents Type3 fonts may introduce circular dependencies, thus resulting in the affected font(s) never loading and parsing/rendering never completing. Note that I've not seen any real-world examples of this kind of font corruption, but the attached PDF document was rather found in https://github.com/pdf-association/safedocs/tree/main/Miscellaneous%20Targeted%20Test%20PDFs *Please note:* That repository contains a number of reduced test-cases that are specifically intended to test interoperability (between PDF viewer) and parsing/rendering for various kinds of strange/corrupt PDF documents. Some of the test-cases found there may thus not make sense to try and "fix" upfront, in my opinion, unless the problems are also found in real-world PDF documents.
2022-01-14 01:36:36 +09:00
{ "id": "ContentStreamCycleType3insideType3",
"file": "pdfs/ContentStreamCycleType3insideType3.pdf",
"md5": "64840fc5dd8ca06afbc86477d9121b59",
"rounds": 1,
"type": "eq"
},
Paint patterns relative to content base transformation.
2013-07-23 06:52:44 +09:00
{ "id": "issue3458.pdf",
"file": "pdfs/issue3458.pdf",
"md5": "dab8bd3ad1acfc8dc82a8381a3c8ff94",
"rounds": 1,
"type": "eq",
"about": "Pattern with current transform different than base transform."
},
Fetch parameters if they are |Ref|s in Pattern color spaces (issue 6081) Fixes 6081.
2015-06-05 04:28:14 +09:00
{ "id": "issue6081",
"file": "pdfs/issue6081.pdf",
"md5": "854326ce9178d10ff4a0ff2aedf67e45",
"rounds": 1,
"link": false,
"type": "eq"
},
Add support for hmoveto and vmoveto during flex.
2012-12-21 04:14:10 +09:00
{ "id": "issue2462",
"file": "pdfs/issue2462.pdf",
"md5": "d4e3dddfdd35464c71cf0310bff29b42",
"rounds": 1,
"type": "eq"
},
Refactors Lab CS; uses different conversion for D50 and D65; adds getRgbItem
2012-12-01 00:07:39 +09:00
{ "id": "issue1998",
"file": "pdfs/issue1998.pdf",
"md5": "586e0213be2f461360ec26770b5a4e48",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Refactors Lab CS; uses different conversion for D50 and D65; adds getRgbItem
2012-12-01 00:07:39 +09:00
"link": true,
Fix lab colorspace decoding and rgb conversion.
2013-04-04 02:36:09 +09:00
"type": "eq"
Refactors Lab CS; uses different conversion for D50 and D65; adds getRgbItem
2012-12-01 00:07:39 +09:00
},
Tests for issue 2627
2013-01-31 09:20:04 +09:00
{ "id": "issue2627",
"file": "pdfs/issue2627.pdf",
"md5": "1b6b2f19f4e1e1b926afb353b41fe6b2",
"rounds": 1,
"link": true,
"firstPage": 4,
"lastPage": 4,
"type": "load"
},
Fallback to the /ToUnicode map for TrueType fonts with (3, 1) and (1, 0) cmap-tables (issue 13316) In the PDF document some of the glyphs have bogus `differences`-entries[1] that cannot be resolved to valid glyph names, thus causing the glyph mapping to fail. My initial idea was to use a similar approach as in the `PartialEvaluator._simpleFontToUnicode`-method, to extract the charCodes from those entries, however it turned out that that didn't actually help in this case (the mapping was still wrong). To fix this I'm thus proposing that we fallback to the /ToUnicode map when no other useable data exists (e.g. no post-table), since it *hopefully* shouldn't make things any worse than leaving parts of the glyph map empty (which currently happens). --- [1] As can be seem below, some of the entries are completely normal while others are non-standard: ``` Differences (array) 0 = 65 1 = /g5167 2 = /space 3 = /g11927 4 = /g17737 5 = /g11540 6 = /g2180 7 = /K 8 = /P 9 = /two 10 = /zero 11 = /one 12 = /five 13 = /four 14 = /g6932 15 = /g7246 16 = /g1691 17 = /g2343 18 = /g14792 19 = /g3325 20 = /g4280 21 = /g20383 22 = /g18166 23 = /g16988 24 = /g17943 25 = /g19223 26 = /g10830 27 = 97 28 = /g982 29 = /g1226 30 = /g5059 31 = /g2677 32 = /g1042 33 = /g11568 34 = /L 35 = /three 36 = /seven 37 = /g2364 38 = /g12063 39 = /g5356 40 = /g2173 41 = /g17877 42 = /g7273 43 = /g7647 44 = /g7224 45 = /g19327 46 = /g5054 47 = /g2342 48 = /g10136 49 = /g6856 50 = /g13381 51 = /g7257 52 = /g12093 53 = /g2359 ```
2021-09-04 01:10:27 +09:00
{ "id": "issue13316",
"file": "pdfs/issue13316_reduced.pdf",
"md5": "f5821891cee29d8de8b65e1efd6f4ceb",
"rounds": 1,
"type": "eq"
},
Fix glyph 0 in CIDFontType2 that has a CIDToGIDMap stream
2019-05-08 00:44:37 +09:00
{ "id": "issue10519",
"file": "pdfs/issue10519_reduced.pdf",
"md5": "8a2dae43c0ef47b0734bedaaa24f8c09",
"rounds": 1,
"type": "eq"
},
The first glyph in CFF CIDFonts must be named 0 instead of ".notdef" Fixes #11718 in which the `ff` ligature glyph is at index zero in a CFF font. Beacuse this is a CIDFont, glyph names are CIDs, which are integers. Thus the string `".notdef"` is not correct. The rest of the charset data is already parsed correctly as integers when the boolean argument `cid` is true.
2020-03-24 22:33:43 +09:00
{ "id": "issue11718",
"file": "pdfs/issue11718_reduced.pdf",
"md5": "a0deea064b4171bb8ea9f6e8a523e594",
"rounds": 1,
"type": "eq"
},
Normalize CFF CID sub matrices to work on windows.
2013-04-16 08:14:07 +09:00
{ "id": "issue3061",
"file": "pdfs/issue3061.pdf",
"md5": "696a7cb1b194d095ca3f7861779a606b",
"rounds": 1,
"type": "eq",
"about": "CFF CID font with font matrices in main top dict and sub top dict."
},
Fix handling of multiply-encoded glyphs.
2013-08-23 02:12:16 +09:00
{ "id": "issue3566",
"file": "pdfs/issue3566.pdf",
"md5": "e9ab02aa769f4c040a6fa52f00d6e3f0",
"rounds": 1,
"type": "eq",
"lastPage": 1,
"about": "CFF font with multiply-encoded glyph and no pdf encoding dict."
Normalize CFF CID sub matrices to work on windows.
2013-04-16 08:14:07 +09:00
},
Add more reduced test-cases for PR 6171
2015-07-03 20:14:41 +09:00
{ "id": "bug1151216",
"file": "pdfs/bug1151216.pdf",
"md5": "e66ea6ee0e0cdd5119224eb073055eca",
"rounds": 1,
"link": false,
"type": "eq"
},
{ "id": "bug1175962",
"file": "pdfs/bug1175962.pdf",
"md5": "012a5ea0d2733408ac7f8b88f7352bba",
"rounds": 1,
"link": false,
"type": "eq",
"about": "The same PDF file as in bug1175943."
},
Don't accidentally accept invalid glyphNames which *appear* to follow the Cdd{d}/cdd{d} format in `PartialEvaluator._buildSimpleFontToUnicode` (issue 11697) The /Differences array of the problematic font contains a `/c.1` entry, which is consequently detected as a *possible* Cdd{d}/cdd{d} glyphName by the existing heuristics. Because of how the base 10 conversion is implemented, which is necessary for the base 16 special case, the parsed charCode becomes `0.1` thus causing `String.fromCodePoint` to throw since that obviously isn't a valid code point. To fix the referenced issue, and to hopefully prevent similar ones in the future, the patch adds *additional* validation of the charCode found by the heuristics.
2020-03-14 06:09:27 +09:00
{ "id": "issue11697",
"file": "pdfs/issue11697_reduced.pdf",
"md5": "5b3793a76f92b357bd8ccc02e1c54ba0",
"rounds": 1,
"link": false,
"type": "eq"
},
Fixes compressed object entries caching
2012-11-04 13:03:52 +09:00
{ "id": "issue1878",
"file": "pdfs/issue1878.pdf",
"md5": "b4fb0ce7c19368e7104dce3d0d34bcb3",
"rounds": 1,
"link": true,
"type": "load"
},
Intersect group bounding box with the current canvas dimensions.
2013-10-11 04:41:11 +09:00
{ "id": "bigboundingbox",
"file": "pdfs/bigboundingbox.pdf",
"md5": "e5c5e2cb80826d6ebf535413865270cd",
"rounds": 1,
"type": "eq",
"about": "When the bounding box for the xobject is transformed it creates a huge bounding box."
},
Fixes encoding reading in CFF fonts
2012-12-09 14:04:37 +09:00
{ "id": "issue2386",
"file": "pdfs/issue2386.pdf",
"md5": "7dc787639aa6765214e9ff5494d231ed",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 2,
Fixes encoding reading in CFF fonts
2012-12-09 14:04:37 +09:00
"link": true,
"type": "eq"
},
Evaluate type 1 charstrings for conversion to type 2.
2013-01-10 10:33:59 +09:00
{ "id": "issue1936",
"file": "pdfs/issue1936.pdf",
"md5": "7302eb9b6a626308e2a933aaed9e1756",
"rounds": 1,
Make firstPage work in test_manifest.json + rename pageLimit -> lastPage
2013-01-31 04:31:08 +09:00
"lastPage": 1,
Evaluate type 1 charstrings for conversion to type 2.
2013-01-10 10:33:59 +09:00
"link": true,
"type": "eq"
},
Enable/disable image smoothing based on image interpolate value. (bug 1722191) While some of the output looks worse to my eye, this behavior more closely matches what I see when I open the PDFs in Adobe acrobat. Fixes: #4706, #9713, #8245, #1344
2021-09-09 09:31:10 +09:00
{ "id": "issue9713",
"file": "pdfs/issue9713.pdf",
"md5": "a62bd42d12271105b26a68c8eae5ea5f",
"rounds": 1,
"type": "eq"
},
Add a couple more, mostly `text`, reference tests for non-embedded symbolic fonts without included encoding information I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones. Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts. To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases. However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly. Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite. Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-10 20:10:15 +09:00
{ "id": "issue1936-text",
"file": "pdfs/issue1936.pdf",
"md5": "7302eb9b6a626308e2a933aaed9e1756",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "text"
},
Better crypto key length recovery.
2015-12-30 06:10:38 +09:00
{ "id": "bug951051",
"file": "pdfs/bug951051.pdf",
"md5": "05d325a5112bd3f6022367dab7bc07b9",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "load"
},
Stops bleeding of pattern edges for mesh.
2016-04-12 08:21:44 +09:00
{ "id": "bug1260585",
"file": "pdfs/bug1260585.pdf",
"md5": "9415b1eb00a43c97c15328cd4c8d136a",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "load"
},
Use a new method for handling soft masks. The old method of handling soft masks had a number of issues where the temporary drawing canvas and the suspended main canvas could get out of sync (e.g. mismatched save/restores or clip state) or we could end up compositing at the wrong time. A good example of things getting out sync is the reduced test case in #9017. To fix this I've changed two big things: 1) Duplicate all the needed graphics state from the temporary canvas to the suspended main canvas. This ensure the canvases stay in sync so that when we switch back to the main canvas the graphics state stack is the same (e.g. transforms, clip paths). 2) Immediately composite after each drawing operation. This ensures that if there's an active clip region that we'll still be able to composite the correct portions of the canvas. Note: This solution could be avoided by using getImageData and putImageData since those ignore clipping region, but this is very very slow. Note2: I also think the old way of only compositing at the end of the soft mask is incorrect and can lead to wrong colors if drawing over the same region, but in practice this doesn't seem to matter much. Fixes: #5781 Fixes: #5853 Fixes: #7267 Fixes: #7891 Fixes: #8403 Fixes: #8624 Fixes: #12798 Fixes: #13891 Fixes: #9017 (reduced test case) Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1703683
2021-10-20 12:14:48 +09:00
{ "id": "issue7891_bc1",
"file": "pdfs/issue7891_bc1.pdf",
"md5": "86b1796da7dad09f93ce68a8ad495a24",
"rounds": 1,
"type": "eq"
},
Tests for OpenType fonts
2013-07-09 11:03:59 +09:00
{ "id": "issue3062",
"file": "pdfs/issue3062.pdf",
"md5": "206715f1258f0e117df4180d98dd4d68",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
{ "id": "issue2442",
"file": "pdfs/issue2442.pdf",
"md5": "4656e36c44f44c71a499f02ce6c781d3",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Fixes cmap when 0xFFFF character is included
2012-10-14 04:21:15 +09:00
{ "id": "issue2074",
"file": "pdfs/issue2074.pdf",
"md5": "5e4ba2241fc35d20e44eb52289a569ab",
"rounds": 1,
"type": "eq"
},
Adds support for color key mask.
2012-08-29 09:19:31 +09:00
{ "id": "colorkeymask",
"file": "pdfs/colorkeymask.pdf",
"md5": "9f11e815b485f7f0e1fa5c116c636cf9",
"rounds": 1,
"type": "eq"
Added a test PDF having Identity-H encoding without embedded font
2013-01-13 04:21:30 +09:00
},
Support rendering appearance streams for annotations
2013-03-14 04:24:55 +09:00
{ "id": "annotation-as",
"file": "pdfs/annotation-as.pdf",
"md5": "e51500c8adc9edcdcc8ebc6a575c90ab",
"rounds": 1,
"link": true,
"type": "eq"
},
Takes SMask's preblending in account
2013-07-03 04:27:06 +09:00
{ "id": "bug888437",
"file": "pdfs/bug888437.pdf",
"md5": "93370cd589a08732a05601441c899bcb",
"rounds": 1,
"link": true,
"type": "eq"
},
Move the creation of canvas path fonts to the worker.
2013-08-20 08:33:20 +09:00
{ "id": "issue3584",
"file": "pdfs/issue3584.pdf",
"md5": "7a00646865a840eefc76f05c588b60ce",
"rounds": 1,
"type": "eq",
"about": "CFF font that is drawn with clipping."
},
Render not displayed annotations in using normal appearance when printing
2020-09-20 00:47:38 +09:00
{ "id": "prefilled_f1040",
"file": "pdfs/prefilled_f1040.pdf",
"md5": "2335da66fb7c2c3b84971597f27785e2",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"1605R": {
"value": true
}
Render not displayed annotations in using normal appearance when printing
2020-09-20 00:47:38 +09:00
}
},
Move svg:clipPath generation from clip to endPath In the PDF from issue 8527, the clip operator (W) shows up before a path is defined. The current SVG backend however expects a path to exist before generating a `<svg:clipPath>` element. In the example, the path was defined after the clip, followed by a endPath operator (n). So this commit fixes the bug by moving the path generation logic from clip to endPath. Our canvas backend appears to use similar logic: `CanvasGraphics_endPath` calls `consumePath`, which in turn draws the clip and resets the `pendingClip` state. The canvas backend calls `consumePath` from multiple other places, so we probably need to check whether doing so is also necessary for the SVG backend. I scanned our corpus of PDF files in test/pdfs, and found that in every instance (except for one), the "W" PDF operator (clip) is immediately followed by "n" (endPath). The new test from this commit (clippath.pdf) starts with "W", followed by a path definition and then "n". # Commands used to find some of the clipping commands: grep -ra '^W$' -C7 | less -S grep -ra '^W ' -C7 | less -S grep -ra ' W$' -C7 | less -S test/pdfs/issue6413.pdf is the only file where "W" (a tline 55) is not followed by "n". In fact, the "W" is the last operation of a series of XObject painting operations, and removing it does not have any effect on the rendered PDF (confirmed by looking at the output of PDF.js's canvas backend, and ImageMagick's convert command).
2017-06-19 19:40:48 +09:00
{ "id": "clippath",
"file": "pdfs/clippath.pdf",
"md5": "7ab95c0f106dccd90d6569f241fe8771",
"rounds": 1,
"link": false,
"type": "eq",
"about": "Clipping before a path exists, followed by adding a path and then drawing a rectangle."
},
Add tx annotation test file.
2013-06-01 06:13:23 +09:00
{ "id": "annotation-tx",
"file": "pdfs/annotation-tx.pdf",
"md5": "56321ea830be9c4f8437ca17ac535b2d",
"rounds": 1,
"type": "eq",
Implement annotation layer regression testing
2015-12-19 06:29:22 +09:00
"annotations": true,
Prevent rendering `TextWidgetAnnotation`s in both the `core`/`display` layer (issue 7643)
2016-09-18 22:35:12 +09:00
"about": "Text widget annotation without appearance streams."
},
{ "id": "annotation-tx-forms",
"file": "pdfs/annotation-tx.pdf",
"md5": "56321ea830be9c4f8437ca17ac535b2d",
"rounds": 1,
"type": "eq",
"forms": true,
"about": "Text widget annotation without appearance streams."
},
{ "id": "annotation-tx2-annotations",
"file": "pdfs/annotation-tx2.pdf",
"md5": "b7a32a751895d394fc07bb6ddb40c420",
"rounds": 1,
"type": "eq",
"annotations": true
},
{ "id": "annotation-tx2-forms",
"file": "pdfs/annotation-tx2.pdf",
"md5": "b7a32a751895d394fc07bb6ddb40c420",
"rounds": 1,
"type": "eq",
"forms": true
},
{ "id": "annotation-tx3-annotations",
"file": "pdfs/annotation-tx3.pdf",
"md5": "3aec45c6465ca4959c25df17c4356a1c",
"rounds": 1,
"type": "eq",
"annotations": true
},
{ "id": "annotation-tx3-forms",
"file": "pdfs/annotation-tx3.pdf",
"md5": "3aec45c6465ca4959c25df17c4356a1c",
"rounds": 1,
"type": "eq",
"forms": true
Add tx annotation test file.
2013-06-01 06:13:23 +09:00
},
Render PopupAnnotations even if they have missing or empty /Rect-entries (issue 15012, PR 14439 follow-up) This only applies to *corrupt* PDF documents, where Annotations are missing the required /Rect-entry. Rendering PopupAnnotations unconditionally shouldn't be a problem, since we're not using a `BaseSVGFactory`-instance in that case.
2022-06-09 21:06:51 +09:00
{ "id": "issue15012",
"file": "pdfs/issue15012.pdf",
"md5": "cc5e89507262cb3ec6862f68cb3eefd1",
"rounds": 1,
"type": "eq",
"annotations": true
},
Extend `getGlyphMapForStandardFonts` with some Hebrew entries (issue 15033) This only adds the minimum entries required in order to render the referenced document correctly, rather than trying to support "all" Hebrew glyphs, to ensure that all lines in `getGlyphMapForStandardFonts` are covered by tests.
2022-06-13 16:48:40 +09:00
{ "id": "issue15033",
"file": "pdfs/issue15033.pdf",
"md5": "4454c98b88d37d5dad779b60a3f35e6e",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Add basic support for non-embedded ArialUnicodeMS fonts (issue 15044) This appears to be a Microsoft-specific version of the regular Arial font, hence we simply map this to Helvetica in the same way that we treat many other Arial-named fonts.
2022-06-15 17:29:24 +09:00
{ "id": "issue15044",
"file": "pdfs/issue15044.pdf",
"md5": "a1ef114e432df51f0c6cbe22c66c5c2e",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Ignore invalid /CIDToGIDMap-entries when parsing fonts (issue 15139) In the referenced PDF document the fonts have /CIDToGIDMap-entries that cannot be loaded. Hence, only when `ignoreErrors` is set, we'll now ignore these corrupt /CIDToGIDMap-entries and fallback to simply assume that no such data is available. Given that this is *clearly* a case of a corrupt PDF document, there's no guarantee that this will "fix" things in the general case since a /CIDToGIDMap may be *required* in order for some composite fonts to render correctly. However, attempting to render *something* is surely better than skipping a font altogether.
2022-07-13 17:06:16 +09:00
{ "id": "issue15139",
"file": "pdfs/issue15139.pdf",
"md5": "0f2beb6a788d1e47bb9af737f6670493",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Refactor 'cmap' generation
2013-03-19 21:37:31 +09:00
{ "id": "gesamt",
"file": "pdfs/gesamt.pdf",
Clean up test PDF references
2013-12-17 09:37:10 +09:00
"md5": "743aaa6f46ed0a42864f079d632d942e",
Refactor 'cmap' generation
2013-03-19 21:37:31 +09:00
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Convert CID fonts using "ToUnicode" CMap if available
2013-03-03 13:38:40 +09:00
{ "id": "javauninstall-7",
Replace the unavailable linked test-case for PR 2875 with a reduced test-case This reduced PDF file only contains the relevant text/font; for reference please see PR 2875.
2015-09-16 20:52:57 +09:00
"file": "pdfs/javauninstall-7r.pdf",
"md5": "c0089082a86826fa0195eeeb73f7f895",
"rounds": 1,
"link": false,
"type": "eq"
Convert CID fonts using "ToUnicode" CMap if available
2013-03-03 13:38:40 +09:00
},
Add a dummy byte at end of the CFF table to satisfy sanitizer Fixes #2674.
2013-02-23 20:46:20 +09:00
{ "id": "jst2007-5",
"file": "pdfs/JST2007-5.pdf",
"md5": "9efa6c37fc771b36a60535036d1910bb",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq"
},
Correct a typo in DeviceRgbCS_getRgbBuffer
2013-03-24 17:48:39 +09:00
{ "id": "kdchart",
"file": "pdfs/kdchart.pdf",
"md5": "2556a1d197d7cbe1f5edfc5c3557582b",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Implement "B5pc-H" CMap
2013-03-16 19:44:54 +09:00
{ "id": "mao",
"file": "pdfs/mao.pdf",
"md5": "797093d67c4d4d4231ac6e1fb66bf6c3",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Fetch binary CMap data in the worker-thread, when `useWorkerFetch` is set This patch uses the new option added in PR 12726 to *also* allow fetching binary CMap data directly in the worker-thread in browsers. Given that these changes remove the need to transfer data between threads for the default (browser) use-case, we can also revert the changes in PR 11118 since that simplifies the overall implementation.
2021-06-08 19:02:26 +09:00
{ "id": "mao-main_thread_fetch",
"file": "pdfs/mao.pdf",
"md5": "797093d67c4d4d4231ac6e1fb66bf6c3",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
"useWorkerFetch": false
},
Use a proper `MessageHandler` for `PartialEvaluator.getTextContent` to avoid errors for fonts relying on built-in CMap files (PR 8064 follow-up) *My apologies for inadvertently breaking this in PR 8064; apparently we don't have any tests that cover this use-case :(* Without this patch `getTextContent` will fail if called before `getOperatorList`, since loading of fonts during text-extraction may require fetching of built-in CMap files. *Please note:* The `text` test added here, which uses an already existing PDF file, fails without this patch.
2017-03-25 01:24:30 +09:00
{ "id": "mao-text",
"file": "pdfs/mao.pdf",
"md5": "797093d67c4d4d4231ac6e1fb66bf6c3",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "text"
},
Added a test PDF having Identity-H encoding without embedded font
2013-01-13 04:21:30 +09:00
{ "id": "noembed-identity",
"file": "pdfs/noembed-identity.pdf",
"md5": "05d3803b6c22451e18cb60d8d8c75c0c",
"rounds": 1,
"type": "eq"
Handle missing 'FontName' entry in FontDescriptor object
2013-01-12 10:10:09 +09:00
},
Removes browser decoding optimization for JPEG CMYK
2013-07-02 23:46:14 +09:00
{ "id": "bug887152",
"file": "pdfs/bug887152.pdf",
"md5": "783a3e7b1de2cf40a47ffe1f36a41d4f",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Fix several issues with radial/axial shadings and tiling patterns. Previously, we set the base transformation and pattern matrix directly to the main rendering ctx of the page, however doing this caused the current transform to be lost. This would cause issues with things like shear missing so the pattern was misaligned or when stroke was used the scale of the line width or dash would be wrong. Instead we should leave the current transform and use setTransfrom on the pattern so it is applied correctly. For axial and radial shadings I had to create a temporary canvas to draw the shading so I could in turn use setTransform. Fixes: #13325, #6769, #7847, #11018, #11597, #11473 The following already in the corpus are improved: issue8078-page1 issue1877-page1
2021-05-11 09:43:37 +09:00
{ "id": "issue11473",
"file": "pdfs/issue11473.pdf",
"md5": "c530851b0523c81784ab4ea3115a7c67",
"rounds": 1,
"type": "eq"
},
[JPEG 2000] Add support for resetContextProbabilities (bug 1731483)
2022-02-26 20:27:39 +09:00
{ "id": "jpx-resetContextProbabilities",
"file": "pdfs/jp2k-resetprob.pdf",
"md5": "fc9fb23e0a08d985b70cfb32fa9e9ca1",
"rounds": 1,
"type": "eq",
"about": "Fixes one part of bug 1731483."
},
Correctly detect the presence of the Adobe specific APP14 JPEG marker (bug 1140761) According to the specification, http://partners.adobe.com/public/developer/en/ps/sdk/5116.DCT_Filter.pdf#G3.851943, the content of the marker segment should begin with `Adobe`, and not `Adobe\x00` as the code currently look for. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1140761. Fixes the colour conversion part of issues 4090 and 5623.
2015-03-10 21:07:09 +09:00
{ "id": "bug1140761",
"file": "pdfs/bug1140761.pdf",
"md5": "b74eced7634d4f248dc6265f8225d432",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Fixes Type3 negative font direction
2014-08-19 07:57:52 +09:00
{ "id": "bug1011159",
"file": "pdfs/bug1011159.pdf",
"md5": "4532e22deb92d4cd2992d0cfe255582a",
"rounds": 1,
"lastPage": 1,
"type": "eq",
"about": "Type3 font with negative HScale and font size"
},
Fix searching for end of inline (EI) images with ASCII85Decode filters (bug 1077808) This patch changes searching for the end of inline image streams to rely on the EOD marker for the filters: ASCII85Decode and ASCIIHexDecode.
2014-10-05 07:12:47 +09:00
{ "id": "bug1077808",
"file": "pdfs/bug1077808.pdf",
"md5": "4a4bfc27e3fafe2f74e7a4a4cd04b8dc",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq",
"about": "Inline image with ASCII85Decode filter."
},
Try to recover if we reach the end of the stream when searching for the `EI` marker of an inline image (issue 8798)
2017-08-21 21:34:15 +09:00
{ "id": "issue8798",
Replace the test-case for issue 8798 with a reduced one (PR 8800 follow-up) *Re: issue 8798 and PR 8800.* Big thanks to @THausherr for providing the test-case.
2017-08-25 00:32:53 +09:00
"file": "pdfs/issue8798r.pdf",
"md5": "3a0e29f013d9edcceb5d852e37738a77",
Attempt to improve the `EI` detection heuristics, for inline images, in streams containing `NUL` bytes (issue 8823) Since this patch will now treat (some) `NUL` bytes as "ASCII", the number of `followingBytes` checked are thus increased to (hopefully) reduce the risk of introducing new false positives. Fixes 8823.
2017-08-26 19:09:49 +09:00
"link": false,
"rounds": 1,
"type": "eq"
},
{ "id": "issue8823",
"file": "pdfs/issue8823.pdf",
"md5": "ad02d4aa374b315bf1766038d002d57a",
"link": false,
Try to recover if we reach the end of the stream when searching for the `EI` marker of an inline image (issue 8798)
2017-08-21 21:34:15 +09:00
"rounds": 1,
Take the dictionary, and not just the image data, into account when caching inline images (issue 9398) The reason for the bug is that we're only computing a checksum of the image data itself, but completely ignore the inline dictionary. The latter is important, since in practice it's not uncommon for inline images to be identical but use e.g. different ColourSpaces. There's obviously a couple of different ways that we could compute a hash/checksum of the dictionary. Initially I tried using `MurmurHash3_64` to compute a hash of the keys/values in the dictionary. Unfortunately this approach turned out to be *way* too slow in practice, especially for PDF files with a huge number of inline images; in particular issue 2618 would regresses quite badly with this solution. The solution that is instead implemented in this patch, is to compute a checksum of the dictionary contents. While this is a much simpler, not to mention a lot more efficient, solution there's one drawback associated with it: If the contents of inline image dictionaries are ordered differently, they will not be considered equal with this approach which could thus lead to failures to cache repeated inline images. In practice this doesn't seem to be a problem in any of the PDF files I've tested, and generally I'd rather err on the side of *not* caching given that too aggressive caching can easily lead to rendering bugs. One small, but somewhat annoying, complication is that by the time `Parser.makeInlineImage` is called, we no longer know the *exact* stream position where the inline image dictionary starts. Having access to that information is crucial here, and the easiest solution I could come up with is to track this in the current `Lexer` instance.[1] With the patch, we're thus able to fix the referenced issues without incurring large regressions in problematic cases such as issue 2618. Fixes 9398; also improves/fixes the `issue8823` reference test. --- [1] Obviously I'd have preferred if this patch could be limited to `Parser.makeInlineImage`, without the need for this "hack", but I'm not sure what that'd look like here.
2018-01-30 20:26:33 +09:00
"type": "eq",
"about": "Also tests issue9398."
Try to recover if we reach the end of the stream when searching for the `EI` marker of an inline image (issue 8798)
2017-08-21 21:34:15 +09:00
},
Fix a stupid spelling error in the `ASCII85Decode` name in `Parser.makeInlineImage` (issue 8613) This is a trivial follow-up to PR 5383, and it's a bit strange that this has been wrong since late 2014 without anyone noticing (maybe because inline images aren't too common). So, apparently code works better if you actually spell correctly, who knew ;-) Fixes 8613.
2017-07-06 02:38:44 +09:00
{ "id": "issue8613",
"file": "pdfs/issue8613.pdf",
"md5": "bc7ad2db75710aa9916c5769e0c02123",
"rounds": 1,
"link": true,
"type": "eq"
},
Attempt to handle DNL (Define Number of Lines) markers when parsing JPEG images (issue 8614) Please refer to the specification, found at https://www.w3.org/Graphics/JPEG/itu-t81.pdf#page=49 Given how the JPEG decoder is currently implemented, we need to know the value of the scanLines parameter (among others) *before* parsing of the SOS (Start of Scan) data begins. Hence the best solution I could come up with here, is to re-parse the image in the *hopefully* rare case of JPEG images that include a DNL (Define Number of Lines) marker. Fixes 8614.
2018-02-02 04:43:01 +09:00
{ "id": "issue8614",
"file": "pdfs/issue8614.pdf",
"md5": "7e8b66cf674ac2b79d6b267d0c6f2fa2",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Add a heuristic, in `src/core/jpg.js`, to handle JPEG images with a wildly incorrect SOF (Start of Frame) `scanLines` parameter (issue 10880) *This whole patch feels somewhat arbitrary, and I'd be slightly worried about possibly breaking something else.* To limit the impact of these changes, we only re-parse JPEG images using a reduced `scanLines` value if and only if: An unexpected EOI (End of Image) marker was encountered during decoding of Scan data *and* the "actual" `scanLines` value is at least one order of magnitude smaller than expected.
2020-01-18 20:53:40 +09:00
{ "id": "issue10880",
"file": "pdfs/issue10880.pdf",
"md5": "244ee5ee3ab88db8d8eb51d4416e2c97",
"rounds": 1,
"link": true,
"firstPage": 7,
"lastPage": 7,
"type": "eq"
},
Tweak the heuristic, in `src/core/jpg.js`, that handles JPEG images with a wildly incorrect SOF (Start of Frame) `scanLines` parameter (issue 10989)
2020-07-06 20:02:41 +09:00
{ "id": "issue10989",
"file": "pdfs/issue10989.pdf",
"md5": "c16de154d9ae6dbeec0a113911957efe",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Tweak the heuristic that handles JPEG images with a wildly incorrect SOF (Start of Frame) `scanLines` parameter (issue 15492)
2022-09-22 21:04:37 +09:00
{ "id": "issue15492",
"file": "pdfs/issue15492.pdf",
"md5": "968d36ef340852a4c0e6fa22ced96798",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Prefer the Width/Height of the image data, rather than the image dictionary, for JPEG 2000 images (issue 9650) According to the PDF specification, see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=45 > When using the JPXDecode filter with image XObjects, the following changes to and constraints on some entries in the image dictionary shall apply (see 8.9.5, "Image Dictionaries" for details on these entries): > > - Width and Height shall match the corresponding width and height values in the JPEG2000 data. > > - . . . Hence it seems reasonable to use the Width/Height of the image data *itself*, rather than the image dictionary when there's a mismatch. Given that JPEG 2000 images are already being parsed, in order to obtain basic parameters, the actual Width/Height is readily available in the `PDFImage` constructor.
2018-07-16 01:53:08 +09:00
{ "id": "issue9650",
"file": "pdfs/issue9650.pdf",
"md5": "20d50bda6b1080b6d9088811299c791e",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
Ignore the rest of the image when encountering an EOI (End of Image) marker while parsing Scan data (issue 9679)
2018-05-16 21:26:12 +09:00
{ "id": "issue9679",
"file": "pdfs/issue9679.pdf",
"md5": "3077d06add3875705aa1021c7b116023",
"rounds": 1,
"link": true,
"type": "eq"
},
Handle some corrupt/truncated JPEG images that are missing the EOI (End of Image) marker (issue 11052) Note that even Adobe Reader cannot render the PDF file completely, which is always a good indication that it's corrupt.
2019-08-08 17:31:48 +09:00
{ "id": "issue11052",
"file": "pdfs/issue11052.pdf",
"md5": "67c20e5bec51183c9283baa0cd49593f",
"rounds": 1,
"link": true,
"type": "eq"
},
Add a (linked) test case for bug 1108753 (PR 5276) When submitting PR 5276 there wasn't a good PDF file to include in the test suite. However, with https://bugzilla.mozilla.org/show_bug.cgi?id=1108753, we now have a better source for a test file, hence this patch.
2014-12-09 09:07:38 +09:00
{ "id": "bug1108753",
"file": "pdfs/bug1108753.pdf",
"md5": "a7aaf92d55b4602afb0ca3d75198b56b",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Fix CCITTStream regression by byte-aligning rows before checking EOL marker
2015-02-14 05:17:27 +09:00
{ "id": "issue5726",
"file": "pdfs/issue5726.pdf",
"md5": "f52f31ad3da316b599cade875ab049db",
"rounds": 1,
"link": true,
"type": "eq"
},
Fix glyph selection for CID fonts that don't actually have CID font files.
2013-05-02 08:42:25 +09:00
{ "id": "bug816075",
"file": "pdfs/bug816075.pdf",
"md5": "7ec87c115c1f9ec41234cc7002555e82",
"rounds": 1,
"type": "eq",
"about": "A CIDFontType0 font with a CFF font that isn't actually CID."
},
XFA - Display rectangle, line and arc
2021-06-05 03:10:35 +09:00
{ "id": "xfa_imm1295e",
"file": "pdfs/xfa_imm1295e.pdf",
"md5": "b995232fda9bb7fa57856ff7f4cda046",
"rounds": 1,
"link": true,
"enableXfa": true,
"type": "eq"
},
Better approximate gradient color stops PDF gradients do not have color stops but an arbitrary PDF function of the type f(t) -> color. CSS gradients are only based on color stops. Most PDF gradient functions are produced from color stop oriented gradients. Take advantage of this by sampling the PDF function at a higher frequency but not converting any samples which could be interpolated to color stops. The sampling frequency is chosen to be the least common multiple of as many values as practical to exactly re-create the common case of the PDF function implementing equally spaced linearly interpolated stops in RGB color space. This also allows for better approximation of other smooth PDF functions (non-linear, or non-equally spaced, or in different color space). Fixes: #10572, #14165
2023-03-04 01:41:04 +09:00
{ "id": "issue14165",
"file": "pdfs/issue14165.pdf",
"md5": "917850af2a387475b34b00010200897d",
"rounds": 1,
"type": "eq"
},
Scale stroking line width when using a tiling pattern.
2019-05-24 08:47:22 +09:00
{ "id": "scorecard_reduced",
"file": "pdfs/scorecard_reduced.pdf",
"md5": "aa8ed0827092c963eea64adb718a3806",
"rounds": 1,
"type": "eq"
},
Proper glyph selection for CIDFontType0C fonts.
2013-10-01 13:40:28 +09:00
{ "id": "bug921409",
"file": "pdfs/bug921409.pdf",
"md5": "920e88dde0f5436ebe0df0281e1c30ca",
"rounds": 1,
"type": "eq",
"about": "A CIDFontType0 font that actually has a Type1C font file."
},
Fixes non-Japanese characters spacing
2013-01-24 01:15:02 +09:00
{ "id": "noembed-identity-2",
"file": "pdfs/noembed-identity-2.pdf",
Add Hankaku-Latin cid to Unicode mappings
2013-01-30 02:46:17 +09:00
"md5": "13b7d9ab9579d45c10bc8d499d087f21",
Fixes non-Japanese characters spacing
2013-01-24 01:15:02 +09:00
"rounds": 1,
"type": "eq"
},
Added tests for PDFs having 'H', 'EUC-H', and '90ms' encodings
2013-01-17 00:13:34 +09:00
{ "id": "noembed-jis7",
"file": "pdfs/noembed-jis7.pdf",
"md5": "a0f6cf5a830f23d0c35994a6aaf92b3d",
"rounds": 1,
"type": "eq"
},
{ "id": "noembed-eucjp",
"file": "pdfs/noembed-eucjp.pdf",
"md5": "d270f2d46db99b70235b4d37cbc313ad",
"rounds": 1,
"type": "eq"
},
{ "id": "noembed-sjis",
"file": "pdfs/noembed-sjis.pdf",
"md5": "51f9d150bf4afe498019b3029d451072",
"rounds": 1,
"type": "eq"
},
Convert cid to Unicode when rebuilding Type 2 CID fonts encoded with non-Identity CMap
2013-03-02 15:28:27 +09:00
{ "id": "ohkubo-ss04",
"file": "pdfs/ohkubo-SS04.pdf",
"md5": "b8c334073ff5be74fac1f36130943ea5",
"rounds": 1,
"link": true,
"type": "eq"
},
Fix where image component decoding takes place.
2013-03-15 06:06:44 +09:00
{ "id": "issue2770",
"file": "pdfs/issue2770.pdf",
"md5": "36070d756d06eaa35c2227efb069fb1b",
"rounds": 1,
"link": true,
"type": "eq",
"about": "Has a 4 bit per component image with mask and decode."
},
Cache fonts by reference.
2013-06-26 02:33:53 +09:00
{ "id": "issue2984",
"file": "pdfs/issue2984.pdf",
Clean up test PDF references
2013-12-17 09:37:10 +09:00
"md5": "a8e81e7b7c6d8b0ec26bbfee9954f110",
Cache fonts by reference.
2013-06-26 02:33:53 +09:00
"rounds": 1,
"link": true,
"type": "eq",
"lastPage": 1,
"about": "Type3 fonts with lots of switching between them."
},
Ignore malformed dictionary entries.
2013-05-01 07:29:25 +09:00
{ "id": "bug808084",
"file": "pdfs/bug808084.pdf",
"md5": "b1c400de699af29ea3f1983bb26870ab",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "load"
},
Fix priority of which font encoding is used.
2013-04-11 01:51:06 +09:00
{ "id": "issue3064",
"file": "pdfs/issue3064.pdf",
"md5": "0307415b7d69b13acaf8bd4285d9544b",
"rounds": 1,
"link": true,
"type": "eq",
"about": "True type font with encoding dict with no base encoding but with differences."
},
Fix reading number of HTMX metrics. The length of the HHEA table can be incorrect, so it is better to read the number of metrics offset from beginning of table instead.
2019-01-05 08:13:13 +09:00
{ "id": "issue10402",
"file": "pdfs/issue10402.pdf",
"md5": "7936bd34d7c0aebd0a864b5aa98aa1b4",
"rounds": 1,
"type": "eq"
},
Add a couple more, mostly `text`, reference tests for non-embedded symbolic fonts without included encoding information I've started to look into how we can fix issue 7580, but quickly became worried that fixing it could easily mean that we'd trade one fixed PDF file for a multitude of broken ones. Hence I started going through the history of the code that choose the fallback encoding, and noticed that it has been changed a number of times over the years to deal with various cases of weirdness/errors in non-embedded fonts. To my relief it turned out that almost all the PRs, please see a possibly incomplete [list here], that changed this code actually included `eq` test-cases. However, in one case it appears that a PR missed to add a test-case. Furthermore since the fallback encoding may also be the only source for creating a `toUnicode` map, changing the encoding could possibly regress only the text-selection despite a PDF file still rendering correctly. Therefore, this PR adds one new `eq` test, and also a number of additional `text` tests for PDF files already present in the test-suite. Note that it's obviously possible that there's a certain overlap between the added tests, but I'd be *a whole lot* more concerned with causing regressions.
2016-09-10 20:10:15 +09:00
{ "id": "issue3064-text",
"file": "pdfs/issue3064.pdf",
"md5": "0307415b7d69b13acaf8bd4285d9544b",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "text"
},
Avoid rendering invisible Type3 fonts (issue 5421)
2014-10-19 05:29:21 +09:00
{ "id": "issue5421",
"file": "pdfs/issue5421.pdf",
"md5": "273f6813758a2349090003c7c8a0d85e",
"link": false,
"rounds": 1,
"type": "eq",
"about": "Invisible Type3 font used for text selection and searching."
},
Add a |text| test-case for issue 5421 Prior to PR 4259, we *incorrectly* ignored `toUnicode` for Type3 fonts. Since we now handle that correctly, this patch adds a `text` test-case to prevent regressions.
2015-03-03 20:58:20 +09:00
{ "id": "issue5421-text",
"file": "pdfs/issue5421.pdf",
"md5": "273f6813758a2349090003c7c8a0d85e",
"link": false,
"rounds": 1,
"type": "text"
},
Add a reduced test-case for PR 4922
2015-09-05 19:29:16 +09:00
{ "id": "pr4922",
"file": "pdfs/pr4922.pdf",
"md5": "178a55510931bc6ecd2f0f848a8fcacc",
"link": false,
"rounds": 1,
"type": "eq",
"about": "Type3 font with a missing /CharProcs resource."
},
Relax the |isSymbolicFont| check for TrueType (3, 1) cmap tables (issue 5701)
2015-02-05 23:25:23 +09:00
{ "id": "issue5701",
"file": "pdfs/issue5701.pdf",
"md5": "7ec476aee12e8bd6be79140223d329c1",
"rounds": 1,
"link": false,
"type": "eq"
},
Fetches params in makeFilter
2014-09-09 22:29:31 +09:00
{ "id": "issue5280",
"file": "pdfs/issue5280.pdf",
"md5": "0ea1230e2964e74cb6db063a89b78803",
"rounds": 1,
"link": false,
"type": "eq",
"about": "DecodeParams can be an indirect object"
},
Improves search of EI (end of inlined image)
2013-06-22 07:03:03 +09:00
{ "id": "bug878194",
"file": "pdfs/bug878194.pdf",
"md5": "c616b21fd2a1a65acc2de0f41e59a8b5",
"link": "true",
"rounds": 1,
"firstPage": 4,
"lastPage": 4,
Change bug878194 to an |eq| test
2014-10-23 21:19:05 +09:00
"type": "eq"
Improves search of EI (end of inlined image)
2013-06-22 07:03:03 +09:00
},
Implement "90pv" CMap
2013-03-02 11:02:35 +09:00
{ "id": "p020121130574743273239",
"file": "pdfs/P020121130574743273239.pdf",
"md5": "271b65885d42d174cbc597ca89becb1a",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Implement "83pv" CMap and fix CIDFontType0 handling
2013-02-26 21:06:07 +09:00
{ "id": "sfaa_japanese",
"file": "pdfs/SFAA_Japanese.pdf",
"md5": "b961bbc0d05bdd6d91041bca60ec8e8b",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Tweak the Bidi-detection heuristics for very short RTL strings (issue 11656) Very short strings can narrowly miss the existing Bidi-detection threshold, leading to incorrect text-selection and copying behaviour. In my testing, neither Adobe Reader or PDFium seem to handle copying "correctly" for this document. Hence it's not entirely clear to me that we actually want to fix this, since tweaking these heuristics can *obviously* cause regressions elsewhere (and our test coverage for RTL-text isn't exactly great).
2021-11-01 01:46:42 +09:00
{ "id": "issue11656",
"file": "pdfs/issue11656.pdf",
"md5": "82d5d4f5978a4974707deb1ea98e62f2",
"rounds": 1,
"type": "text"
},
Implements vertical writing
2013-02-08 21:29:22 +09:00
{ "id": "vertical",
"file": "pdfs/vertical.pdf",
"md5": "8a74d33504701edcefeef2afd022765e",
"rounds": 1,
"type": "eq"
},
Map all glyphs to the private use area and duplicate the first glyph. There have been lots of problems with trying to map glyphs to their unicode values. It's more reliable to just use the private use areas so the browser's font renderer doesn't mess with the glyphs. Using the private use area for all glyphs did highlight other issues that this patch also had to fix: * small private use area - Previously, only the BMP private use area was used which can't map many glyphs. Now, the (much bigger) PUP 16 area can also be used. * glyph zero not shown - Browsers will not use the glyph from a font if it is glyph id = 0. This issue was less prevalent when we mapped to unicode values since the fallback font would be used. However, when using the private use area, the glyph would not be drawn at all. This is illustrated in one of the current test cases (issue #8234) where there's an "ä" glyph at position zero. The PDF looked like it rendered correctly, but it was actually not using the glyph from the font. To properly show the first glyph it is always duplicated and appended to the glyphs and the maps are adjusted. * supplementary characters - The private use area PUP 16 is 4 bytes, so String.fromCodePoint must be used where we previously used String.fromCharCode. This is actually an issue that should have been fixed regardless of this patch. * charset - Freetype fails to load fonts when the charset size doesn't match number of glyphs in the font. We now write out a fake charset with the correct length. This also brought up the issue that glyphs with seac/endchar should only ever write a standard charset, but we now write a custom one. To get around this the seac analysis is permanently enabled so those glyphs are instead always drawn as two glyphs.
2018-01-05 07:43:07 +09:00
{ "id": "bug1425312",
"file": "pdfs/bug1425312.pdf",
"md5": "5b1e7d3e4ba7792fab2b69d1836df5a9",
"link": true,
"rounds": 1,
"firstPage": 2,
"lastPage": 2,
"type": "eq"
},
Ignoring glyphs without points
2013-11-03 07:07:13 +09:00
{ "id": "issue3438",
"file": "pdfs/issue3438.pdf",
"md5": "5aa3340b0920b65a377f697587668f89",
"rounds": 1,
"type": "eq"
},
Fixes decoding for CMYK jpegs.
2014-10-16 05:56:29 +09:00
{ "id": "bug1072164",
"file": "pdfs/bug1072164.pdf",
"md5": "cfee3c51e8464aa44218f4eaf27e084b",
"rounds": 1,
"link": true,
"type": "eq",
"about": "CMYK jpeg with mask"
},
Handle annotations with no resources.
2013-06-26 06:22:03 +09:00
{ "id": "bug886717",
"file": "pdfs/bug886717.pdf",
"md5": "8ba614192797a1324765610231a1bc9d",
"rounds": 1,
"type": "load",
"about": "Annotation that has no resources."
},
Test for #3263
2013-05-17 01:39:39 +09:00
{ "id": "issue3263",
Replace the unavailable linked test-case for issue 3263 with a reduced test-case Re: issue 3263 and PR 3265.
2015-11-14 00:47:02 +09:00
"file": "pdfs/issue3263r.pdf",
"md5": "0ef82d7a6998c3919cf5595dd47b31a6",
Test for #3263
2013-05-17 01:39:39 +09:00
"rounds": 1,
Replace the unavailable linked test-case for issue 3263 with a reduced test-case Re: issue 3263 and PR 3265.
2015-11-14 00:47:02 +09:00
"link": false,
Test for #3263
2013-05-17 01:39:39 +09:00
"type": "eq"
},
Fix lab colorspace decoding and rgb conversion.
2013-04-04 02:36:09 +09:00
{ "id": "issue2761",
"file": "pdfs/issue2761.pdf",
"md5": "35df0b8cff4afec0c08f08c6a5bc9857",
"rounds": 1,
"type": "eq",
"about": "Image with indexed colorspace that has a base lab colorspace."
},
Regression test for issue 2842
2013-03-10 11:21:44 +09:00
{ "id": "20130226130259",
"file": "pdfs/20130226130259.pdf",
"md5": "c33e90a1b369c508573023d2434b950f",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Handle missing 'FontName' entry in FontDescriptor object
2013-01-12 10:10:09 +09:00
{ "id": "issue2099-1",
"file": "pdfs/issue2099-1.pdf",
"md5": "c7eca682d70a976dfc4b7e64d3e9f1ce",
"rounds": 1,
"type": "eq"
test for issue2829.
2013-02-28 09:56:12 +09:00
},
Fixes reading unordered Subrs in Type1
2013-05-17 01:21:47 +09:00
{ "id": "issue3207",
Replace the unavailable linked test-case for issue 3207 with a reduced test-case Re: issue 3207 and PR 3268.
2015-11-15 21:27:48 +09:00
"file": "pdfs/issue3207r.pdf",
"md5": "617bcf475c109365a113cf9fb6711b0a",
"link": false,
"rounds": 1,
"type": "eq"
Fixes reading unordered Subrs in Type1
2013-05-17 01:21:47 +09:00
},
Adds test case for JPX COC marker
2014-06-14 08:22:22 +09:00
{ "id": "issue3591",
"file": "pdfs/issue3591.pdf",
"md5": "f76b3e9d1a44621b73063cf10556c6ff",
"link": true,
"firstPage": 1,
"lastPage": 1,
"rounds": 1,
"type": "eq",
"about": "JPX with 0xFF55 marker"
},
Add test case for JPX "Out of packets" error
2014-10-22 17:40:50 +09:00
{ "id": "bug865858",
"file": "pdfs/bug865858.pdf",
"md5": "7a81bd987dc1d95e9a0be46b7c3f2e18",
"link": true,
"rounds": 1,
"type": "eq",
"about": "JPX packets"
},
Extend the glyph maps for standard respectively Calibri fonts (issue 13916)
2021-08-21 06:17:53 +09:00
{ "id": "issue13916",
"file": "pdfs/issue13916.pdf",
"md5": "5cfaff104b17f325610936875363541f",
"rounds": 1,
"type": "eq"
},
Implements FFC1 marker (and syncs with jpgjs)
2013-06-26 02:35:34 +09:00
{ "id": "bug766138",
"file": "pdfs/bug766138.pdf",
"md5": "b171f5cf8d9834348112fba60ee54f8c",
"link": true,
"rounds": 1,
"type": "eq"
},
Fixes ASCIIHex decoding
2013-07-12 03:33:29 +09:00
{ "id": "bug889327",
"file": "pdfs/bug889327.pdf",
"md5": "b45cd63419241c40731f98d0e1dac082",
"link": true,
"lastPage": 1,
"rounds": 1,
"type": "eq"
},
Fallback font for buttons must be ZapfDingbats. Fix bug https://bugzilla.mozilla.org/show_bug.cgi?id=1669099.
2020-10-22 00:21:33 +09:00
{ "id": "bug1669099",
"file": "pdfs/bug1669099.pdf",
"md5": "34421549d58e2b6eeddc674759381f7d",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"29R": {
"value": true
},
"33R": {
"value": true
},
"37R": {
"value": true
},
"65R": {
"value": true
},
"69R": {
"value": true
}
Fallback font for buttons must be ZapfDingbats. Fix bug https://bugzilla.mozilla.org/show_bug.cgi?id=1669099.
2020-10-22 00:21:33 +09:00
}
},
Skipping empty font tables
2013-11-02 07:13:31 +09:00
{ "id": "issue1171.pdf",
"file": "pdfs/issue1171.pdf",
"md5": "2a6188a42a5874c7874b88eebd4acaf0",
"rounds": 1,
"type": "eq"
},
Support for CMap GBKp-EUC-H
2013-08-11 17:35:56 +09:00
{ "id": "issue3521.pdf",
"file": "pdfs/issue3521.pdf",
"md5": "df95d31443e20a38efa29c3a635a045b",
"rounds": 1,
"type": "eq",
"about": "Support for CMap GBKp-EUC-H"
},
Fix several issues with radial/axial shadings and tiling patterns. Previously, we set the base transformation and pattern matrix directly to the main rendering ctx of the page, however doing this caused the current transform to be lost. This would cause issues with things like shear missing so the pattern was misaligned or when stroke was used the scale of the line width or dash would be wrong. Instead we should leave the current transform and use setTransfrom on the pattern so it is applied correctly. For axial and radial shadings I had to create a temporary canvas to draw the shading so I could in turn use setTransform. Fixes: #13325, #6769, #7847, #11018, #11597, #11473 The following already in the corpus are improved: issue8078-page1 issue1877-page1
2021-05-11 09:43:37 +09:00
{ "id": "issue13325_reduced",
"file": "pdfs/issue13325_reduced.pdf",
"md5": "a9311230d2e3388070711be8748a1aa0",
"rounds": 1,
"type": "eq"
},
Support Optional Content in Image-/XObjects (issue 13931) Currently, in the `PartialEvaluator`, we only support Optional Content in Form-/XObjects. Hence this patch adds support for Image-/XObjects as well, which looks like a simple oversight in PR 12095 since the canvas-implementation already contains the necessary code to support this.
2021-08-24 18:30:19 +09:00
{ "id": "issue13931-default",
"file": "pdfs/issue13931.pdf",
"md5": "799d5025787115d22863ae23a3042491",
"rounds": 1,
"type": "eq"
},
Add support for specifying non-default Optional Content in the ref-tests
2021-08-24 18:48:54 +09:00
{ "id": "issue13931-hidden",
"file": "pdfs/issue13931.pdf",
"md5": "799d5025787115d22863ae23a3042491",
"rounds": 1,
"type": "eq",
"optionalContent": {
"7R": false
}
},
test for issue2829.
2013-02-28 09:56:12 +09:00
{ "id": "issue2829",
"file": "pdfs/issue2829.pdf",
"md5": "f32b28cf8792f6ccc470446bfbb38584",
"link": true,
"rounds": 1,
"type": "eq"
Sharpen the patterns. Draw the patterns with the intended resolution instead of scaling afterwards. Scaling leads to unclear patterns. Also: Make TilingPattern function for paintType switch case. Make TilingPattern function for bbox clipping. Make TilingPattern functions for scaling code. Increase MAX_PATTERN_SIZE to 4096. Add Singular Value Decomposition function.
2012-12-27 16:35:25 +09:00
},
JS -- Add support for buttons * radio buttons * checkboxes
2020-11-19 02:54:26 +09:00
{ "id": "js-buttons",
"file": "pdfs/js-buttons.pdf",
JS -- update radio/checkbox values even if there are no actions
2021-01-09 00:43:16 +09:00
"md5": "26f552398b77f8e85b2a8a166ca2ba6a",
JS -- Add support for buttons * radio buttons * checkboxes
2020-11-19 02:54:26 +09:00
"rounds": 1,
"type": "eq"
},
Strip TT programs if it's invalid
2013-03-18 22:06:59 +09:00
{ "id": "issue2956",
"file": "pdfs/issue2956.pdf",
"md5": "d8f68cbbb4bf54cde9f7f878acb6d7cd",
"rounds": 1,
Removes duplicate entries after reading cmap table
2013-11-02 06:30:28 +09:00
"type": "eq"
},
Fixes cvt table length; removes cvt when hints invalid
2013-11-09 02:38:36 +09:00
{ "id": "issue2799",
"file": "pdfs/issue2799.pdf",
"md5": "3d3224eae54bbae5fc76224a2af49486",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Removes duplicate entries after reading cmap table
2013-11-02 06:30:28 +09:00
{ "id": "issue3025",
"file": "pdfs/issue3025.pdf",
"md5": "8e4e8eacbd7c4c248deeca0ec49d38da",
"rounds": 1,
Strip TT programs if it's invalid
2013-03-18 22:06:59 +09:00
"type": "eq"
},
Sharpen the patterns. Draw the patterns with the intended resolution instead of scaling afterwards. Scaling leads to unclear patterns. Also: Make TilingPattern function for paintType switch case. Make TilingPattern function for bbox clipping. Make TilingPattern functions for scaling code. Increase MAX_PATTERN_SIZE to 4096. Add Singular Value Decomposition function.
2012-12-27 16:35:25 +09:00
{ "id": "issue2177-eq",
"file": "pdfs/issue2177.pdf",
"md5": "48a808278bf31de8414c4e03ecd0900a",
"rounds": 1,
"type": "eq"
Fix regression from issue 3312
2013-06-25 00:21:12 +09:00
},
{ "id": "issue3384",
"file": "pdfs/issue3384.pdf",
"md5": "57e31e83c165f16609528ad5ec5825ba",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
Enable loading of PDFs with invalid document information dictionaries
2013-08-09 02:02:11 +09:00
},
Implement initial CalGray support Gamma and Whitepoint are supported in this patch for CalGray. Blackpoint is not supported.
2013-04-26 04:26:42 +09:00
{ "id": "calgray",
"file": "pdfs/calgray.pdf",
"md5": "ee784999bfa1ed373f55cdabbb580df1",
"rounds": 1,
"type": "eq"
},
implement CalRGB color space Both whitespace and blackspace support are implemented.
2014-03-18 03:38:00 +09:00
{ "id": "calrgb",
"file": "pdfs/calrgb.pdf",
CalRGB: optimize CalRGB calculations Also fix one silly mistake.
2014-08-16 17:37:52 +09:00
"md5": "625068e9a7dd80e4f70b24ce97b3ec5c",
implement CalRGB color space Both whitespace and blackspace support are implemented.
2014-03-18 03:38:00 +09:00
"rounds": 1,
"lastPage": 8,
"type": "eq"
},
Allocates bigger hashData buffer
2013-11-18 22:48:06 +09:00
{ "id": "bug900822",
"file": "pdfs/bug900822.pdf",
"md5": "70e2a3c5922574eeda169c955cf9d084",
"rounds": 1,
"type": "load"
},
Enable loading of PDFs with invalid document information dictionaries
2013-08-09 02:02:11 +09:00
{ "id": "issue2853",
"file": "pdfs/issue2853.pdf",
"md5": "9f0ad95ef0b243ee8813c4eca0f7a042",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "load"
Transposed feature for text decoding in jbig2
2013-09-27 03:49:02 +09:00
},
Guesses Type1C font type based on file content
2014-04-25 01:48:18 +09:00
{ "id": "issue4668",
"file": "pdfs/issue4668.pdf",
"md5": "a749d5ca995ad745411406d29156b04e",
"rounds": 1,
"type": "eq"
},
Transposed feature for text decoding in jbig2
2013-09-27 03:49:02 +09:00
{ "id": "issue3666",
"file": "pdfs/issue3666.pdf",
Update the link location for 'issue3666.pdf' to point to the Internet Archive Note that despite the new file having a different hash than the the current one, it does render *identically* and most importantly it uses *the same* JBIG2 functionality. For reference, please see issue 3666 and PR 3738.
2016-01-12 05:24:50 +09:00
"md5": "cbcaf533d8a4e825d7f12cb4f137babd",
Transposed feature for text decoding in jbig2
2013-09-27 03:49:02 +09:00
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 2,
"type": "eq"
Fix word spacing in Type 0 fonts Fix word spacing in Type 0 font correct word spacing correct word spacing in type 0 font fix word spacing
2013-11-07 02:06:00 +09:00
},
Fix handling of symbolic fonts and unicode cmaps. In issue 12120, the font has a 1,0 cmap and is marked symbolic which according to the spec means we should directly use the cmap instead of the extra steps that are defined in 9.6.6.4. However, just fixing that caused bug 1057544 to break. The font in bug 1057544 has a 0,1 cmap (Unicode 1.1) which we were not using, but is easy to support. We're also easily able to support some of the other unicode cmaps, so I added those as well. There was also a second issue with bug 1057544, the cmap doesn't have a mapping for the "quoteright" glyph, but it is defined in the post table. To handle this, I've moved post table as a fallback for any font that has an encoding.
2020-08-22 07:25:07 +09:00
{ "id": "issue12120_reduced",
"file": "pdfs/issue12120_reduced.pdf",
"md5": "b4570dcee26ac3121ad3322e19ed1a6a",
"rounds": 1,
"type": "eq"
},
Prevent errors if the `InkList` property, in InkAnnotations, is missing and/or not an Array (issue 12392) To prevent a future bug, the `Vertices` property in PolylineAnnotations are handled the same way.
2020-09-19 22:29:55 +09:00
{ "id": "issue12392",
"file": "pdfs/issue12392.pdf",
"md5": "76c3a34c6520940c45c66c92f7df2de5",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
In a text widget, Font resources can be in the appearance
2020-09-20 00:11:04 +09:00
{ "id": "issue12394",
"file": "pdfs/issue12392.pdf",
"md5": "76c3a34c6520940c45c66c92f7df2de5",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
"print": "true",
"annotationStorage": {
Fix broken "issue12394" test-case This test-case is currently broken, with the reference image being completely empty, since it uses the old "annotationStorage" format in the manifest.
2021-01-10 05:42:56 +09:00
"35R": {
"value": "收文"
}
In a text widget, Font resources can be in the appearance
2020-09-20 00:11:04 +09:00
}
},
Support `InkAnnotation`s without appearance streams (issue 13298) (#13301) For now, we keep things purposely simple by using straight lines (rather than curves); please see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G11.2096579
2021-04-27 18:49:03 +09:00
{ "id": "annotation-ink-without-appearance",
"file": "pdfs/annotation-ink-without-appearance.pdf",
"md5": "eb06ad4ac260060082ef86435a2feed5",
"rounds": 1,
"type": "eq"
},
Adds CMYK JPEG test
2014-06-03 22:56:16 +09:00
{ "id": "issue4883",
"file": "pdfs/issue4883.pdf",
"md5": "2fac0d9a189ca5fcef8626153d050be8",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"about": "CMYK JPEG with Decode"
},
Fixes glyphs with invalid flags
2013-11-14 04:45:59 +09:00
{ "id": "bug903856",
"file": "pdfs/bug903856.pdf",
"md5": "286eaa9d06a5809f4f08f2093cef8f3f",
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
},
Fix word spacing in Type 0 fonts Fix word spacing in Type 0 font correct word spacing correct word spacing in type 0 font fix word spacing
2013-11-07 02:06:00 +09:00
{ "id": "issue3205",
Replace the unavailable linked test-case for issue 3205 with a reduced test-case
2015-09-10 23:59:30 +09:00
"file": "pdfs/issue3205r.pdf",
"md5": "379cd3f2f0d651215c6df5ac6182d013",
Fix word spacing in Type 0 fonts Fix word spacing in Type 0 font correct word spacing correct word spacing in type 0 font fix word spacing
2013-11-07 02:06:00 +09:00
"rounds": 1,
Replace the unavailable linked test-case for issue 3205 with a reduced test-case
2015-09-10 23:59:30 +09:00
"link": false,
Fix word spacing in Type 0 fonts Fix word spacing in Type 0 font correct word spacing correct word spacing in type 0 font fix word spacing
2013-11-07 02:06:00 +09:00
"type": "eq"
Support for the image mask in higher resolution than the image itself
2014-02-06 03:58:14 +09:00
},
fix handling of flags 1-3 in coons shading Short story: somebody got lost in two different indices. pi is an index in the stream and is explained on page 198 of the 32000-spec (however 1-based there), and ps is an index to something in PDF.js. I used the code from flag 0 (which works) to understand which is which. It is also important to understand that for flags 1,2 and 3, the stream is always assigned to the same coordinates and colors. What changes is which "old" coordinates and colors are assigned to what is "missing" in the stream. This is why for these flags, the code is identical except for the assignments in the first "row".
2015-08-04 00:34:30 +09:00
{ "id": "issue4227",
"file": "pdfs/coons-allflags-withfunction.pdf",
"md5": "c5f79c24bf9eb66698be0e4ecaa1bdf8",
"rounds": 1,
"type": "eq"
},
Add a reduced test-case for issue 4575 Re: issue 4575 and PR 4581.
2015-10-23 22:15:06 +09:00
{ "id": "issue4575",
"file": "pdfs/issue4575.pdf",
"md5": "9ea15032afd330916a4d7475cbdb55f6",
"rounds": 1,
"link": false,
"type": "eq"
},
Test case for tensor shading PR 6310
2015-08-05 06:55:55 +09:00
{ "id": "issue6305-part-1",
"file": "pdfs/tensor-allflags-withfunction.pdf",
"md5": "b47260d50f6a0f26aaccbfa3b7176ae8",
"rounds": 1,
"type": "eq"
},
Support for the image mask in higher resolution than the image itself
2014-02-06 03:58:14 +09:00
{ "id": "issue4246",
"file": "pdfs/issue4246.pdf",
"md5": "ed81787b83cc317c9f049643b853bea3",
"rounds": 1,
"type": "eq",
"about": "Image mask in higher resolution than the image itself"
Added TC for issue 4436
2014-03-19 21:25:46 +09:00
},
Map all glyphs to the private use area and duplicate the first glyph. There have been lots of problems with trying to map glyphs to their unicode values. It's more reliable to just use the private use areas so the browser's font renderer doesn't mess with the glyphs. Using the private use area for all glyphs did highlight other issues that this patch also had to fix: * small private use area - Previously, only the BMP private use area was used which can't map many glyphs. Now, the (much bigger) PUP 16 area can also be used. * glyph zero not shown - Browsers will not use the glyph from a font if it is glyph id = 0. This issue was less prevalent when we mapped to unicode values since the fallback font would be used. However, when using the private use area, the glyph would not be drawn at all. This is illustrated in one of the current test cases (issue #8234) where there's an "ä" glyph at position zero. The PDF looked like it rendered correctly, but it was actually not using the glyph from the font. To properly show the first glyph it is always duplicated and appended to the glyphs and the maps are adjusted. * supplementary characters - The private use area PUP 16 is 4 bytes, so String.fromCodePoint must be used where we previously used String.fromCharCode. This is actually an issue that should have been fixed regardless of this patch. * charset - Freetype fails to load fonts when the charset size doesn't match number of glyphs in the font. We now write out a fake charset with the correct length. This also brought up the issue that glyphs with seac/endchar should only ever write a standard charset, but we now write a custom one. To get around this the seac analysis is permanently enabled so those glyphs are instead always drawn as two glyphs.
2018-01-05 07:43:07 +09:00
{ "id": "PDFJS-9279-reduced",
"file": "pdfs/PDFJS-9279-reduced.pdf",
"md5": "a562a25596e9fe571ac6fb5b9f561974",
"rounds": 1,
"type": "eq"
},
Added TC for issue 4436
2014-03-19 21:25:46 +09:00
{ "id": "issue4436",
Replace the unavailable linked test-case for issue 4436 with a reduced test-case Issue 4436 actually contains enough information to create a reduced test-case, which this patch uses to replace a currently unavailable linked test.
2015-09-10 19:49:41 +09:00
"file": "pdfs/issue4436r.pdf",
Improve performance with image masks (bug 857031) - it aims to partially fix performance issue reported: https://bugzilla.mozilla.org/show_bug.cgi?id=857031; - the idea is too avoid to use byte arrays but use ImageBitmap which are a way faster to draw: * an ImageBitmap is Transferable which means that it can be built in the worker instead of in the main thread: - this is achieved in using an OffscreenCanvas when it's available, there is a bug to enable them for pdf.js: https://bugzilla.mozilla.org/show_bug.cgi?id=1763330; - or in using createImageBitmap: in Firefox a task is sent to the main thread to build the bitmap so it's slightly slower than using an OffscreenCanvas. * it's transfered from the worker to the main thread by "reference"; * the byte buffers used to create the image data have a very short lifetime and ergo the memory used is globally less than before. - Use the localImageCache for the mask; - Fix the pdf issue4436r.pdf: it was expected to have a binary stream for the image; - Move the singlePixel trick from operator_list to image: this way we can use this trick even if it isn't in a set as defined in operator_list.
2022-04-06 22:34:08 +09:00
"md5": "f5dc60cce342ac8d165069a80d23b92e",
Added TC for issue 4436
2014-03-19 21:25:46 +09:00
"rounds": 1,
Replace the unavailable linked test-case for issue 4436 with a reduced test-case Issue 4436 actually contains enough information to create a reduced test-case, which this patch uses to replace a currently unavailable linked test.
2015-09-10 19:49:41 +09:00
"link": false,
Added TC for issue 4436
2014-03-19 21:25:46 +09:00
"type": "eq"
Fix mishandling of incomplete, inverted masks.
2014-06-13 09:37:41 +09:00
},
{ "id": "issue4926",
"file": "pdfs/issue4926.pdf",
"md5": "ed881c8ea2f9bc4be94ecb7f2b2c149b",
"rounds": 1,
"link": true,
"type": "eq"
Test case for issue 5549
2014-12-18 06:42:06 +09:00
},
Improve "EI" detection in inline images (PR 12028 follow-up, issue 16454) Given that inline images may contain "EI"-sequences in the image-data itself, actually finding the end-of-image operator isn't always straightforward. Here we extend the implementation from PR 12028 to potentially check all of the following bytes, rather than stopping immediately. While we have fairly decent test-coverage for this code, whenever you're changing it there's unfortunately a slightly higher than normal risk of regressions. (You'd really wish that PDF generators just stop using inline images.)
2023-05-23 20:08:02 +09:00
{ "id": "issue16454",
"file": "pdfs/issue16454.pdf",
"md5": "82fe0c54a96667472ce999be7a789199",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
},
Adjust `decodeACSuccessive` in src/core/jpg.js to improve the rendering quality of (progressive) JPEG images I've been looking into the remaining point in 8637 about blurry images, to see if we could perhaps improve the rendering quality slightly there. After quite a bit of debugging, it seems that the issue is limited to certain progressive JPEG images. As mentioned previously, I've got no detailed knowledge of the JPEG format, but this patch does seem to improve things quite a bit for the images in question. Squinting at https://searchfox.org/mozilla-central/rev/6c33dde6ca02b389c52e8db3d22494df8b916f33/media/libjpeg/jdphuff.c#492-639, it seems reasonable that we should take the sign of the data into account. Furthermore, looking at the specification in https://www.w3.org/Graphics/JPEG/itu-t81.pdf#page=118, the "F.2.4.3 Decoding the binary decision sequence for non-zero DC differences and AC coefficients" section even contains a description of this (even though I cannot claim to really understand the details).
2017-12-29 22:39:29 +09:00
{ "id": "decodeACSuccessive",
"file": "pdfs/decodeACSuccessive.pdf",
"md5": "7749c032624fe27ab8e8d7d5e9a4a93f",
"rounds": 1,
"link": false,
[api-minor] Decode all JPEG images with the built-in PDF.js decoder in `src/core/jpg.js` Currently some JPEG images are decoded by the built-in PDF.js decoder in `src/core/jpg.js`, while others attempt to use the browser JPEG decoder. This inconsistency seem unfortunate for a number of reasons: - It adds, compared to the other image formats supported in the PDF specification, a fair amount of code/complexity to the image handling in the PDF.js library. - The PDF specification support JPEG images with features, e.g. certain ColorSpaces, that browsers are unable to decode natively. Hence, determining if a JPEG image is possible to decode natively in the browser require a non-trivial amount of parsing. In particular, we're parsing (part of) the raw JPEG data to extract certain marker data and we also need to parse the ColorSpace for the JPEG image. - While some JPEG images may, for all intents and purposes, appear to be natively supported there's still cases where the browser may fail to decode some JPEG images. In order to support those cases, we've had to implement a fallback to the PDF.js JPEG decoder if there's any issues during the native decoding. This also means that it's no longer possible to simply send the JPEG image to the main-thread and continue parsing, but you now need to actually wait for the main-thread to indicate success/failure first. In practice this means that there's a code-path where the worker-thread is forced to wait for the main-thread, while the reverse should *always* be the case. - The native decoding, for anything except the *simplest* of JPEG images, result in increased peak memory usage because there's a handful of short-lived copies of the JPEG data (see PR 11707). Furthermore this also leads to data being *parsed* on the main-thread, rather than the worker-thread, which you usually want to avoid for e.g. performance and UI-reponsiveness reasons. - Not all environments, e.g. Node.js, fully support native JPEG decoding. This has, historically, lead to some issues and support requests. - Different browsers may use different JPEG decoders, possibly leading to images being rendered slightly differently depending on the platform/browser where the PDF.js library is used. Originally the implementation in `src/core/jpg.js` were unable to handle all of the JPEG images in the test-suite, but over the last couple of years I've fixed (hopefully) all of those issues. At this point in time, there's two kinds of failure with this patch: - Changes which are basically imperceivable to the naked eye, where some pixels in the images are essentially off-by-one (in all components), which could probably be attributed to things such as different rounding behaviour in the browser/PDF.js JPEG decoder. This type of "failure" accounts for the *vast* majority of the total number of changes in the reference tests. - Changes where the JPEG images now looks *ever so slightly* blurrier than with the native browser decoder. For quite some time I've just assumed that this pointed to a general deficiency in the `src/core/jpg.js` implementation, however I've discovered when comparing two viewers side-by-side that the differences vanish at higher zoom levels (usually around 200% is enough). Basically if you disable [this downscaling in canvas.js](https://github.com/mozilla/pdf.js/blob/8fb82e939cf0c8618a4e775ff17fc96f726872b5/src/display/canvas.js#L2356-L2395), which is what happens when zooming in, the differences simply vanish! Hence I'm pretty satisfied that there's no significant problems with the `src/core/jpg.js` implementation, and the problems are rather tied to the general quality of the downscaling algorithm used. It could even be seen as a positive that *all* images now share the same downscaling behaviour, since this actually fixes one old bug; see issue 7041.
2020-01-20 20:10:16 +09:00
"type": "eq"
Adjust `decodeACSuccessive` in src/core/jpg.js to improve the rendering quality of (progressive) JPEG images I've been looking into the remaining point in 8637 about blurry images, to see if we could perhaps improve the rendering quality slightly there. After quite a bit of debugging, it seems that the issue is limited to certain progressive JPEG images. As mentioned previously, I've got no detailed knowledge of the JPEG format, but this patch does seem to improve things quite a bit for the images in question. Squinting at https://searchfox.org/mozilla-central/rev/6c33dde6ca02b389c52e8db3d22494df8b916f33/media/libjpeg/jdphuff.c#492-639, it seems reasonable that we should take the sign of the data into account. Furthermore, looking at the specification in https://www.w3.org/Graphics/JPEG/itu-t81.pdf#page=118, the "F.2.4.3 Decoding the binary decision sequence for non-zero DC differences and AC coefficients" section even contains a description of this (even though I cannot claim to really understand the details).
2017-12-29 22:39:29 +09:00
},
Add back dir property in spans in text layer - aims to fix #12909
2021-01-26 06:10:46 +09:00
{ "id": "issue12909",
"file": "pdfs/issue12909.pdf",
"md5": "0faa1cb029c3323c168595cccbe46ec0",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "text"
},
CCITTFaxStream: fix regression when EncodedByteAlign is true and EndOfLine is false
2014-12-30 06:28:03 +09:00
{ "id": "issue5592",
"file": "pdfs/issue5592.pdf",
"md5": "a0750f95afa80c880f7966df7062616c",
"rounds": 1,
"link": true,
"type": "eq"
},
shading-pattern: While drawing patterns, transform to the baseTransform first
2015-11-25 16:44:06 +09:00
{ "id": "issue6296.pdf",
"file": "pdfs/issue6296.pdf",
"md5": "734e191aab1372e6fd7523ca7751fcf0",
"rounds": 1,
"type": "eq"
},
shading-pattern: Decreased `Shadings.SMALL_NUMBER` and added a test case for #6298
2015-12-24 02:17:23 +09:00
{ "id": "issue6298.pdf",
"file": "pdfs/issue6298.pdf",
"md5": "214340be34f463611fc3127ad0695034",
"rounds": 1,
"type": "eq"
},
Test case for issue 5549
2014-12-18 06:42:06 +09:00
{ "id": "issue5549.pdf",
"file": "pdfs/issue5549.pdf",
"md5": "6c36df6ebc583c9e18aad0ad00d257b8",
"rounds": 1,
"type": "eq",
"about": "Free image obtained from www.unsplash.com"
Test case for issue 5475
2014-12-18 06:46:47 +09:00
},
{ "id": "issue5475.pdf",
"file": "pdfs/issue5475.pdf",
"md5": "bda962373570ac4dfe0fbd1ad4f0d9ef",
"rounds": 1,
"type": "eq",
"about": "Free image obtained from www.unsplash.com"
Test case for issue 5481
2014-12-19 05:26:02 +09:00
},
Add tests and documentation for the annotation border style class This patch adds: - Unit tests for the annotation border style class - Regression test (self-made) for the annotation border style class - Documentation generation using JSDoc
2014-12-26 05:04:01 +09:00
{ "id": "annotation-border-styles.pdf",
"file": "pdfs/annotation-border-styles.pdf",
"md5": "22930fc09c7386e1131b14d936e554af",
"rounds": 1,
Implement annotation layer regression testing
2015-12-19 06:29:22 +09:00
"type": "eq",
"annotations": true
Add tests and documentation for the annotation border style class This patch adds: - Unit tests for the annotation border style class - Regression test (self-made) for the annotation border style class - Documentation generation using JSDoc
2014-12-26 05:04:01 +09:00
},
Test case for issue 5481
2014-12-19 05:26:02 +09:00
{ "id": "issue5481.pdf",
"file": "pdfs/issue5481.pdf",
"md5": "cf00bd25b15b7e23542b48a626585c36",
"rounds": 1,
"type": "eq",
"about": "Free image obtained from www.unsplash.com"
Test case for issue 5567
2015-02-10 07:32:16 +09:00
},
{ "id": "issue5567",
"file": "pdfs/issue5567.pdf",
"md5": "d5b37f8bf1b3aafa1b4fcf19ebdc7c74",
"rounds": 1,
"type": "eq"
Fix error reading concatenated pdfs
2015-04-04 15:15:31 +09:00
},
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
{ "id": "issue5909_original",
"file": "pdfs/issue5909_original.pdf",
"md5": "65c169b6f540b27ac0ff2738a80d1e14",
"link": true,
Fix error reading concatenated pdfs
2015-04-04 15:15:31 +09:00
"rounds": 1,
Convert a number of reference tests, for documents with corrupt XRef tables, from `load` to `eq` As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly *first*. Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.
2019-10-13 01:15:55 +09:00
"lastPage": 2,
"type": "eq"
Subtract start offset for xrefs in recovery mode Xref offsets are relative to the start of the PDF data, not to the start of the PDF file. This is clear if you look at the other code: - In the XRef's readXRefTable and processXRefTable methods of XRef, the offset of a xref entry is set to the bytes as given by a PDF file. These values are always relative to the start of the PDF file (%PDF-). - The XRef's readXRef method adds the start offset of the stream to Xref entry's offset: "stream.pos = startXRef + stream.start". Clearly, this line assumes that the entry offset excludes the start offset. However, when the PDF is parsed in recovery mode, the xref table is filled with entries whose offset is relative to the start of the stream rather than the PDF file. This is incorrect, and the fix is to subtract the start offset of the stream from the entry's byte offset. The manually created PDF file serves as a regression test. It is a valid PDF, except: - The integer to point to the start of the xref table and the %%EOF trailer are missing. This will activate recovery mode in PDF.js - Some junk was added before the start of the PDF file. This exposes the bad offset bug.
2015-07-11 03:18:53 +09:00
},
{ "id": "issue6069",
"file": "pdfs/issue6069.pdf",
"md5": "d0ad8871f4116bca8e39513ffa8b7d8e",
"rounds": 1,
"type": "load"
Improve robustness of stream parser (invalid length) When the parser finds a stream, it retrieves the Length from the stream dictionary and advances the lexer to the offset as specified in Length. If this Length is incorrect, the lexer could end up anywhere. When the lexer gets in an invalid state, it could throw errors. For example, in issue 6108, the lexer ends up inside the stream data. This stream has the ASCIIHexDecode filter, so all characters are made up from ASCII characters, and the lexer interprets it as a command token. Tokens cannot be longer than 127 bytes, so eventually 128 bytes are consumed and the lexer throws "Command token too long" error. Another possible error is "Illegal character: 41" when the lexer happens to end up at a ')' due to the length mismatch. These problems are solved by catching lexer errors and recovering the parser via the existing stream length detection branch.
2015-07-11 19:15:43 +09:00
},
Group popup creation code and apply it to more annotation types
2016-02-23 08:21:28 +09:00
{ "id": "issue7014",
"file": "pdfs/issue7014.pdf",
"md5": "b410891d7a01af791364e9c530d61b17",
"rounds": 1,
"type": "eq",
"annotations": true
},
Implement support for Popup annotations Most code for Popup annotations is already present for Text annotations. This patch extracts the popup creation logic from the Text annotation code so it can be reused for Popup annotations. Not only does this add support for Popup annotations, the Text annotation code is also considerably easier. If a `Popup` entry is available for a Text annotation, it will not be more than an image. The popup will be handled by the Popup annotation. However, it is also possible for Text annotations to not have a separate Popup annotation, in which case the Text annotation handles the popup creation itself.
2015-12-23 05:31:56 +09:00
{ "id": "annotation-link-text-popup",
"file": "pdfs/annotation-link-text-popup.pdf",
"md5": "4bbf56e81d47232de5f305124ab0ba27",
"rounds": 1,
"type": "eq",
"annotations": true
},
{ "id": "annotation-text-without-popup",
"file": "pdfs/annotation-text-without-popup.pdf",
"md5": "7c2d241babe00139e34b9f8369a909eb",
"rounds": 1,
"type": "eq",
"annotations": true,
"about": "Text annotation without a separate Popup annotation"
},
Implement support for Underline annotations
2015-12-28 08:33:41 +09:00
{ "id": "annotation-underline",
"file": "pdfs/annotation-underline.pdf",
"md5": "c24b3aba771de52f9bac25e854c39458",
"rounds": 1,
"type": "eq",
"annotations": true
},
Add support for missing appearances for hightlights, strikeout, squiggly and underline annotations.
2020-08-08 03:46:41 +09:00
{ "id": "annotation-underline-without-appearance",
"file": "pdfs/annotation-underline-without-appearance.pdf",
"md5": "dd5be5e9a8e6bdbf67c175ca170f7cb7",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Use the *full* inline image as the cacheKey in `Parser.makeInlineImage` (bug 1799927) *Please note:* This only fixes the "wrong letter" part of bug 1799927. It appears that the simple `computeAdler32` function, used when caching inline images, generates hash collisions for some (very short) TypedArrays. In this case that leads to some of the "letters", which are actually inline images, being rendered incorrectly. Rather than switching to another hashing algorithm, e.g. the `MurmurHash3_64` class, we simply cache using a stringified version of the inline image data as the cacheKey to prevent any future collisions. While this will (naturally) lead to slightly higher peak memory usage, it'll however be limited to the current `Parser`-instance which means that it's not persistent. One small benefit of these changes is that we can avoid creating lots of `Stream`-instances for already cached inline images.
2022-11-10 22:00:23 +09:00
{ "id": "bug1799927",
"file": "pdfs/bug1799927.pdf",
"md5": "e6ad013c24e58e5b40c3bae50f04c8e8",
"rounds": 1,
"type": "eq"
},
Support `LineAnnotation`s with empty /Rect-entries (issue 6564) This extends PR 13033 slightly, with a heuristic to support corrupt PDF documents where the `LineAnnotation`s have an empty /Rect-entry. Please note that while I have no idea if this is "correct", this patch at least makes us output the same /BBox as re-saving in Adobe Reader does.
2021-03-16 00:16:49 +09:00
{ "id": "annotation-line-without-appearance-empty-Rect",
"file": "pdfs/annotation-line-without-appearance-empty-Rect.pdf",
"md5": "65f2d3ef80acfea637718c3fc66043b7",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Ignore color-operators in Type3 glyphs beginning with a `d1` operator (issue 12705) Please refer to the PDF specification at https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1977497 and https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G7.3998470 This patch removes the color-operators in the evaluator, since that should be more efficient than doing it repeatedly in the main-thread when rendering the Type3 glyphs.
2020-12-10 22:22:05 +09:00
{ "id": "issue12705",
"file": "pdfs/issue12705.pdf",
"md5": "d8725b9dcfef72fd4fa4a39cab711624",
"rounds": 1,
"type": "eq"
},
Implement support for StrikeOut annotations
2015-12-29 23:09:28 +09:00
{ "id": "annotation-strikeout",
"file": "pdfs/annotation-strikeout.pdf",
"md5": "6624e6b5bedd2f2855b6ab12bbf93c57",
"rounds": 1,
"type": "eq",
"annotations": true
},
Add support for missing appearances for hightlights, strikeout, squiggly and underline annotations.
2020-08-08 03:46:41 +09:00
{ "id": "annotation-strikeout-without-appearance",
"file": "pdfs/annotation-strikeout-without-appearance.pdf",
"md5": "1dc751ab83e8deb3094bfc580289b097",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Implement support for Squiggly annotations
2015-12-30 23:28:26 +09:00
{ "id": "annotation-squiggly",
"file": "pdfs/annotation-squiggly.pdf",
"md5": "38661e731ac6c525af5894d2d20c6e71",
"rounds": 1,
"type": "eq",
"annotations": true
},
Add support for missing appearances for hightlights, strikeout, squiggly and underline annotations.
2020-08-08 03:46:41 +09:00
{ "id": "annotation-squiggly-without-appearance",
"file": "pdfs/annotation-squiggly-without-appearance.pdf",
"md5": "6546f22a06a5e51d0e835c677cdbc705",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Implement support for Highlight annotations
2016-01-01 23:31:46 +09:00
{ "id": "annotation-highlight",
"file": "pdfs/annotation-highlight.pdf",
"md5": "e13e198e3a69c32dc9ebdc704d3105e1",
"rounds": 1,
"type": "eq",
"annotations": true
},
Add support for missing appearances for hightlights, strikeout, squiggly and underline annotations.
2020-08-08 03:46:41 +09:00
{ "id": "annotation-highlight-without-appearance",
"file": "pdfs/annotation-highlight-without-appearance.pdf",
"md5": "a1f2811324fa1ff0c9f1778697413dad",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Implement free text annotations
2019-04-14 01:45:22 +09:00
{ "id": "annotation-freetext",
"file": "pdfs/annotation-freetext.pdf",
"md5": "6ca19ce632ead3aed08f22e588510e2f",
"rounds": 1,
"type": "eq",
"annotations": true
},
Annotations: implement support for line annotations This patch implements support for line annotations. Other viewers only show the popup annotation when hovering over the line, which may have any orientation. To make this possible, we render an invisible line (SVG element) over the line on the canvas that acts as the trigger for the popup annotation. This invisible line has the same starting coordinates, ending coordinates and width of the line on the canvas.
2017-04-03 03:50:17 +09:00
{ "id": "annotation-line",
"file": "pdfs/annotation-line.pdf",
"md5": "fde60608be2748f10fb6522cba425ca1",
"rounds": 1,
"type": "eq",
"annotations": true
},
Implement rendering line annotations without appearance stream
2021-03-01 02:51:37 +09:00
{ "id": "annotation-line-without-appearance",
"file": "pdfs/annotation-line-without-appearance.pdf",
"md5": "1f60935b2a7719ce40616af60fc308a2",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Implement reference tests for square and circle annotations
2017-07-24 07:34:39 +09:00
{ "id": "annotation-square-circle",
"file": "pdfs/annotation-square-circle.pdf",
"md5": "cfd3c302f68d61e1d55ed9c7896046c3",
"rounds": 1,
"type": "eq",
"annotations": true
},
Implement rendering square/circle annotations without appearance stream
2021-02-22 01:10:35 +09:00
{ "id": "annotation-square-circle-without-appearance",
"file": "pdfs/annotation-square-circle-without-appearance.pdf",
"md5": "5b2a5e1e918137993d26a0cd8b0947f6",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Implement support for stamp annotations
2017-09-16 23:37:50 +09:00
{ "id": "annotation-stamp",
"file": "pdfs/annotation-stamp.pdf",
"md5": "0a04d7ce1ad103cb3c033d26855d6ec7",
"rounds": 1,
"type": "eq",
"annotations": true
},
Implement unit and reference testing for FileAttachment annotations
2016-02-15 05:27:53 +09:00
{ "id": "annotation-fileattachment",
"file": "pdfs/annotation-fileattachment.pdf",
"md5": "d20ecee4b53c81b2dd44c8715a1b4a83",
"rounds": 1,
"type": "eq",
"annotations": true
},
Add default icons for FileAttachment annotations (bug 1230933) *Please note:* This "borrows" the icons from Thunderbird. According to the PDF specification, see https://web.archive.org/web/20220309040754if_/https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf#G11.2096626, we should be providing default icons for FileAttachment annotations without appearances.
2022-11-26 01:00:57 +09:00
{ "id": "bug1230933",
"file": "pdfs/bug1230933.pdf",
"md5": "d8e7dce9ce79aa5a6121b21be8935429",
"link": true,
"rounds": 1,
"type": "eq",
"annotations": true
},
Implement TrueType character map "format 2" (fixes #14117) If a PDF included an embedded TrueType font whose preferred character map (cmap) was in "format 2", the code would select that character map and then refuse to read it because of an unsupported format, thus causing the characters not to be rendered. This commit implements support for format 2 as described at the link below. https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6cmap.html
2021-10-13 07:24:18 +09:00
{ "id": "issue14117",
"file": "pdfs/issue14117.pdf",
"md5": "9b1c33ad2f59f4e723c258e863149abf",
"rounds": 1,
"type": "eq"
},
Prevent rendering `TextWidgetAnnotation`s in both the `core`/`display` layer (issue 7643)
2016-09-18 22:35:12 +09:00
{ "id": "annotation-text-widget-annotations",
"file": "pdfs/annotation-text-widget.pdf",
Text widget annotations: implement comb support
2016-09-20 07:04:11 +09:00
"md5": "b7b8923a12998fca8603fae53f73f19b",
Prevent rendering `TextWidgetAnnotation`s in both the `core`/`display` layer (issue 7643)
2016-09-18 22:35:12 +09:00
"rounds": 1,
"type": "eq",
"annotations": true
},
Text widget annotations: improve unit and reference tests This patch improves the unit tests by testing the support for read-only and multiline fields. Moreover, we add a reference test to ensure that the text widgets are not only rendered, but also that their contents are styled properly. Finally, we perform minor improvements in `src/core/annotation.js`, for example adding missing comments.
2016-09-15 04:51:21 +09:00
{ "id": "annotation-text-widget-forms",
"file": "pdfs/annotation-text-widget.pdf",
Text widget annotations: implement comb support
2016-09-20 07:04:11 +09:00
"md5": "b7b8923a12998fca8603fae53f73f19b",
Text widget annotations: improve unit and reference tests This patch improves the unit tests by testing the support for read-only and multiline fields. Moreover, we add a reference test to ensure that the text widgets are not only rendered, but also that their contents are styled properly. Finally, we perform minor improvements in `src/core/annotation.js`, for example adding missing comments.
2016-09-15 04:51:21 +09:00
"rounds": 1,
"type": "eq",
"forms": true
},
Include reference tests for text/choice/button widget printing
2020-08-18 05:34:02 +09:00
{ "id": "annotation-text-widget-print",
"file": "pdfs/annotation-text-widget.pdf",
"md5": "b7b8923a12998fca8603fae53f73f19b",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"61R": {
"value": "Single line, unlimited length"
},
"62R": {
"value": "Single lin"
},
"63R": {
"value": "Single line, center aligned"
},
"64R": {
"value": "Single line, right aligned"
},
"65R": {
"value": ""
},
"66R": {
"value": "zyxwvutsrqponmlkjihgfedcba"
},
"67R": {
"value": "Multiline\nstring"
}
Include reference tests for text/choice/button widget printing
2020-08-18 05:34:02 +09:00
}
},
Choice widget annotations: unit and reference testing
2016-09-26 00:08:17 +09:00
{ "id": "annotation-choice-widget-annotations",
"file": "pdfs/annotation-choice-widget.pdf",
"md5": "7dfb0d743a0da0f4a71b209ab43b0be5",
"rounds": 1,
"type": "eq",
"annotations": true
},
Improve text-selection for Type3 fonts with empty /FontBBox-entries (issue 6605) For Type3 fonts where the /CharProcs-streams of the individual glyph starts with a `d1` operator, we can use that to build a fallback bounding box for the font and thus improve text-selection in some cases.
2021-05-30 01:06:49 +09:00
{ "id": "issue6605",
"file": "pdfs/issue6605.pdf",
"md5": "67158a9c6d0e966ece55f7c433e18cc5",
"rounds": 1,
"type": "text"
},
Choice widget annotations: unit and reference testing
2016-09-26 00:08:17 +09:00
{ "id": "annotation-choice-widget-forms",
"file": "pdfs/annotation-choice-widget.pdf",
"md5": "7dfb0d743a0da0f4a71b209ab43b0be5",
"rounds": 1,
"type": "eq",
"forms": true
},
Include reference tests for text/choice/button widget printing
2020-08-18 05:34:02 +09:00
{ "id": "annotation-choice-widget-print",
"file": "pdfs/annotation-choice-widget.pdf",
"md5": "7dfb0d743a0da0f4a71b209ab43b0be5",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"57R": {
"value": "Ipsum"
},
"58R": {
"value": "Lorem"
},
"59R": {
"value": "Dolor"
},
"62R": {
[Annotations] Add support for printing/saving choice list with multiple selections - it aims to fix issue #12189.
2022-03-27 06:45:50 +09:00
"value": ["Sit", "Adipiscing"]
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
}
Include reference tests for text/choice/button widget printing
2020-08-18 05:34:02 +09:00
}
},
Include forms/print reference tests for the document from #12233 In addition to the unit tests these reference tests make sure that this document, that triggered some edge cases in our code, can be rendered and printed successfully now.
2020-08-22 23:24:03 +09:00
{ "id": "issue12233-forms",
"file": "pdfs/issue12233.pdf",
"md5": "6099fc695fe018ce444752929d86f9c8",
"link": true,
"rounds": 1,
"type": "eq",
"forms": true
},
{ "id": "issue12233-print",
"file": "pdfs/issue12233.pdf",
"md5": "6099fc695fe018ce444752929d86f9c8",
"link": true,
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"20R": {
"value": true
}
Include forms/print reference tests for the document from #12233 In addition to the unit tests these reference tests make sure that this document, that triggered some edge cases in our code, can be rendered and printed successfully now.
2020-08-22 23:24:03 +09:00
}
},
Better approximate gradient color stops PDF gradients do not have color stops but an arbitrary PDF function of the type f(t) -> color. CSS gradients are only based on color stops. Most PDF gradient functions are produced from color stop oriented gradients. Take advantage of this by sampling the PDF function at a higher frequency but not converting any samples which could be interpolated to color stops. The sampling frequency is chosen to be the least common multiple of as many values as practical to exactly re-create the common case of the PDF function implementing equally spaced linearly interpolated stops in RGB color space. This also allows for better approximation of other smooth PDF functions (non-linear, or non-equally spaced, or in different color space). Fixes: #10572, #14165
2023-03-04 01:41:04 +09:00
{ "id": "issue10572",
"file": "pdfs/issue10572.pdf",
"md5": "48ad69ed106338b3c6845fc7101488b2",
"rounds": 1,
"type": "eq"
},
Jpeg encoded with RGB -instead of YCbCr- write the components index as "RGB" in ASCII to say it so On ISO/IEC 10918-6:2013 (E), section 6.1: (http://www.itu.int/rec/T-REC-T.872-201206-I/en) "Images encoded with three components are assumed to be RGB data encoded as YCbCr unless the image contains an APP14 marker segment as specified in 6.5.3, in which case the colour encoding is considered either RGB or YCbCr according to the application data of the APP14 marker segment" But common jpeg libraries consider RGB too if components index are ASCII R (0x52), G (0x47) and B (0x42): https://stackoverflow.com/questions/50798014/determining-color-space-for-jpeg/50861048 Issue #11931
2020-06-04 15:43:46 +09:00
{ "id": "issue11931",
"file": "pdfs/issue11931.pdf",
"md5": "9ea233037992e1f10280420a49e72845",
"rounds": 1,
"type": "eq"
},
Add (basic) support for transfer functions to Images (issue 6931, bug 1149713) This is *similar* to the existing transfer function support for SMasks, but extended to simple image data. Please note that the extra amount of data now being sent to the worker-thread, for affected /ExtGState entries, is limited to *at most* 4 `Uint8Array`s each with a length of 256 elements. Refer to https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G9.1658137 for additional details.
2020-08-17 15:49:19 +09:00
{ "id": "issue6931",
"file": "pdfs/issue6931_reduced.pdf",
"md5": "e61388913821a5e044bf85a5846d6d9a",
"rounds": 1,
"type": "eq"
},
[api-minor] Extend general transfer function support to browsers without `OffscreenCanvas` This patch extends PR 16115 to work in all browsers, regardless of their `OffscreenCanvas` support, such that transfer functions will be applied to general rendering (and not just image data). In order to do this we introduce the `BaseFilterFactory` that is then extended in browsers/Node.js environments, similar to all the other factories used in the API, such that we always have the necessary factory available in `src/display/canvas.js`. These changes help simplify the existing `putBinaryImageData` function, and the new method can easily be stubbed-out in the Firefox PDF Viewer. *Please note:* This patch removes the old *partial* transfer function support, which only applied to image data, from Node.js environments since the `node-canvas` package currently doesn't support filters. However, this should hopefully be fine given that: - Transfer functions are not very commonly used in PDF documents. - Browsers in general, and Firefox in particular, are the *primary* development target for the PDF.js library. - The FAQ only lists Node.js as *mostly* supported, see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support
2023-03-12 23:47:01 +09:00
{ "id": "issue6931-disable-isOffscreenCanvasSupported",
"file": "pdfs/issue6931_reduced.pdf",
"md5": "e61388913821a5e044bf85a5846d6d9a",
"rounds": 1,
"type": "eq",
"isOffscreenCanvasSupported": false
},
Button widget annotations: implement reference testing Moreover, ensure that the read-only state is respected and improve CSS names.
2016-12-16 06:15:38 +09:00
{ "id": "annotation-button-widget-annotations",
"file": "pdfs/annotation-button-widget.pdf",
"md5": "5cf23adfff84256d9cfe261bea96dade",
"rounds": 1,
"type": "eq",
"annotations": true
},
{ "id": "annotation-button-widget-forms",
"file": "pdfs/annotation-button-widget.pdf",
"md5": "5cf23adfff84256d9cfe261bea96dade",
"rounds": 1,
"type": "eq",
"forms": true
},
Include reference tests for text/choice/button widget printing
2020-08-18 05:34:02 +09:00
{ "id": "annotation-button-widget-print",
"file": "pdfs/annotation-button-widget.pdf",
"md5": "5cf23adfff84256d9cfe261bea96dade",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
JS -- hidden annotations must be built in case a script show them * in some pdf, there are actions with "event.source.hidden = ..." * in order to handle visibility when printing, annotationStorage is extended to store multiple properties (value, hidden, editable, ...)
2020-11-04 00:04:08 +09:00
"105R": {
"value": true
},
"106R": {
"value": false
},
"107R": {
"value": false
},
"108R": {
"value": true
},
"109R": {
"value": false
},
"110R": {
"value": false
},
"111R": {
"value": true
},
"112R": {
"value": false
},
"113R": {
"value": false
}
Include reference tests for text/choice/button widget printing
2020-08-18 05:34:02 +09:00
}
},
Enforce linewidth to 1px when at least one of scale factor is lower than 1
2021-01-15 19:56:20 +09:00
{ "id": "issue6127",
"file": "pdfs/issue6127.pdf",
"md5": "65ef9572bddef5fddfaf7172f10a0df2",
"rounds": 1,
"lastPage": 1,
"type": "eq"
},
Implement reference tests for polyline and polygon annotations
2017-09-24 00:01:19 +09:00
{ "id": "annotation-polyline-polygon",
"file": "pdfs/annotation-polyline-polygon.pdf",
"md5": "e68611602f58c8ca70cc40575ba3b04e",
"rounds": 1,
"type": "eq",
"annotations": true
},
Implement rendering polyline/polygon annotations without appearance stream
2021-04-28 02:02:20 +09:00
{ "id": "annotation-polyline-polygon-without-appearance",
"file": "pdfs/annotation-polyline-polygon-without-appearance.pdf",
"md5": "b776937148e9f7c4de6bea552e23b92f",
"rounds": 1,
"annotations": true,
"type": "eq"
},
Button widget annotations: implement support for pushbuttons
2017-11-21 07:00:19 +09:00
{ "id": "issue4872",
"file": "pdfs/issue4872.pdf",
"md5": "21c6cbc682140d6f6017bbeb45892053",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"annotations": true
},
Bug 1661226 - Push button are not rendered with renderInteractiveForms enabled
2020-08-27 03:26:18 +09:00
{ "id": "issue4872-forms",
"file": "pdfs/issue4872.pdf",
"md5": "21c6cbc682140d6f6017bbeb45892053",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq",
"forms": true
},
Improve robustness of stream parser (invalid length) When the parser finds a stream, it retrieves the Length from the stream dictionary and advances the lexer to the offset as specified in Length. If this Length is incorrect, the lexer could end up anywhere. When the lexer gets in an invalid state, it could throw errors. For example, in issue 6108, the lexer ends up inside the stream data. This stream has the ASCIIHexDecode filter, so all characters are made up from ASCII characters, and the lexer interprets it as a command token. Tokens cannot be longer than 127 bytes, so eventually 128 bytes are consumed and the lexer throws "Command token too long" error. Another possible error is "Illegal character: 41" when the lexer happens to end up at a ')' due to the length mismatch. These problems are solved by catching lexer errors and recovering the parser via the existing stream length detection branch.
2015-07-11 19:15:43 +09:00
{ "id": "issue6108",
"file": "pdfs/issue6108.pdf",
"md5": "8961cb55149495989a80bf0487e0f076",
"rounds": 1,
"type": "load"
Replace `getAll` with `getKeys` in `PartialEvaluator_hasBlendModes` to speed up loading of badly generated PDF files (issue 6961) Some bad PDF generators, in particular "Scribus PDF", duplicates resources *a lot* at various levels of the PDF files. This can lead to `PartialEvaluator_hasBlendModes` taking an unreasonable amount of time to complete. The reason is that the current code is using `Dict_getAll`, which recursively dereferences *all* indirect objects, which can be really slow. This patch instead uses `Dict_getKeys`, and then manually looks up only the necessary indirect objects. I've added the PDF file as a `load` test. The most important thing here is probably to ensure that the file remains available in the repo, and the comment should help reduced the chance of regressions. (Note that locally, the `load` test times out without this patch, but we cannot really assume that that always happens.) Fixes 6961.
2016-02-10 01:09:17 +09:00
},
Re-enable the `issue6961` test-case (issue 7112)
2021-02-02 18:31:16 +09:00
{ "id": "issue6961",
"file": "pdfs/issue6961.pdf",
"md5": "a80e4357a8fda758d96c2c76f2980b03",
"link": false,
"rounds": 1,
"lastPage": 1,
Don't double apply a group xobject's bbox. In `beginGroup` we create a new canvas that is the size of the bounding box and we translate it to the offset. This means we don't need to also apply the bounding box during `paintFormXObjectBegin`. This improves #6961 quite a bit, but it still is missing the indention in the ruler.
2021-11-06 06:50:48 +09:00
"type": "eq"
Re-enable the `issue6961` test-case (issue 7112)
2021-02-02 18:31:16 +09:00
},
Fix for descent calculation while reading font hhea headers
2016-03-03 11:10:15 +09:00
{ "id": "zero_descent",
"file": "pdfs/zero_descent.pdf",
"md5": "32805ab28be1d0e91d27d9742c66eccf",
"link": false,
"rounds": 1,
"lastPage": 1,
"type": "text"
Fix getTextContent evaluation to only apply TJ horizontal offsets using numeric items/args While the array argument to TJ should only contain strings and numbers, other unfortunate items are found in PDFs in the wild, e.g.: [(Grandes) 0.0 Tc -250.0 (Client\350les,) 0.0 Tc -250.0 (Financements) 0.0 Tc -250.0 (et) 0.0 Tc -250.0 (March\351s) ] TJ getOperatorList already properly ignores any non-string, non-numeric values in TJ arrays; without this patch to getTextContent, returned text items can have NaN widths due to calculations being applied to those non-numeric values.
2016-10-13 20:47:17 +09:00
},
Fix non-standard quadpoints orders for annotations This change requires us to use valid quadpoints arrays in the existing unit tests too due to the normalization.
2020-12-06 05:27:38 +09:00
{ "id": "quadpoints",
"file": "pdfs/quadpoints.pdf",
"md5": "aadbc9bf826b4604c49a994fc8cd72c1",
"rounds": 1,
"type": "eq",
"annotations": true
},
Fix getTextContent evaluation to only apply TJ horizontal offsets using numeric items/args While the array argument to TJ should only contain strings and numbers, other unfortunate items are found in PDFs in the wild, e.g.: [(Grandes) 0.0 Tc -250.0 (Client\350les,) 0.0 Tc -250.0 (Financements) 0.0 Tc -250.0 (et) 0.0 Tc -250.0 (March\351s) ] TJ getOperatorList already properly ignores any non-string, non-numeric values in TJ arrays; without this patch to getTextContent, returned text items can have NaN widths due to calculations being applied to those non-numeric values.
2016-10-13 20:47:17 +09:00
{ "id": "operator-in-TJ-array",
"file": "pdfs/operator-in-TJ-array.pdf",
"md5": "dfe0f15a45be18eca142adaf760984ee",
"link": false,
"rounds": 1,
"type": "text"
Consitently apply textAdvanceScale during building of textContentItems for improved highlighting. Fixes #7878.
2016-12-07 07:07:16 +09:00
},
{ "id": "issue7878",
"file": "pdfs/issue7878.pdf",
"md5": "59194e30037e8c09ae846ddd0ace4c81",
"link": false,
"rounds": 1,
"type": "text"
Font ascent descent calculation fix
2017-02-11 15:25:05 +09:00
},
{ "id": "font_ascent_descent",
"file": "pdfs/font_ascent_descent.pdf",
"md5": "c0048a7735010002b998c112335e47bf",
"rounds": 1,
"type": "eq"
Handle cff fonts with erroneous stackSize
2017-03-07 09:17:27 +09:00
},
{ "id": "issue8097",
"file": "pdfs/issue8097_reduced.pdf",
"md5": "ced0e2d88cfd5b4d3a55d937ea288af1",
"rounds": 1,
"type": "eq"
Implement JBIG2 halftone regions and pattern dictionaries
2017-08-08 21:38:29 +09:00
},
Improve performance of reused patterns. Bug 1721218 has a shading pattern that was used thousands of times. To improve performance of this PDF: - add a cache for patterns in the evaluator and only send the IR form once to the main thread (this also makes caching in canvas easier) - cache the created canvas radial/axial patterns - for shading fill radial/axial use the pattern directly instead of creating temporary canvas
2021-07-22 04:27:39 +09:00
{ "id": "bug1721218_reduced",
"file": "pdfs/bug1721218_reduced.pdf",
"md5": "20ee3e9500d8f5f5e532ec2edfaaaaaa",
"rounds": 1,
"type": "eq"
},
Implement JBIG2 halftone regions and pattern dictionaries
2017-08-08 21:38:29 +09:00
{ "id": "pr8491",
"file": "pdfs/pr8491.pdf",
"md5": "36ea2e28cd77e9e70731f574ab27cbe0",
"rounds": 1,
"link": true,
"type": "eq"
CCITTFaxStream problem when EndOfBlock is false
2017-09-20 04:19:40 +09:00
},
{ "id": "ccitt_EndOfBlock_false",
"file": "pdfs/ccitt_EndOfBlock_false.pdf",
"md5": "ce718efe601cd7491dd00651b4790329",
"rounds": 1,
"type": "eq"
Removed Extraneous Matrix Check in CalRGB Conversion
2018-08-03 02:16:42 +09:00
},
{ "id": "issue9940",
"file": "pdfs/issue9940.pdf",
"md5": "6ffef210c4b6cfe423e20430d8af168a",
"rounds": 1,
"link": false,
"type": "eq"
Fix text spacing with vertical fonts. #7687 and #11526. When the writing mode is vertical, we have to reverse the sign of spacing since we are subtracting it from current.y. We have to add it to current.y. See 9.4.4 Text Space Details, https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1694762
2020-01-27 11:03:27 +09:00
},
{ "id": "issue11526",
"file": "pdfs/issue11526.pdf",
"md5": "9babc771fc8792f43e4ada46b0daff8c",
"rounds": 1,
"lastPage": 1,
"link": true,
"type": "eq"
Fix the vertical writing mode with horizontal scaling. #11555. It is not valid to multiply textHScale when the writing mode is vertical. See 9.4.4 Text Space Details, https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1694762
2020-01-31 23:22:54 +09:00
},
{ "id": "issue11555",
"file": "pdfs/issue11555.pdf",
"md5": "f84ce8b7414f6a18e75a6ce69c902501",
"rounds": 1,
"type": "eq"
Implement resetting of created streams for annotations
2020-09-12 23:52:38 +09:00
},
{ "id": "issue12337",
"file": "pdfs/issue12337.pdf",
"md5": "9165772d5b860bcbcc2478f32e311eb0",
"rounds": 2,
"lastPage": 1,
"type": "fbf"
Make sure that Popup is rendered next to trigger for textAnnotation
2020-11-03 15:44:21 +09:00
},
{ "id": "pr12564",
"file": "pdfs/pr12564.pdf",
"md5": "24a19949a2541b960363832cf141f2f2",
"rounds": 1,
"type": "eq",
"annotations": true
set font size and color on annotation layer use the default appearance to set the font size and color of a text annotation widget
2021-01-22 06:33:43 +09:00
},
{
"id": "pr12828",
"file": "pdfs/pr12828.pdf",
"md5": "e44d364fba2f146aed04f9d9abbb0f28",
"rounds": 1,
"type": "eq",
"forms": true
fix initial state of checkboxes in display layer (#12904) consider the export value when multiple checkboxes have the same name
2021-02-12 19:22:54 +09:00
},
{
"id": "issue12716",
"file": "pdfs/issue12716.pdf",
"md5": "9bdc9c552bcfccd629f5f97385e79ca5",
"rounds": 1,
"link": true,
"type": "eq",
"forms": true,
"lastPage": 1
XFA - Add the possibily to layout and measure text - some containers doesn't always have their 2 dimensions and those dimensions re based on contents; - so in order to measure text, we must get the glyph widths (for the xfa fonts) before starting the layout; - implement a word-wrap algorithm; - handle font change during text layout.
2021-06-15 02:16:42 +09:00
},
Generate test images at different output scales. This will default to generating test images at the device pixel ratio of the machine the tests are created on unless the test explicitly defines and output scale using the `outputScale` setting. This makes the test look visually like they would on the machine they are running on. It also allows us to test different output scales.
2022-02-08 07:40:21 +09:00
{
"id": "issue12716-hidpi",
"file": "pdfs/issue12716.pdf",
"md5": "9bdc9c552bcfccd629f5f97385e79ca5",
"rounds": 1,
"link": true,
"type": "eq",
"forms": true,
"lastPage": 1,
"outputScale": 2,
"about": "This tests draws to another canvas for the button, so it's a good test to ensure output scale is working."
},
XFA - Add the possibily to layout and measure text - some containers doesn't always have their 2 dimensions and those dimensions re based on contents; - so in order to measure text, we must get the glyph widths (for the xfa fonts) before starting the layout; - implement a word-wrap algorithm; - handle font change during text layout.
2021-06-15 02:16:42 +09:00
{ "id": "xfa_issue13500",
"file": "pdfs/xfa_issue13500.pdf",
"md5": "b81274a19f5a95c1466db3648f1be491",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq"
Let `Lexer.getObj` return a dummy-`Cmd` for commands that start with a non-visible ASCII character (issue 13999) This way we avoid breaking badly generated PDF documents where a non-visible ASCII character is "glued" to a valid command.
2021-09-12 01:29:31 +09:00
},
{ "id": "issue13999",
"file": "pdfs/issue13999.pdf",
"md5": "8829c76887e7827390e9a5f73cab23f2",
"link": true,
"rounds": 1,
"lastPage": 1,
"type": "eq"
Annotation - For checkboxes, get field value from AS (if any) instead of V (bug 1722036) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1722036. - AS and V should share the same value for checkbox: it's at least what the specs say; - the pdf in the above bug opens correctly in Acrobat so it likely means that AS is chosen over V.
2021-09-17 19:41:50 +09:00
},
{ "id": "bug1722036",
"file": "pdfs/bug1722036.pdf",
"md5": "bbc7f62ca85609c97069bd3ce2658288",
"rounds": 1,
"link": true,
"forms": true,
"type": "eq"
[api-minor] Add basic support for RTL text-content in PopupAnnotations (issue 14046) In order to implement this, we utilize the existing `bidi` function to infer the text-direction of /T and /Contents entries. While this may not be perfect in cases where one PopupAnnotation mixes LTR and RTL languages, it should work well enough in most cases. To avoid having to add *two new* properties in lots of annotations, supplementing the existing `title`/`contents`-properties, this patch instead re-factors the existing code such that the properties are replaced by Objects (containing `str` and `dir`). *Please note:* In order avoid breaking existing third-party implementations, `GENERIC`-builds of the PDF.js library will still provide the old `title`/`contents`-properties on annotations returned by `PDFPageProxy.getAnnotations`.
2021-09-25 00:30:56 +09:00
},
{ "id": "issue14046",
"file": "pdfs/issue14046.pdf",
"md5": "dbb5d4e284ca9cc3219e04af6ce64e13",
"rounds": 1,
"type": "eq",
"annotations": true
Annotation - Some checkboxes have an empty N dictionary - it aims to fix #14021; - the N dict is empty here so just create a default one; - it implies that the checked checkbox has no appearance so create a default one too in order to print it; - in the pdf in the issue, a checked box is not printed because it has no default appearance so we need to guess its appearance from its state.
2021-09-17 22:31:22 +09:00
},
{ "id": "issue14021",
"file": "pdfs/issue14021.pdf",
"md5": "d18aa84135ce985c70a8f56306ecb95f",
"link": true,
"rounds": 1,
"firstPage": 2,
"lastPage": 2,
"type": "eq",
"forms": true
},
{ "id": "issue14021-storage",
"file": "pdfs/issue14021.pdf",
"md5": "d18aa84135ce985c70a8f56306ecb95f",
"link": true,
"rounds": 1,
"firstPage": 2,
"lastPage": 3,
"type": "eq",
"print": true,
"annotationStorage": {
"148R": {
"value": true
},
"138R": {
"value": true
},
"139R": {
"value": true
}
}
Annotation - Use border and background colors from MK dictionary - it aims to fix #13003; - set the bg and fg colors as they're in the pdf; - put a transparent overlay to help to see the fields.
2021-09-19 03:22:29 +09:00
},
{ "id": "issue13003",
"file": "pdfs/issue13003.pdf",
"md5": "a4c00bd6456d3c16b9bd44957caa4ab6",
"rounds": 1,
"type": "eq",
"annotations": true
XFA - Embedded image is missing
2021-10-15 18:46:28 +09:00
},
{ "id": "xfa_issue14144",
"file": "pdfs/xfa_issue14144.pdf",
"md5": "6a0e99edcf31e815dd0e1395e8dc15f2",
"link": true,
"rounds": 1,
"enableXfa": true,
"type": "eq",
"lastPage": 1
XFA - Fix xfaLink class to make links work (bug 1735738) There were some links not working in some XFA files,I realized that the anchor tag that contains the link has an inline display and couldn't receive any height, solved this by adding a "position: absolute". Tested with two different files in Firefox Nightly and Chrome and now all links are working perfectly fine. Added reftest to avoid future regressions
2021-10-19 00:28:42 +09:00
},
{ "id": "xfa_bug1735738",
"file": "pdfs/xfa_bug1735738.pdf",
"md5": "7aa91f6681798c48e0c9d9836ed30742",
"enableXfa": true,
"link": true,
"rounds": 1,
"type": "eq"
Use positive dimensions for text chunks in the text layer (issue #14415).
2022-01-05 05:36:25 +09:00
},
{ "id": "issue14415",
"file": "pdfs/issue14415.pdf",
"md5": "fa306a250a3d37fe0e7a4b3bba51c91e",
"type": "text"
Ignore Annotations with empty /Rect-entries in the display-layer (issue 14438) This prevents the `BaseSVGFactory.create`-method from throwing, and thus preventing any remaining Annotations (on the page) from rendering in corrupt documents.
2022-01-11 21:43:16 +09:00
},
{ "id": "issue14438",
"file": "pdfs/issue14438.pdf",
"md5": "c4f5a21bbd6567fe08583fc9d3149a38",
"rounds": 1,
"type": "eq",
"annotations": true
Font renderer - get int8 instead of uint8 in composite glyphes (bug 1749563) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1749563; - use some helper functions to get (u|i)int** values in buffer: it helps to have a clearer code; - in composite glyphes the translations values with a transformations are signed so consequently get some int8 instead of uint8; - add few TODOs.
2022-01-16 07:41:18 +09:00
},
{ "id": "bug1749563",
"file": "pdfs/bug1749563.pdf",
"md5": "11294f6071a8dcc25b0e18953cee68fa",
"rounds": 1,
"link": true,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
Remove the invisible format marks from the text chunks - it aims to fix issue #9186.
2022-01-24 07:04:18 +09:00
},
{ "id": "issue9186",
"file": "pdfs/issue9186.pdf",
"md5": "d151857bb724ab9a291704a45a0b5d7f",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "text"
Take into account all rotations before comparing glyph positions - it aims to fix #14497; - previously, only rotations with an angle 0, 90, 180 or 270 were taken into account; - so generalize to any angle but keep the fast path for 0, 90, ... because they're likely more common than anything else.
2022-01-26 23:35:46 +09:00
},
{ "id": "issue14497",
"file": "pdfs/issue14497.pdf",
"md5": "7f795a92caa612117b6928f8bb4c5b65",
"rounds": 1,
"type": "text"
[api-minor] Annotations - Adjust the font size in text field in considering the total width (bug 1721335) - it aims to fix #14502 and bug 1721335; - Acrobat and Pdfium do the same; - it'll avoid to have truncated data when printed; - change the factor to compute font size in using field height: lineHeight = 1.35*fontSize - this is the value used by Acrobat. - in order to not have truncated strings on the bottom, add few basic metrics for standard fonts.
2022-01-28 06:51:30 +09:00
},
{ "id": "issue14052",
"file": "pdfs/issue14502.pdf",
"md5": "7085cdc31243ab0b979f0c5fa151e491",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"27R": {
"value": "Hello PDF.js World"
},
"28R": {
"value": "PDF.js PDF.js PDF.js PDF.js\nPDF.js PDF.js PDF.js PDF.js\nPDF.js PDF.js PDF.js PDF.js\nPDF.js PDF.js PDF.js PDF.js"
},
"29R": {
"value": "PDF.js"
},
"30R": {
"value": "PDF.js PDF.js PDF.js"
}
}
[Search] Some matches were incorrectly shifted because of some '-\n' - it aims to fix #14562; - 'X-\n' were not correctly positioned; - when X is a diacritic (e.g. in "sä-\n", which is decomposed into "sa¨-\n") we must handle both things: - diacritics on the one hand; - "-\n" on the other hand.
2022-02-14 00:55:56 +09:00
},
{ "id": "issue14562",
"file": "pdfs/issue14562.pdf",
"md5": "565b0a1e46a32e907837506a10d25277",
"rounds": 1,
"link": true,
"type": "other"
Fix some issues with lineWidth < 1 after transform (bug 1753075, bug 1743245, bug 1710019) - it aims to fix: - https://bugzilla.mozilla.org/show_bug.cgi?id=1753075; - https://bugzilla.mozilla.org/show_bug.cgi?id=1743245; - https://bugzilla.mozilla.org/show_bug.cgi?id=1710019; - issue #13211; - issue #14521. - previously we were trying to adjust lineWidth to have something correct after the current transform is applied but this approach was not correct because finally the pixel is rescaled with the same factors in both directions. And sometimes those factors must be different (see bug 1753075). - So the idea of this patch is to apply a scale matrix to the current transform just before setting lineWidth and stroking. This scale matrix is computed in order to ensure that after transform, a pixel will have its two thickness greater than 1.
2022-02-06 06:33:54 +09:00
},
{ "id": "bug1753075",
"file": "pdfs/bug1753075.pdf",
"md5": "12716fa2dc3e0b3a61d88fef10abc7cf",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue13211",
"file": "pdfs/issue13211.pdf",
"md5": "d193853e8a123dc50eeea593a4150b60",
"rounds": 1,
"type": "eq"
[text selection] Add the whitespaces present in the pdf in the text chunk - it aims to fix issue #14627; - the basic idea of the recent text refactoring was to only consider the rendered visible whitespaces. But sometimes, the heuristics aren't correct and although some whitespaces are in the text stream they weren't in the text chunks because they were too small. Hence we added some exceptions, for example, we always add a whitespace when it is between two non-whitespace chars but only when in the same Tj. So basically, this patch removes the constraint to have the chars in the same Tj (in using a circular buffer to save the two last chars) but don't add a space when the visible space is really too small (hence `NOT_A_SPACE_FACTOR`).
2022-03-22 06:10:46 +09:00
},
{ "id": "issue14627",
"file": "pdfs/issue14627.pdf",
"md5": "5d1bfcc3b3130bfa7e33e43990e2213a",
"rounds": 1,
"type": "text"
[Annotations] Some annotations can have their values stored in the xfa:datasets - it aims to fix #14685; - add a basic object to get values from the parsed datasets; - these annotations don't have an appearance so we must create one when printing or saving.
2022-04-01 02:18:30 +09:00
},
{ "id": "issue14685",
"file": "pdfs/issue14685.pdf",
"md5": "2c608203b9b1d13455f0b1d9cebc9515",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue14685-print",
"file": "pdfs/issue14685.pdf",
"md5": "2c608203b9b1d13455f0b1d9cebc9515",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"150R": {
"value": "Hello PDF.js World"
}
}
Improve performances with image masks (bug 857031) - it's the second part of the fix for https://bugzilla.mozilla.org/show_bug.cgi?id=857031; - some image masks can be used several times but at different positions; - an image need to be pre-process before to be rendered: * rescale it; * use the fill color/pattern. - the two operations above are time consuming so we can cache the generated canvas; - the cache key is based on the current transform matrix (without the translation part) and the current fill color when it isn't a pattern. - the rendering of the pdf in the above bug is really faster than without this patch.
2022-04-13 22:44:33 +09:00
},
{ "id": "bug857031",
"file": "pdfs/bug857031.pdf",
"md5": "f11ecd7f75675e0cafbc9880c1a586c7",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
Don't clip when the clip path is empty (issue #12306)
2022-04-18 04:59:17 +09:00
},
{ "id": "issue12306",
"file": "pdfs/issue12306.pdf",
"md5": "7fd05ba56791238b5a60adc6cc0e7a22",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
Use integer coordinates when drawing images (bug 1264608, issue #3351) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1264608; - it's only a partial fix for #3351; - some tiled images have some spurious white lines between the tiles. When the current transform is applyed the corners of an image can have some non-integer coordinates leading to some extra transparency added to handle that. So with this patch the current transform is applied on the point and on the dimensions in order to have at the end only integer values.
2022-04-28 23:25:47 +09:00
},
{ "id": "issue3351.1",
"file": "pdfs/issue3351.1.pdf",
"md5": "4216245a5f18bb3eac80575ccf0b272d",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue3351.2",
"file": "pdfs/issue3351.2.pdf",
"md5": "fa3fd1659c409c7824ef8838c3071efc",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
},
{ "id": "issue3351.3",
"file": "pdfs/issue3351.3.pdf",
"md5": "60e2f2c480b6bc0e7f726743c6896520",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq"
Display background when printing or saving a text widget (issue #14928)
2022-05-18 06:10:02 +09:00
},
{ "id": "issue14928",
"file": "pdfs/issue14928.pdf",
"md5": "9687feb927eeb1b2a6f0794ea00f5c60",
"rounds": 1,
"link": true,
"lastPage": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"1483R": {
"value": "05/17/2022"
}
}
[JS] Format all the fields if any when the document is open (bug 1766987) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1766987.
2022-05-22 21:37:17 +09:00
},
{ "id": "bug1766987",
"file": "pdfs/bug1766987.pdf",
"md5": "3ce134ead03d6158c3e8207453dcd21d",
"rounds": 1,
"link": true,
"type": "other"
Set the text fields font size based on their height - right now we're using the font size from the pdf itself but we use an other font in the annotation layer. So this size doesn't really make sense and leads to bad rendering (see pdf in #14928); - use a sans-serif font for the fields containing text (fix issue #14736); - remove useless padding in text-based fields (fix issue #14301); - text fields allow/disallow scrolling bars (see bit 24 in Ff entry), so use this value to hide/show scrollbars in annotation layer.
2022-05-19 22:12:28 +09:00
},
{ "id": "issue14301",
"file": "pdfs/issue14301.pdf",
"md5": "9973936dcf8dd41daa62c04a4eb621f0",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq",
"forms": true,
"annotationStorage": {
"1832R": {
"value": "3"
},
"1827R": {
"value": "2"
},
"1808R": {
"value": "1"
}
}
[Annotations] Show buttons even if they've no actions - it's a regression from PR #14247: - before the PR, the button was rendered on the canvas whatever its status was; - after the PR, the button image has been moved in an other canvas so when the button is not renderable (because it has no actions) then the image is not added the HTML element. - the buttons in the pdf in bug 1737260 or in the pdf in #14308 were not visible - make the button always renderable but don't add the link element if it's useless.
2022-02-20 00:47:49 +09:00
},
Add (basic) support for Optional Content in Annotations Given that Annotations can also have an `OC`-entry, we need to take that into account when generating their operatorLists. Note that in order to simplify the patch the `getOperatorList`-methods, for the Annotation-classes, were converted to be `async`.
2022-06-24 21:39:08 +09:00
{ "id": "bug1737260-oc",
"file": "pdfs/bug1737260.pdf",
"md5": "8bd4f810d30972764b07ae141a4afbc4",
"rounds": 1,
"link": true,
"type": "eq",
"optionalContent": {
"191R": false
}
},
[Annotations] Show buttons even if they've no actions - it's a regression from PR #14247: - before the PR, the button was rendered on the canvas whatever its status was; - after the PR, the button image has been moved in an other canvas so when the button is not renderable (because it has no actions) then the image is not added the HTML element. - the buttons in the pdf in bug 1737260 or in the pdf in #14308 were not visible - make the button always renderable but don't add the link element if it's useless.
2022-02-20 00:47:49 +09:00
{ "id": "bug1737260",
"file": "pdfs/bug1737260.pdf",
"md5": "8bd4f810d30972764b07ae141a4afbc4",
"rounds": 1,
"link": true,
"type": "eq",
"annotations": true
Reset all the canvas states after rendering each annotations (#14105) - each annotation must be rendered independently of the others. So after having rendered each annotation, the canvas states are reset in order to have something clean to render the next one.
2022-06-07 00:24:38 +09:00
},
{ "id": "issue14105",
"file": "pdfs/issue14105.pdf",
"md5": "554174cd461180cbe46c137e846dd527",
"rounds": 1,
"link": true,
"type": "eq",
"annotations": true
Outline fields which are required (bug 1724918) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1724918; - it applies for both Acroform and XFA.
2022-06-07 21:44:17 +09:00
},
{ "id": "bug1724918",
"file": "pdfs/bug1724918.pdf",
"md5": "ab30269570c8ff2c9f8eb73fb376a081",
"rounds": 1,
"type": "eq",
"annotations": true
Rotate annotations based on the MK::R value (bug 1675139) - it aims to fix: https://bugzilla.mozilla.org/show_bug.cgi?id=1675139; - An annotation can be rotated (counterclockwise); - the rotation can be set in using JS.
2022-06-19 23:39:54 +09:00
},
{ "id": "bug1675139",
"file": "pdfs/bug1675139.pdf",
"md5": "052c2c3dcc7ef4d4ac622282cb0fb17a",
"rounds": 1,
"type": "eq",
"annotations": true
},
{ "id": "bug1675139-print",
"file": "pdfs/bug1675139.pdf",
"md5": "052c2c3dcc7ef4d4ac622282cb0fb17a",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"42R": {
"value": "pi/2"
},
"46R": {
"value": "3*pi/2",
"rotation": 180
},
"47R": {
"value": "0*pi/2"
},
"45R": {
"value": "pi"
},
"55R": {
"value": "C",
"rotation": 90
},
"52R": {
"value": "Yes"
},
"56R": {
"rotation": 270
}
}
[Editor] Add support for printing newly added Ink annotations
2022-06-15 23:57:33 +09:00
},
{
"id": "tracemonkey-editor",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"lastPage": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"pdfjs_internal_editor_0": {
"annotationType": 3,
"color": [0, 0, 0],
"fontSize": 10,
"value": "Hello World",
"pageIndex": 0,
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
"rect": [67.5, 543, 119, 556.5],
"rotation": 0
[Editor] Add support for printing newly added Ink annotations
2022-06-15 23:57:33 +09:00
},
"pdfjs_internal_editor_1": {
"annotationType": 15,
"color": [255, 0, 0],
"thickness": 3,
Set `opacity` in the reference tests (PR 15219 follow-up) Without these changes in the manifest, the affected test-cases fail to render correctly.
2022-07-28 21:35:09 +09:00
"opacity": 1,
[Editor] Add support for printing newly added Ink annotations
2022-06-15 23:57:33 +09:00
"paths": [{
"bezier": [
1.5, 25.727771084724367, 2.8040804485100495, 27.031851533234402,
5.396811581133676, 23.25556095123241, 6, 22.727771084724367,
10.45407020558315, 18.830459654839103, 15.981183968598401,
16.364531104350363, 21, 13.227771084724367, 25.88795894206055,
10.172796745936523, 37.988543516372076, 5.739227568352277, 42,
1.7277710847243668
],
"points": [
1.5, 25.727771084724367, 5.225791198862495, 23.602568747729173,
4.012834511116397, 24.914722452856147, 6, 22.727771084724367, 21,
13.227771084724367, 37.71378602219673, 4.78737352236285,
31.828688421912233, 7.836451889039392, 42, 1.7277710847243668
]
}],
"pageIndex": 0,
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
"rect": [71.5, 534.5, 115, 562],
"rotation": 0
[Editor] Add support for printing newly added Ink annotations
2022-06-15 23:57:33 +09:00
}
}
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
},
{
"id": "tracemonkey-editor-rotation",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"lastPage": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"pdfjs_internal_editor_3": {
"annotationType": 3,
"color": [0, 0, 0],
"fontSize": 10,
"value": "Hello",
"pageIndex": 0,
"rect": [
96.34615384615385, 554.8461538461538, 119.12498076923077,
568.3461538461538
],
"rotation": 0
},
"pdfjs_internal_editor_4": {
"annotationType": 3,
"color": [0, 0, 0],
"fontSize": 10,
"value": "PDF",
"pageIndex": 0,
"rect": [
125.57692307692308, 533.5384615384615, 139.07692307692307,
553.5384807692308
],
"rotation": 90
},
"pdfjs_internal_editor_5": {
"annotationType": 3,
"color": [0, 0, 0],
"fontSize": 10,
"value": ".js",
"pageIndex": 0,
"rect": [
105.9615576923077, 535.0769230769231, 115.96153846153847,
548.5769230769231
],
"rotation": 180
},
"pdfjs_internal_editor_6": {
"annotationType": 3,
"color": [0, 0, 0],
"fontSize": 10,
"value": "world!",
"pageIndex": 0,
"rect": [
77.84615384615385, 531.682673076923, 91.34615384615385,
558.3461538461538
],
"rotation": 270
},
"pdfjs_internal_editor_21": {
"annotationType": 15,
"color": [0, 0, 0],
"thickness": 1,
Set `opacity` in the reference tests (PR 15219 follow-up) Without these changes in the manifest, the affected test-cases fail to render correctly.
2022-07-28 21:35:09 +09:00
"opacity": 1,
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
"paths": [
{
"bezier": [
0.5, 15.653846153846189, 0.5, 10.612792605955292,
2.221156193659856, 5.960961418318131, 2.221156193659856,
0.7371591421274406
],
"points": [
0.5, 15.653846153846189, 2.221156193659856, 0.7371591421274406
]
}
],
"pageIndex": 0,
"rect": [
416.53846153846155, 561.8076923076923, 419.41346388596753,
577.9615384615385
],
"rotation": 0
},
"pdfjs_internal_editor_23": {
"annotationType": 15,
"color": [0, 0, 0],
"thickness": 1,
Set `opacity` in the reference tests (PR 15219 follow-up) Without these changes in the manifest, the affected test-cases fail to render correctly.
2022-07-28 21:35:09 +09:00
"opacity": 1,
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
"paths": [
{
"bezier": [
0.5, 18.538461538461547, 0.5, 12.869221974582576,
3.9307267310416893, 5.207607308237302, 1.6538461538461537,
0.653846153846164
],
"points": [
0.5, 18.538461538461547, 2.434116685812059, 4.572198481030599,
1.9307532933714027, 9.17784944259592, 1.6538461538461537,
0.653846153846164
]
}
],
"pageIndex": 0,
"rect": [
390.00000000000006, 543.4615384615386, 409.0384615384616,
546.9134638859676
],
"rotation": 90
},
"pdfjs_internal_editor_25": {
"annotationType": 15,
"color": [0, 0, 0],
"thickness": 1,
Set `opacity` in the reference tests (PR 15219 follow-up) Without these changes in the manifest, the affected test-cases fail to render correctly.
2022-07-28 21:35:09 +09:00
"opacity": 1,
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
"paths": [
{
"bezier": [
0.5, 24.307692307692264, 0.5, 16.218230266280443,
1.6442331167367787, 8.976323168614734, 1.6442331167367787,
0.8509134145882982
],
"points": [
0.5, 24.307692307692264, 1.6442331167367787, 0.8509134145882982
]
}
],
"pageIndex": 0,
"rect": [
422.7788438063401, 515.7692307692307, 425.07692307692304,
540.576923076923
],
"rotation": 180
},
"pdfjs_internal_editor_27": {
"annotationType": 15,
"color": [0, 0, 0],
"thickness": 1,
Set `opacity` in the reference tests (PR 15219 follow-up) Without these changes in the manifest, the affected test-cases fail to render correctly.
2022-07-28 21:35:09 +09:00
"opacity": 1,
Support rotating editor layer - As in the annotation layer, use percent instead of pixels as unit; - handle the rotation of the editor layer in allowing editing when rotation angle is not zero; - the different editors are rotated counterclockwise in order to be usable when the main page is itself rotated; - add support for saving/printing rotated editors.
2022-06-23 22:47:45 +09:00
"paths": [
{
"bezier": [
0.5, 32.96153846153845, 4.262222952239026, 32.96153846153845,
2.8076923076923075, 4.355429108316972, 2.8076923076923075,
0.6538461538461462
],
"points": [
0.5, 32.96153846153845, 2.9761779872739975, 7.263528385840449,
3.0646797609357885, 18.195785915618856, 2.8076923076923075,
0.6538461538461462
]
}
],
"pageIndex": 0,
"rect": [
425.6538461538462, 553.7403822678785, 459.11538461538464,
557.7692307692307
],
"rotation": 270
}
}
[Annotation] A push button can have no action (bug 1778692)
2022-07-08 21:28:32 +09:00
},
{ "id": "bug1778692",
"file": "pdfs/bug1778692.pdf",
"md5": "8855414caaa04fbbdfad1545d1c8a8ae",
"rounds": 1,
"link": true,
"firstPage": 2,
"lastPage": 2,
"type": "eq",
"annotations": true
Fix wrong order of arguments when calling the CipherTransform ctor (bug 1782186)
2022-07-29 19:29:19 +09:00
},
{ "id": "bug1782186",
"file": "pdfs/bug1782186.pdf",
"password": "Hello",
"md5": "8505033d63625dfd77e90a3722b0c316",
"rounds": 1,
"type": "eq"
Fix OTS issue with empty index (#15289)
2022-08-09 05:04:14 +09:00
},
{ "id": "issue15289",
"file": "pdfs/issue15289.pdf",
"md5": "f3d20aee398e052ac3dce7cc030f50de",
"link": true,
"rounds": 1,
"firstPage": 1,
"lastPage": 1,
"type": "eq"
Initialize values in the path bounding box before flushing the operator list (bug 1791583) OperatorList.addOp can trigger a flush if it's required, hence the values passed to it must be correctly initialized in order to avoid some wrong values in the renderer. Because of that a clip path was considered as empty, nothing was clipped, hence the wrong rendering in bug 1791583.
2022-09-21 01:39:20 +09:00
},
{ "id": "bug1791583",
"file": "pdfs/bug1791583.pdf",
"md5": "1ff6badc865c9a5e9a0dc0b7131ffe28",
"link": true,
"rounds": 1,
"type": "eq"
Use all the current transform as key when caching some image for masks used with pattern fill (bug 1795263, #15573)
2022-10-14 20:14:13 +09:00
},
{ "id": "bug1795263",
"file": "pdfs/bug1795263.pdf",
"md5": "af708acbb22c6c9d268240dcf4a39809",
"rounds": 1,
"type": "eq"
[Form] Don't use field appearances when /NeedAppearances is set to true (bug 1796741) When a form isn't changed, we used the appearances we had in the file, but when /NeedAppearances is true, all the appearances have to be regenerated whatever they're.
2022-10-24 22:26:00 +09:00
},
{ "id": "bug1796741-print",
"file": "pdfs/bug1796741.pdf",
"md5": "d5167d1b0d1b840c9aa258b98ce4fa62",
"rounds": 1,
"type": "eq",
"print": true
[Annotation] Fix printing/saving for annotations containing some non-ascii chars and with no fonts to handle them (bug 1666824) - For text fields * when printing, we generate a fake font which contains some widths computed thanks to an OffscreenCanvas and its method measureText. In order to avoid to have to layout the glyphs ourselves, we just render all of them in one call in the showText method in using the system sans-serif/monospace fonts. * when saving, we continue to create the appearance streams if the fonts contain the char but when a char is missing, we just set, in the AcroForm dict, the flag /NeedAppearances to true and remove the appearance stream. This way, we let the different readers handle the rendering of the strings. - For FreeText annotations * when printing, we use the same trick as for text fields. * there is no need to save an appearance since Acrobat is able to infer one from the Content entry.
2022-10-19 00:07:47 +09:00
},
{ "id": "ascii_print_textfields",
"file": "pdfs/textfields.pdf",
"md5": "5f743ca838ff9b7a286dbe52002860b7",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"32R": {
"value": "Hello World"
},
"35R": {
"value": "Hello World"
},
"38R": {
"value": "Hello World"
},
"34R": {
"value": "Hello World"
},
"37R": {
"value": "Hello World"
},
"40R": {
"value": "Hello World"
},
"33R": {
"value": "Hello World\nDlrow Olleh\nHello World"
},
"36R": {
"value": "Hello World\nDlrow Olleh\nHello World"
},
"39R": {
"value": "Hello World\nDlrow Olleh\nHello World"
}
}
},
{ "id": "arabic_print_textfields",
"file": "pdfs/textfields.pdf",
"md5": "5f743ca838ff9b7a286dbe52002860b7",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"32R": {
"value": "مرحبا بالعالم"
},
"35R": {
"value": "مرحبا بالعالم"
},
"38R": {
"value": "مرحبا بالعالم"
},
"34R": {
"value": "مرحبا بالعالم"
},
"37R": {
"value": "مرحبا بالعالم"
},
"40R": {
"value": "مرحبا بالعالم"
},
"33R": {
"value": "مرحبا بالعالم\nملاعلاب ابحرم\nمرحبا بالعالم"
},
"36R": {
"value": "مرحبا بالعالم\nملاعلاب ابحرم\nمرحبا بالعالم"
},
"39R": {
"value": "مرحبا بالعالم\nملاعلاب ابحرم\nمرحبا بالعالم"
}
}
},
{ "id": "ascii_save_print_textfields",
"file": "pdfs/textfields.pdf",
"md5": "5f743ca838ff9b7a286dbe52002860b7",
"rounds": 1,
"type": "eq",
"save": true,
"print": true,
"annotationStorage": {
"32R": {
"value": "Hello World"
},
"35R": {
"value": "Hello World"
},
"38R": {
"value": "Hello World"
},
"34R": {
"value": "Hello World"
},
"37R": {
"value": "Hello World"
},
"40R": {
"value": "Hello World"
},
"33R": {
"value": "Hello World\nDlrow Olleh\nHello World"
},
"36R": {
"value": "Hello World\nDlrow Olleh\nHello World"
},
"39R": {
"value": "Hello World\nDlrow Olleh\nHello World"
}
}
},
{ "id": "arabic_save_print_textfields",
"file": "pdfs/textfields.pdf",
"md5": "5f743ca838ff9b7a286dbe52002860b7",
"rounds": 1,
"type": "eq",
"save": true,
"print": true,
"annotationStorage": {
"32R": {
"value": "مرحبا بالعالم"
},
"35R": {
"value": "مرحبا بالعالم"
},
"38R": {
"value": "مرحبا بالعالم"
},
"34R": {
"value": "مرحبا بالعالم"
},
"37R": {
"value": "مرحبا بالعالم"
},
"40R": {
"value": "مرحبا بالعالم"
},
"33R": {
"value": "مرحبا بالعالم\nملاعلاب ابحرم\nمرحبا بالعالم"
},
"36R": {
"value": "مرحبا بالعالم\nملاعلاب ابحرم\nمرحبا بالعالم"
},
"39R": {
"value": "مرحبا بالعالم\nملاعلاب ابحرم\nمرحبا بالعالم"
}
}
},
{ "id": "freetext_no_appearance",
"file": "pdfs/freetext_no_appearance.pdf",
"md5": "1dc519c06f1dc6f6e594f168080dcde9",
"rounds": 1,
"type": "eq"
},
{ "id": "freetext_print_no_appearance",
"file": "pdfs/freetext_no_appearance.pdf",
"md5": "1dc519c06f1dc6f6e594f168080dcde9",
"rounds": 1,
"type": "eq",
"print": true
},
{
"id": "tracemonkey-multi-lang-editors",
"file": "pdfs/tracemonkey.pdf",
"md5": "9a192d8b1a7dc652a19835f6f08098bd",
"rounds": 1,
"lastPage": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"pdfjs_internal_editor_0": {
"annotationType": 3,
"color": [255, 0, 0],
"fontSize": 10,
"value": "Hello World",
"pageIndex": 0,
"rect": [67.5, 143, 119, 156.5],
"rotation": 0
},
"pdfjs_internal_editor_1": {
"annotationType": 3,
"color": [0, 255, 0],
"fontSize": 10,
"value": "مرحبا بالعالم",
"pageIndex": 0,
"rect": [67.5, 243, 119, 256.5],
"rotation": 0
},
"pdfjs_internal_editor_2": {
"annotationType": 3,
"color": [0, 0, 255],
"fontSize": 10,
"value": "你好世界",
"pageIndex": 0,
"rect": [67.5, 343, 119, 356.5],
"rotation": 0
},
"pdfjs_internal_editor_3": {
"annotationType": 3,
"color": [255, 0, 255],
"fontSize": 10,
"value": "Hello World 你好世界 مرحبا بالعالم",
"pageIndex": 0,
"rect": [67.5, 443, 222, 456.5],
"rotation": 0
}
}
},
{
"id": "issue12233-arabic-print",
"file": "pdfs/issue12233.pdf",
"md5": "6099fc695fe018ce444752929d86f9c8",
"link": true,
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"23R": {
"value": "مرحبا بالعالم"
}
}
[JS] Handle correctly choice widgets where the display and the export values are different (issue #15815)
2022-12-13 08:07:45 +09:00
},
{
"id": "issue15815-print",
"file": "pdfs/issue15815.pdf",
"md5": "48b8b057954d5b773421ac03b7fcd738",
"rounds": 1,
"type": "eq",
"print": true,
"annotationStorage": {
"24R": {
"value": "x3"
}
}
},
{
"id": "issue15815-save-print",
"file": "pdfs/issue15815.pdf",
"md5": "48b8b057954d5b773421ac03b7fcd738",
"rounds": 1,
"type": "eq",
"save": true,
"print": true,
"annotationStorage": {
"24R": {
"value": "x2"
}
}
Strip out a reserved operator (9) from CFF char strings (fixes issue #15784)
2022-12-16 19:51:23 +09:00
},
{
"id": "issue15784",
"file": "pdfs/issue15784.pdf",
"md5": "6e4fce8e36d960955a7476b862f58939",
"rounds": 1,
"link": true,
"type": "eq"
[Annotation] Avoid to encrypt the appearance stream two times (bug 1815476)
2023-02-08 03:26:46 +09:00
},
{
"id": "bug1815476-save-print",
"file": "pdfs/bug1815476.pdf",
"md5": "476f77da5f9422ef86ea5f4531602e93",
"rounds": 1,
"type": "eq",
"save": true,
"print": true,
"annotationStorage": {
"88R": {
"value": "foo"
},
"87R": {
"value": "bar"
}
}
[Annotation] Take into account the stroke alpha for a FreeText without appearance
2023-02-08 05:16:14 +09:00
},
{
"id": "issue16021",
"file": "pdfs/issue16021.pdf",
"md5": "78a12254cac90ba5219a4c5555ea35ed",
"rounds": 1,
"type": "eq"
[Annotation] For choice widget, use the I entry instead of the V one (bug 1770750) It isn't really conform to the specifications but Acrobat is working like that...
2023-02-09 22:58:41 +09:00
},
{
"id": "bug1770750-annotations",
"file": "pdfs/bug1770750.pdf",
"md5": "01e6d77eac90b4b08d75240d3db2b826",
"rounds": 1,
"type": "eq",
"annotations": true
[Acroform] Use the full path to find the node in the XFA datasets where to store the value I noticed several 'Path not found' errors because of a field called #subform[2]. From the XFA specs, the hash is used for a class of elements in the template tree. When we're looking for a node in the datasets tree, it doesn't make sense to search for a class. Hence the path element starting with a hash are just skipped.
2023-02-23 06:08:21 +09:00
},
{
"id": "issue16081",
"file": "pdfs/issue16081.pdf",
"md5": "e890d55c9527a116431ebef3efb960ff",
"link": true,
"type": "other"
},
{
"id": "f1040_2022.pdf",
"file": "pdfs/f1040_2022.pdf",
"md5": "1eec7137e471a3d68a20855a04293b5b",
"link": true,
"type": "other"
Render large images even if they're larger than the canvas limits (bug 1720282) The idea is to encode large image in BMP format (which is very simple and doesn't require to compute any checksums) and then use createImageBitmap with a BMP blob (which doesn't suffer of the Canvas/ImageData limits). From a performance point of view, it isn't crazy (generating a large blob + decoding it on the main thread is really not ideal) but at least we've something to display which is a way better than a blank page (and one can notice that most of the time is spent in decoding the image from the pdf stream).
2023-02-21 01:35:41 +09:00
},
{
"id": "issue6741",
"file": "pdfs/issue6741.pdf",
"md5": "ddbe6ccc7ae414c7ffa6c4110536730d",
"rounds": 1,
"link": true,
"type": "eq"
},
{
"id": "issue8076",
"file": "pdfs/issue8076.pdf",
"md5": "4a866bff4209956a6cfa2e2c9456f421",
"rounds": 1,
"link": true,
"type": "eq"
[Annotation] Don't rotate an annotation when it has the NoRotate flag
2023-03-05 21:57:27 +09:00
},
{
"id": "annotation-link-text-popup-rotated-90",
"file": "pdfs/annotation-link-text-popup.pdf",
"md5": "4bbf56e81d47232de5f305124ab0ba27",
"rounds": 1,
"type": "eq",
"annotations": true,
"rotation": 90
},
{
"id": "annotation-link-text-popup-rotated-180",
"file": "pdfs/annotation-link-text-popup.pdf",
"md5": "4bbf56e81d47232de5f305124ab0ba27",
"rounds": 1,
"type": "eq",
"annotations": true,
"rotation": 180
},
{
"id": "annotation-link-text-popup-rotated-270",
"file": "pdfs/annotation-link-text-popup.pdf",
"md5": "4bbf56e81d47232de5f305124ab0ba27",
"rounds": 1,
"type": "eq",
"annotations": true,
"rotation": 270
Use appearance stream to render locked annotations (bug 1723568)
2023-03-07 20:58:59 +09:00
},
{
"id": "bug1723568",
"file": "pdfs/bug1723568.pdf",
"md5": "c5cc9f1e01d195b96eadf8be0a819578",
"rounds": 1,
"link": true,
"type": "eq",
"forms": true
Slightly modify the max width of a tracking space
2023-03-08 03:38:49 +09:00
},
{
"id": "issue16119",
"file": "pdfs/issue16119.pdf",
"md5": "76d680172c969c77c9fb650b3d822ad6",
"link": true,
"type": "other"
Apply transfer filters to any graphic commands
2023-03-06 18:57:05 +09:00
},
{
"id": "issue16114",
"file": "pdfs/issue16114.pdf",
"md5": "c04827ea33692e0f94a5e51716d9aa2e",
"rounds": 1,
"link": true,
"type": "eq"
Fix search in pdf a containing some UTF-32 characters (bug 1820909) Some chars were supposed to have a length equals to 1 but UTF-32 chars can be longuer.
2023-03-09 22:13:28 +09:00
},
[api-minor] Extend general transfer function support to browsers without `OffscreenCanvas` This patch extends PR 16115 to work in all browsers, regardless of their `OffscreenCanvas` support, such that transfer functions will be applied to general rendering (and not just image data). In order to do this we introduce the `BaseFilterFactory` that is then extended in browsers/Node.js environments, similar to all the other factories used in the API, such that we always have the necessary factory available in `src/display/canvas.js`. These changes help simplify the existing `putBinaryImageData` function, and the new method can easily be stubbed-out in the Firefox PDF Viewer. *Please note:* This patch removes the old *partial* transfer function support, which only applied to image data, from Node.js environments since the `node-canvas` package currently doesn't support filters. However, this should hopefully be fine given that: - Transfer functions are not very commonly used in PDF documents. - Browsers in general, and Firefox in particular, are the *primary* development target for the PDF.js library. - The FAQ only lists Node.js as *mostly* supported, see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support
2023-03-12 23:47:01 +09:00
{
"id": "issue16114-disable-isOffscreenCanvasSupported",
"file": "pdfs/issue16114.pdf",
"md5": "c04827ea33692e0f94a5e51716d9aa2e",
"rounds": 1,
"link": true,
"type": "eq",
"isOffscreenCanvasSupported": false
},
Fix search in pdf a containing some UTF-32 characters (bug 1820909) Some chars were supposed to have a length equals to 1 but UTF-32 chars can be longuer.
2023-03-09 22:13:28 +09:00
{
"id": "bug1820909",
"file": "pdfs/bug1820909.pdf",
"md5": "d95a83a868671a03cbf322f16b2e2b9d",
"link": true,
"type": "other"
Use the position of the previous xref stream if any when saving a pdf (bug 1823296)
2023-03-22 02:14:43 +09:00
},
{
"id": "bug1823296",
"file": "pdfs/bug1823296.pdf",
"md5": "f71e89ebe3d6e75e0c83ce41cd72df1f",
"link": true,
"type": "other"
Create a new chunk when the char is too rised compared to the previouse one
2023-03-28 19:00:53 +09:00
},
{
"id": "issue16221-text",
"file": "pdfs/issue16221.pdf",
"md5": "62d93c9b3aa4ba3af5446504632e78a5",
"rounds": 1,
"type": "text"
Thin whitespaces must have their own span
2023-03-29 00:48:09 +09:00
},
{
"id": "issue16224-text",
"file": "pdfs/issue16224.pdf",
"md5": "1aa34fbb2154f9a647c7fa9e90db0eff",
"rounds": 1,
"type": "text"
Apply HCM filters on annotations which have their own canvas (bug 1830850)
2023-05-02 23:37:49 +09:00
},
{
"id": "annotation-fileattachment-forced-colors-eq",
"file": "pdfs/annotation-fileattachment.pdf",
"md5": "d20ecee4b53c81b2dd44c8715a1b4a83",
"rounds": 1,
"pageColors": {
"background": "black",
"foreground": "#00FF00"
},
"annotations": true,
"type": "eq"
[Annotations] Draw readonly annotations on their own canvas and show the HTML elements when there is a JS interaction (issue #16384)
2023-05-05 03:08:32 +09:00
},
{
"id": "issue16384",
"file": "pdfs/issue16384.pdf",
"md5": "2a4695a9ce6243832a06e989f1dc6599",
"rounds": 1,
"link": true,
"forms": true,
"type": "eq"
Make something similar to Acrobat when Underline annotation has no appearance
2023-05-07 03:25:01 +09:00
},
{
"id": "issue14565",
"file": "pdfs/issue14565.pdf",
"md5": "ee0b064d227fe90a4795ff0c4dd0a47c",
"rounds": 1,
"annotations": true,
"type": "eq"
Compress the data when saving annotions CompressionStream API has been added in Firefox 113 (see https://bugzilla.mozilla.org/show_bug.cgi?id=1823619) hence we can use it to compress the streams with added/modified annotations.
2023-04-28 04:50:27 +09:00
},
{
"id": "multiline_compress",
"file": "pdfs/multiline.pdf",
"md5": "4727c7d1e4e5c7d45fded8ab7a2e05e5",
"rounds": 1,
"type": "eq",
"save": true,
"print": true,
"annotationStorage": {
"24R": {
"value": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz\nabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"
}
}
Sanitize the glyph bounding box - if the contours count is lower than -1, the glyph is really likely wrong so just remove it from the font; - if a contour has the repeat flag then repeats count mustn't be 0.
2023-05-21 20:42:11 +09:00
},
{
"id": "issue16300",
"file": "pdfs/issue16300.pdf",
"md5": "45ac5cd3a159a4e9152bc1fdb685750d",
"rounds": 1,
"link": true,
"type": "eq"
},
{
"id": "issue15813",
"file": "pdfs/issue15813.pdf",
"md5": "af5124ee1dbc39c679a903690958c5b2",
"rounds": 1,
"link": true,
"print": true,
"type": "eq"
Extract all the text of text annotations
2023-05-26 05:59:09 +09:00
},
{
"id": "issue16471",
"file": "pdfs/issue16471.pdf",
"md5": "8ac3720d6d3ddcc58e2eadab477fd81e",
"rounds": 1,
"link": true,
"forms": true,
"type": "eq"
[OTS] Remove cntrmask instruction with no stem in charstring (bug 1529502)
2023-05-29 00:47:04 +09:00
},
{
"id": "bug1529502",
"file": "pdfs/bug1529502.pdf",
"md5": "4830e765a3d6cb64d39b84de11178f6e",
"rounds": 1,
"type": "eq"
Font renderer - get int8 instead of uint8 in composite glyphes (bug 1749563) - it aims to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1749563; - use some helper functions to get (u|i)int** values in buffer: it helps to have a clearer code; - in composite glyphes the translations values with a transformations are signed so consequently get some int8 instead of uint8; - add few TODOs.
2022-01-16 07:41:18 +09:00
}
Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.
2011-06-19 10:09:21 +09:00
]
Reference in New Issue Copy Permalink