Add potential hueristics for the README #828
Conversation
Co-Authored-By: Nathan Shively-Sanders <[email protected]>
| - Is the IDL source from WHATWG? | ||
| - Are the additions available in at least two of Firefox, Safari and Chromium? | ||
| - Is the IDL source from W3C? | ||
| - What stage of the [W3C process](https://en.wikipedia.org/wiki/World_Wide_Web_Consortium#Specification_maturation) is the proposal for these changes: We aim for Proposed recommendation, but can accept Candidate recommendation for stable looking proposals. |
There was a problem hiding this comment.
What would be reasons to take W3C specs in different way? W3C also will try not to introduce a breaking change if multiple implementations are already shipped and being used, as doing so will break the web. I know they have their approval steps, but I think that's more about algorithmic details rather than the API form.
There was a problem hiding this comment.
I think of this as we're seeing this a little bit more mechanically (because we're not involved in the process and are always coming a bit late to the party) and trying to find heuristics to understand how to react directly from a PR
The main reason they were differentiated was because they came with differing level of ways to verify "done"-ness. A W3C spec can says "this is ready, and won't change" vs a WHATWG which is always living and we have to validate
There was a problem hiding this comment.
Makes sense. I guess I'm okay with this as I think you will allow some exceptions 👍
|
Thanks @saschanaz |
Notes -> Prose from our pairing session