Chromium on Linux fails to save files

[tmcw]

So, I'm not an expert on the differences between Chrome and Chromium and any possible native fs difference between Mac, Linux, etc. but I've gotten reports from the field and can replicate locally in a Ubuntu VM that attempting to use browser-fs-access in Chromium on Ubuntu consistently produces AbortError failures:

This can be replicated on the demo as well as in my application. As far as I can tell, Chromium on Linux advertises support for the native filesystem API and breaks if you try to use it.

[tomayac]

Interesting, I can reproduce this, too. I need to investigate what might be causing this.

[tmcw]

Did some digging, seems like it tracks back to these issues: https://bugs.chromium.org/p/chromium/issues/detail?id=1264708#c10

And it looks like the solution is that Chromium/Linux requires the description parameter. Tested that and it seems to fix behavior. I think on the browser-fs-access side (assuming that Chromium doesn't fix its behavior), a solution would be either to make the description member of the options argument required, or to have a non-empty default value for Description.

[tomayac]

Oh, nice. This would be an easy fix. In meeting all of the rest of today, but will definitely look tomorrow.

[tomayac]

Confirmed working!