You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec includes a few vendor prefixed properties and functions (webkitRelativePath, webkitdirectory, webkitEntries, and webkitGetAsEntry). Are those intended to be standardized as is?
The text was updated successfully, but these errors were encountered:
(FYI, the failures are because Chromium ran into compat issues trying to rename Entry to FileSystemEntry etc and pushing to align has been very low priority for a long time.)
This document specifies a "de facto standard", i.e. it describes the reality of things. So by that metric, yes they are standardized. Does everyone involved wish this whole API didn't exist and was replaced by something with better performance and ergonomics? Also yes.
The spec includes a few vendor prefixed properties and functions (
webkitRelativePath
,webkitdirectory
,webkitEntries
, andwebkitGetAsEntry
). Are those intended to be standardized as is?The text was updated successfully, but these errors were encountered: