Hi all,

the implementation of <input type=file webkitdirectory> and
Entries API[1] (dragEvent.dataTransfer.items[<x>].webkitGetAsEntry()) is close 
to be ready.
Just couple of patches to land, I hope. Dnd directories to Google Drive works 
etc.

The original idea was to ship so called Upload proposal, but
MS decided to implement webkit* stuff (which was already implemented in Chrome, 
but not in Safari). So given that
there are two implementations of the old APIs shipping (or about to ship, 
Entries API in Edge. webkitdirectory is already shipping there)
and no implementation of the proposal shipping, it was decided that it is better to implement the old APIs first, and then if other browser vendors show interest to implement the proposal (which is quite a bit better and easier to use API), we could enable also that API.
We do have partial implementation of the Upload proposal and Entries API is 
implemented on top of that.


When Upload proposal was being implemented, the idea was to expose it only in 
SecureContext.
The old APIs however are exposed everywhere in other browsers and that is why I 
propose and am planning to do the same.
Feel free to disagree, but please explain why we'd implement something 
differently to others and why it would be web compatible.
We can still after shipping try to convince other browsers to move the APIs 
behind SecureContext.



-Olli




[1] very early draft https://wicg.github.io/entries-api/ which doesn't quite 
yet follow what browsers actually do.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to