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.

Sign up for GitHub

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

Jump to bottom

Lack of example and Explainer document #16

Closed
slightlyoff opened this issue Mar 30, 2016 · 2 comments
Closed

Lack of example and Explainer document #16

slightlyoff opened this issue Mar 30, 2016 · 2 comments
Labels
good first issue Ideal for someone new to a WHATWG standard or software project

Comments

@slightlyoff
Copy link

In general, Chrome engineers should only be implementing new APIs that have reasonable Explainer documents attached. Re TAG issues #85, the examples in this spec are pretty thin and there's no adjoining Explainer doc to compensate.

/cc @davidsgrogan
@annevk
Copy link
Member

annevk commented Mar 30, 2016

Happy to take PRs, though I'm not sure an Explainer document makes sense as we should just make the specification clearer then.

@annevk annevk added the good first issue Ideal for someone new to a WHATWG standard or software project label Mar 31, 2016
@annevk annevk closed this as completed in 21d77ce Mar 31, 2016
@annevk
Copy link
Member

annevk commented Mar 31, 2016

I added some examples. If you have some more ideas, please consider submitting a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Ideal for someone new to a WHATWG standard or software project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@slightlyoff @annevk