Name: fetch
Owner: WHATWG
Description: Fetch Standard
Created: 2012-09-12 08:39:20.0
Updated: 2018-01-15 14:26:40.0
Pushed: 2018-01-17 12:01:07.0
Homepage: https://fetch.spec.whatwg.org/
Size: 6627
Language: HTML
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This repository hosts the Fetch Standard.
We are committed to providing a friendly, safe and welcoming environment for all. Please read and respect the WHATWG Code of Conduct.
Folks notice minor and larger issues with the Fetch Standard all the time and we'd love your help fixing those. Pull requests for typographical and grammar errors are also most welcome.
We'd be happy to mentor you through this process. If you're interested and need help getting started, leave a comment on the issue or ask around on IRC.
In short, change fetch.bs and submit your patch, with a
good commit message. Consider
reading through the WHATWG FAQ if you are new here.
Please add your name to the Acknowledgments section in your first pull request, even for trivial fixes. The names are sorted lexicographically.
If you want to preview the spec locally, you can either use a locally installed copy of
Bikeshed by running make or use the HTTP API version by
running make remote.
If you want to do a complete “local deploy” including commit and/or branch snapshots, run
make deploy.
Use a column width of 100 characters.
Do not use newlines inside “inline” elements, even if that means exceeding the column width requirement.
><p>Execute
href=https://w3c.github.io/webappsec-csp/#set-response-csp-list>set <var>response</var>'s CSP list</a>
<var>response</var>. <span data-anolis-ref>CSP</span>
is okay and
><p>Execute
href=https://w3c.github.io/webappsec-csp/#set-response-csp-list>set <var>response</var>'s CSP
t</a> on <var>response</var>. <span data-anolis-ref>CSP</span>
is not.
Using newlines between “inline” element tag names and their content is also forbidden. (This actually alters the content, by adding spaces.) That is
oken</a>
is fine and
oken
is not.
An <li> element always has a <p> element inside it, unless it's a child of <ul class=brief>.
If a “block” element contains a single “block” element, do not put it on a newline.
Do not indent for anything except a new “block” element. For instance
><p>Set <var>response</var>'s <span title=concept-response-url-list>url list</span> to a copy of
r>request</var>'s <span title=concept-request-url-list>url list</span>.
is not indented, but
>
>Run these substeps <span data-anolis-spec=html>in parallel</span>:
l>
is.
End tags must be omitted when possible and attribute values must not be quoted (if necessary, use double quotes).
If you can commit to this repository, see the maintainer guidelines.
Tests can be found in the fetch/ directory of
web-platform-tests.