Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: What are the statuses of vendor prefixed properties? #42

Closed
kt3k opened this issue Jul 21, 2023 · 1 comment
Closed

Question: What are the statuses of vendor prefixed properties? #42

kt3k opened this issue Jul 21, 2023 · 1 comment

Comments

@kt3k
Copy link

kt3k commented Jul 21, 2023

The spec includes a few vendor prefixed properties and functions (webkitRelativePath, webkitdirectory, webkitEntries, and webkitGetAsEntry). Are those intended to be standardized as is?

@inexorabletash
Copy link
Member

Per https://wpt.fyi/results/entries-api/idlharness.window.html?label=experimental&label=master&aligned

Chromium (Chrome, Edge), Gecko (Firefox) and WebKit (Safari) all have:

  • File interface: attribute webkitRelativePath
  • HTMLInputElement interface: attribute webkitdirectory
  • HTMLInputElement interface: attribute webkitEntries
  • DataTransferItem interface: operation webkitGetAsEntry()

(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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants