Command line doesn't URL-encode spaces in its arguments

[lokegustafsson]

Description

As said in the title, opening a pdf through the command line fails when the file name contains spaces. Instead of one tab with file:///home/loke/my%20file.pdf, one tab opens with file:///home/loke/my and another with file.pdf.

Steps to Reproduce

1. Use Linux? I am not sure about non-Linux equivalents to the command line brave
2. Locate some file on your system, here /home/loke/my file.pdf.
3. Execute and compare brave "file:///home/loke/my file.pdf" and brave "file:///home/loke/my%20file.pdf"

Actual result:

brave "file:///home/loke/my file.pdf" opens two tabs, file:///home/loke/my and file.pdf.
brave "file:///home/loke/my%20file.pdf" opens a single tab, file:///home/loke/my%20file.pdf.

Expected result:

I think that the first command should behave the same as the second one, that spaces in an argument should be automatically URL-encoded.

Reproduces how often:

This occurs every single time.

Brave version (brave://version info)

Brave | 0.69.132 Chromium: 77.0.3865.90 (Official Build) unknown (64-bit)
Revision | 58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830}
OS | Linux
(arch linux)