You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See https://github.com/whatwg/spec-factory for details.
(Note that READMEEND.md is a locally maintained addition that is merged into README.md by spec-factory.)
description: File a new issue against the URL Standard.
3
+
body:
4
+
- type: markdown
5
+
attributes:
6
+
value: |
7
+
Before filling out this form, please familiarize yourself with the [Code of Conduct](https://whatwg.org/code-of-conduct). You might also find the [FAQ](https://whatwg.org/faq) and [Working Mode](https://whatwg.org/working-mode) useful.
8
+
9
+
If at any point you have questions, please reach out to us on [Chat](https://whatwg.org/chat).
10
+
- type: textarea
11
+
attributes:
12
+
label: "What is the issue with the URL Standard?"
13
+
validations:
14
+
required: true
15
+
- type: markdown
16
+
attributes:
17
+
value: "Thank you for taking the time to improve the URL Standard!"
Before filling out this form, please familiarize yourself with the [Code of Conduct](https://whatwg.org/code-of-conduct), [FAQ](https://whatwg.org/faq), and [Working Mode](https://whatwg.org/working-mode). They help with setting expectations and making sure you know what is required. The FAQ ["How should I go about proposing new features to WHATWG standards?"](https://whatwg.org/faq#adding-new-features) is especially relevant.
9
+
10
+
If at any point you have questions, please reach out to us on [Chat](https://whatwg.org/chat).
11
+
- type: textarea
12
+
attributes:
13
+
label: "What problem are you trying to solve?"
14
+
validations:
15
+
required: true
16
+
- type: textarea
17
+
attributes:
18
+
label: "What solutions exist today?"
19
+
- type: textarea
20
+
attributes:
21
+
label: "How would you solve it?"
22
+
- type: textarea
23
+
attributes:
24
+
label: "Anything else?"
25
+
- type: markdown
26
+
attributes:
27
+
value: "Thank you for taking the time to improve the URL Standard!"
Thank you for contributing to the URL Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
3
+
When editing this comment after the PR is created, check that PR-Preview doesn't overwrite your changes.
4
+
If you think your PR is ready to land, please double-check that the build is passing and the checklist is complete before pinging.
3
5
-->
4
6
5
7
-[ ] At least two implementers are interested (and none opposed):
6
8
* …
7
9
* …
8
10
-[ ][Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
9
-
* …
11
+
* …<!-- If these tests are tentative, link a PR to make them non-tentative. -->
10
12
-[ ][Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
11
13
* Chromium: …
12
14
* Gecko: …
13
15
* WebKit: …
14
16
* Deno: …
15
17
* Node.js: …
16
18
-[ ][MDN issue](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) is filed: …
19
+
-[ ] The top of this comment includes a [clear commit message](https://github.com/whatwg/meta/blob/main/COMMITTING.md) to use. <!-- If you created this PR from a single commit, Github copied its message. Otherwise, you need to add a commit message yourself. -->
17
20
18
21
(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)
Copy file name to clipboardExpand all lines: README.md
+68-27
Original file line number
Diff line number
Diff line change
@@ -2,47 +2,88 @@ This repository hosts the [URL Standard](https://url.spec.whatwg.org/).
2
2
3
3
## Code of conduct
4
4
5
-
We are committed to providing a friendly, safe, and welcoming environment for all. Please read and
6
-
respect the [WHATWG Code of Conduct](https://whatwg.org/code-of-conduct).
5
+
We are committed to providing a friendly, safe, and welcoming environment for all. Please read and respect the [Code of Conduct](https://whatwg.org/code-of-conduct).
7
6
8
7
## Contribution opportunities
9
8
10
-
Folks notice minor and larger issues with the URL Standard all the time and we'd love your help
11
-
fixing those. Pull requests for typographical and grammar errors are also most welcome.
9
+
Folks notice minor and larger issues with the URL Standard all the time and we'd love your help fixing those. Pull requests for typographical and grammar errors are also most welcome.
12
10
13
-
We'd be happy to mentor you through this process. If you're interested and need help getting
14
-
started, leave a comment on the issue or ask around [on IRC](https://whatwg.org/irc).
11
+
Issues labeled ["good first issue"](https://github.com/whatwg/url/labels/good%20first%20issue) are a good place to get a taste for editing the URL Standard. Note that we don't assign issues and there's no reason to ask for availability either, just provide a pull request.
15
12
16
-
## Pull requests
13
+
If you are thinking of suggesting a new feature, read through the [FAQ](https://whatwg.org/faq) and [Working Mode](https://whatwg.org/working-mode) documents to get yourself familiarized with the process.
17
14
18
-
In short, change `url.bs` and submit your patch, with a
To ensure your patch meets all the necessary requirements, please also see the [Contributor Guidelines](https://github.com/whatwg/meta/blob/main/CONTRIBUTING.md). Editors of the URL Standard are expected to follow the [Maintainer Guidelines](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md).
Tests are an essential part of the standardization process and will need to be created or adjusted as changes to the standard are made. Tests for the URL Standard can be found in the `url/` directory of [`web-platform-tests/wpt`](https://github.com/web-platform-tests/wpt).
40
28
41
-
## Tests and implementations
29
+
A dashboard showing the tests running against browser engines can be seen at [wpt.fyi/results/url](https://wpt.fyi/results/url).
30
+
31
+
## Building "locally"
42
32
43
-
Tests can be found in the `url/` directory of
44
-
[web-platform-tests/wpt](https://github.com/web-platform-tests/wpt). A dashboard showing the tests
45
-
running against major browsers can be seen at [wpt.fyi](https://wpt.fyi/results/url).
33
+
For quick local iteration, run `make`; this will use a web service to build the standard, so that you don't have to install anything. See more in the [Contributor Guidelines](https://github.com/whatwg/meta/blob/main/CONTRIBUTING.md#building).
34
+
35
+
## Formatting
36
+
37
+
Use a column width of 100 characters.
38
+
39
+
Do not use newlines inside "inline" elements, even if that means exceeding the column width requirement.
lt=remove(tokens)|remove()><code>remove(<var>tokens</var>…)</code></dfn> method, when
49
+
invoked, must run these steps:
50
+
```
51
+
is not.
52
+
53
+
Using newlines between "inline" element tag names and their content is also forbidden. (This actually alters the content, by adding spaces.) That is
54
+
```html
55
+
<a>token</a>
56
+
```
57
+
is fine and
58
+
```html
59
+
<a>token
60
+
</a>
61
+
```
62
+
is not.
63
+
64
+
An `<li>` element always has a `<p>` element inside it, unless it's a child of `<ul class=brief>`.
65
+
66
+
If a "block" element contains a single "block" element, do not put it on a newline.
67
+
68
+
Do not indent for anything except a new "block" element. For instance
69
+
```html
70
+
<li><p>For each <var>token</var> in <var>tokens</var>, in given order, that is not in
71
+
<a>tokens</a>, append <var>token</var> to <a>tokens</a>.
72
+
```
73
+
is not indented, but
74
+
```html
75
+
<ol>
76
+
<li>
77
+
<p>For each <var>token</var> in <var>tokens</var>, run these substeps:
78
+
79
+
<ol>
80
+
<li><p>If <var>token</var> is the empty string, <a>throw</a> a {{SyntaxError}} exception.
81
+
```
82
+
is.
83
+
84
+
End tags may be included (if done consistently) and attributes may be quoted (using double quotes), though the prevalent theme is to omit end tags and not quote attributes (unless they contain a space).
85
+
86
+
## Implementations
46
87
47
88
A complete JavaScript implementation of the standard can be found at
48
89
[jsdom/whatwg-url](https://github.com/jsdom/whatwg-url). This implementation is kept synchronized
0 commit comments