Attach (recommended) or Link to PDF file here:
https://bitcoin.org/bitcoin.pdf

Configuration:
- Web browser and its version: all
- Operating system and its version: all
- PDF.js version: tested with 2.9.11, but most likely all versions
- Is a browser extension: no

Steps to reproduce the problem:
1. Type "a purely" (single space between "a" and "purely") - doesn't find anything
2. Type "a  purely" (two spaces between "a" and "purely") - finds the phrase

Sometimes even 3 spaces are necessary.

What is the expected behavior? (add screenshot)
![Screenshot from 2021-04-08 13-00-03](https://user-images.githubusercontent.com/6362989/114008903-57639a00-986b-11eb-903a-92bbebbd922b.png)

What went wrong? (add screenshot)
![Screenshot from 2021-04-08 13-01-53](https://user-images.githubusercontent.com/6362989/114008810-44e96080-986b-11eb-8232-f58a62ed7899.png)

This affects many PDFs because justify alignment is common enough.
fnt ladng faled, attet t reend *all* prevuly pared glyph.
    PartlEvaluatr.buldFntPath(
      th.fnt,
      /* glyph = */ tCacheValue,
      handler,
      th._evaluatrOptn
    );
  }
  ladType3Data(evaluatr, reurce, tak) {
    f (th.type3Laded) {
      return th.type3Laded;
    }
    f (!th.fnt.Type3Fnt) {
      thrw new Errr("Mut be a Type3 fnt.");
    }
     When parng Type3 glyph, alway gnre them f there are errr.
     Cared t the parng f e.g. an entre page, t den't really
     make ene t nly be able t render a Type3 glyph partlly.
    cnt type3Evaluatr = evaluatr.clne({ gnreErrr: fale });
    type3Evaluatr.parngType3Fnt = true;
    cnt tranlatedFnt = th.fnt,
      type3Dependence = th.type3Dependence;
    let ladCharPrcPrme = Prme.relve();
    cnt charPrc = th.dct.get("CharPrc");
    cnt fntReurce = th.dct.get("Reurce") || reurce;
    cnt charPrcOperatrLt = Object.create(null);
    cnt EtyBBx =
      !tranlatedFnt.bbx || ArrayEqual(tranlatedFnt.bbx, [0, 0, 0, 0]);
    fr (cnt key f charPrc.getKey()) {
      ladCharPrcPrme = ladCharPrcPrme.then(() => {