Skip to content

Commit f30b39e

Browse files
saschanazsandersn
andcommitted
Revise the condition to add specs (#708)
* Revise condition to add specs * Fix typo Co-Authored-By: Nathan Shively-Sanders <[email protected]>
1 parent 243bf35 commit f30b39e

File tree

1 file changed

+2
-13
lines changed

1 file changed

+2
-13
lines changed

README.md

Lines changed: 2 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -53,19 +53,8 @@ The common steps to send a pull request are:
5353

5454
### When should a DOM API be included here?
5555

56-
If a DOM API is still a draft, it belongs on [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped#readme).
57-
When it graduates past draft stage, it can be added here and removed from DefinitelyTyped.
58-
A feature is considered a draft if:
59-
60-
#### W3C
61-
62-
A Working Draft should go on DefinitelyTyped.
63-
A feature that is a Candidate Recommendation (or has passed that stage) should be added here.
64-
65-
#### WhatWG
66-
67-
A "Working Draft" ([example](https://whatwg.org/specs/web-controls/current-work/)) should go on DefinitelyTyped.
68-
A "Living Standard" ([example](https://xhr.spec.whatwg.org/)) should be added here.
56+
A feature is considered highly experimental if a DOM API lacks multiple implementations or a formal specification from W3C or WHATWG. Such a feature belongs on [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped#readme).
57+
When it gets multiple implementations and a proper specification, it can be added here and removed from DefinitelyTyped.
6958

7059

7160
## Code Structure

0 commit comments

Comments
 (0)