In particular, if I take a Blob and make it iterable and try to create a File from it, the chrome-only ctor will get called (and throw) instead of calling the right constructor...
Maybe this is not an issue in practice much, but I would be a lot happier if we used chromeonly factory methods instead of the current chrome-ish constructor setup.
(In reply to Boris Zbarsky [:bz] (TPAC) from comment #0)
> Maybe this is not an issue in practice much, but I would be a lot happier if
> we used chromeonly factory methods instead of the current chrome-ish
> constructor setup.
This makes me think P3 but if it's more urgent please change the priority accordingly.
Created attachment 8809759 [details] [diff] [review]
Pushed by firstname.lastname@example.org:
Remove the chrome only constructor for File, r=qdot
Could you update the docs: https://developer.mozilla.org/en-US/docs/Extensions/Using_the_DOM_File_API_in_chrome_code