Conversation
Add a note to the input/file non-standard attributes section explaining that webkitdirectory is being standardized via the WICG File and Directory Entries API spec, which is not yet a W3C standard (browser-compat-data still marks it standard_track: false).
|
Preview URLs (2 pages) (comment last updated: 2026-09-11 22:39:46) |
|
Just saw that BCD says it's non-standard. I think you should get that fixed first because right now it's inconsistent with https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/webkitdirectory. |
Per review feedback on PR mdn#45474: webkitdirectory is defined in the File and Directory Entries API (a WICG spec), matching the standard track status already recorded for api.HTMLInputElement.webkitdirectory in browser-compat-data. Move it out of the "Non-standard attributes" sections on the <input type="file"> and <input> pages into the regular attribute lists, alongside a companion browser-compat-data fix (html.elements.input.webkitdirectory's standard_track) prepared separately so the two stay consistent. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P2PaDYUv8Js2URx3GmpfP2
|
Traced the inconsistency down: browser-compat-data has two entries for this feature with mismatched status. Pushed a commit here that moves |
Co-authored-by: Joshua Chen <sidachen2003@gmail.com>
webkitdirectory is being standardizedwebkitdirectory to standard
Description
Add a note to the
<input type="file">reference page's "Non-standard attributes" section explaining thatwebkitdirectoryis in the process of being standardized.Motivation
The issue reported that the page doesn't mention
webkitdirectoryis being standardized. I confirmed the current spec status before editing:webkitdirectory, explicitly states it "is not a W3C Standard nor is it on the W3C Standards Track" — it's a WICG Community Group draft, not a full standard.browser-compat-data's entry forhtml/elements/input.json'swebkitdirectorystill has"standard_track": false.webkitdirectory.Since it isn't yet part of a full WHATWG/W3C standard, I kept it in the "Non-standard attributes" section (rather than moving it out) and added a note pointing to the WICG spec that is standardizing it, so readers get the "it's on track to become standard" context the issue asked for without an inaccurate "this is now standard" claim.
I also checked the sibling
HTMLInputElement.webkitdirectoryproperty page — it doesn't make any explicit standard/non-standard text claim (its Specifications/Compat sections are auto-generated from BCD), so it's already consistent and didn't need a change.Additional details
webkitdirectoryBCD entry (standard_track: false)Related issues and pull requests
Fixes #45466