ENOENT: no such file or directory, lstat with # encoded in filename

#8928 actually resolved the issue #8907 I open couple days ago. However, when filenames contain an encoded # character (%23), current decoding process do not handled it.

Configuration:

• Web browser and its version: Electron 1.7.8
• Operating system and its version: Fedora 25
• PDF.js version: 1.9.617

Steps to reproduce the problem:

1. Open a locale file with an # encoded character file:///home/njakob/Foo%20Bar/document%23.pdf

What went wrong?

• The error ENOENT: no such file or directory, lstat is raised.

Issue is related to the decodeURI usage which ignore decoding of %23.

Solution should also cover cases were the # is inside the path such as file:///home/njakob/Foo%23/document.pdf.

[mukulmishra18]

If you try to decode any url that contains %23 in it, using decodeURIComponent then it will decode just fine. So I think this should solve the problem.

Also note that you are using chrome extension, so node_stream was never used, because it is intended to use in node environment. I will suggest to create a node app that uses pdf.js and see if problem still persists.

Edit: I would suggest to use console.log as much as you can to see if code really executing.

[shikhar-scs]

Also note that you are using chrome extension, so node_stream was never used, because it is intended to use in node environment. I will suggest to create a node app that uses pdf.js and see if problem still persists.

Thank you so much for this information and also for your help.