NW.js crashes when setting value of file input element

[cdog]

Issue Type

• Bug Report

• Feature Request

• Successfully reproduced against the latest version of NW.js?

Current/Missing Behavior

Trying to set file input value programmatically as shown in docs: https://github.com/nwjs/nw.js/wiki/Changes-to-dom#setting-value-of-file-input-element

var f = new File('/path/to/file', 'name');
var files = new FileList();
files.append(f);
document.getElementById('input0').files = files;

As soon as using new FileList(); or trying to append the file NW.js process crashes. Just try executing in the console:

new FileList();

new-filelist.mov

Expected/Proposed Behavior

Set the value of file input element.

Additional Info

• Operating System: MacOS and Ubuntu
• NW.js Version: nw@0.66.1-sdk, nw@0.67.1-sdk
• Repro Link: https://github.com/nwjs/nw.js/wiki/Changes-to-dom#setting-value-of-file-input-element
• Code snippet: see above
• Crash report:

[0831/011401.372552:ERROR:zip.cc(179)] Cannot open '/Users/<user>/.volta/tools/image/packages/nw/lib/node_modules/nw/nwjs/nwjs.app/Contents/Resources/app.nw': FILE_ERROR_NOT_FOUND: No such file or directory (2)
[0831/011401.373517:ERROR:zip.cc(179)] Cannot open '/Users/<user>/.volta/tools/image/packages/nw/lib/node_modules/nw/nwjs/package.nw': FILE_ERROR_NOT_FOUND: No such file or directory (2)
Received signal 11 SEGV_MAPERR 000000002405
 [0x00011c0bc059]
 [0x00011c014e83]
 [0x00011c0bbfb1]
 [0x7ff801a82dfd]
 [0x000000000004]
 [0x00011aaf4786]
 [0x00011aaf2861]
 [0x00011aaf1beb]
 [0x00011aaf0fbd]
 [0x00011a798156]
 [0x00011a797f2f]
 [0x00011a796304]
 [0x00011af4cc12]
 [0x00011af59109]
 [0x00011af562ec]
 [0x00011aeeffb1]
 [0x00011aef104d]
 [0x00011aef698d]
 [0x00011aef5f6b]
 [0x00011a718d88]
 [0x00011a718892]
 [0x00011a717d86]
 [0x0131f7f0fdf8]
[end of stack trace]
[0831/011410.062984:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063463:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063482:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063497:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063510:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063523:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063536:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063549:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063562:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063574:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063587:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063599:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063611:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063624:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063636:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063648:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063661:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063673:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063685:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063697:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063788:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063801:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063814:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063827:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.063840:ERROR:process_reader_mac.cc(308)] thread_get_state(4): (os/kern) invalid argument (4)
[0831/011410.064831:WARNING:process_reader_mac.cc(517)] multiple MH_EXECUTE modules (/usr/libexec/rosetta/runtime, /Library/Apple/usr/libexec/oah/libRosettaRuntime)
[0831/011410.065148:WARNING:process_reader_mac.cc(517)] multiple MH_EXECUTE modules (/usr/libexec/rosetta/runtime, /Users/<user>/.volta/tools/image/packages/nw/lib/node_modules/nw/nwjs/nwjs.app/Contents/Frameworks/nwjs Framework.framework/Versions/103.0.5060.114/Helpers/nwjs Helper (Renderer).app/Contents/MacOS/nwjs Helper (Renderer))
[0831/011410.203717:ERROR:exception_snapshot_mac.cc(139)] exception_thread not found in task

[ayushmanchhabra]

@cdog This is the expected behaviour from a Chromium standpoint. The FileList API is read only and it does not have the append() anymore. See https://stackoverflow.com/questions/74630989/why-use-domstringlist-rather-than-an-array/74641156#74641156 for more context.

We could either keep functionality as is or change upstream behaviour.

cc @rogerwang