Skip to content

Commit 8f4ea0d

Browse files
marcoscaceresmarcoscaceres
authored
chore: put in updatable rec infra (#149)
1 parent 09b48e6 commit 8f4ea0d

File tree

1 file changed

+70
-56
lines changed

1 file changed

+70
-56
lines changed

‎index.html‎

Lines changed: 70 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,21 @@
5454
</p>
5555
</section>
5656
<section id="sotd" class="updateable-rec">
57+
<script class="removeOnSave">
58+
function updateableRecFilter(commit) {
59+
const { message } = commit;
60+
// only show commits that start with Addition: or Correction:
61+
return /^Addition:|^Correction:/.test(message);
62+
}
63+
</script>
64+
<p>
65+
Since this specification become a W3C Recommendation on 01 September 2022,
66+
the following substantive additions and/or corrections have been proposed:
67+
</p>
68+
<rs-changelog from="REC-2022" filter="updateableRecFilter">
69+
</rs-changelog>
5770
<p>
58-
The Devices and Sensors Working Group is updating this specification in
59-
the hope of making it a "living standard". As such, we've dropped the
60-
"Editions" and aim to continue publishing updated W3C Recommendations
61-
of this specification as we add new features or fix bugs.
71+
A more detailed list of changes can be found in section [[[#changelog]]].
6272
</p>
6373
</section>
6474
<section id="introduction" class="informative">
@@ -117,58 +127,6 @@ <h3>
117127
locations.
118128
</p>
119129
</section>
120-
<section class="informative">
121-
<h2>
122-
Change log
123-
</h2>
124-
<p>
125-
Since First Public Working Draft in 2021, the <cite>Geolocation
126-
API</cite> has received the following normative changes:
127-
</p>
128-
<script class="removeOnSave">
129-
function removeCommits({ message }) {
130-
return !/^Clarify which FPWD|^Merge pull|^tidy|^editorial|^Editiorial|^edtiorial|^chore|^refactor|^tests?|^docs|^typo|^nit/i.test(message);
131-
}
132-
</script> <rs-changelog from="FPWD" filter=
133-
"removeCommits"></rs-changelog>
134-
<p>
135-
Since publication of the Second Edition in 2016, this specification
136-
has received the following changes:
137-
</p>
138-
<ul>
139-
<li>[=Request a position=] only proceeds when a document is visible,
140-
or the document becomes visible.
141-
</li>
142-
<li>Clarified how caching works as part of [=acquiring a position=]:
143-
only last position is cached, and can be evicted at any time.
144-
</li>
145-
<li>Now relies on the [[[Permissions]]] specification to handle
146-
permission grants, and user interface requirements.
147-
</li>
148-
<li>The `errorCallback` is now nullable.
149-
</li>
150-
<li>The API can be controlled by [[[Permissions-Policy]]], which
151-
restricts how/where the API is exposed to web pages.
152-
</li>
153-
<li>The `callbacks` are no longer treated as "EventHandler" objects
154-
(i.e., objects that have a `.handleEvent()` method), but are now
155-
exclusively treated as IDL callback functions.
156-
</li>
157-
<li>The API is now only exposed in Secure Contexts (i.e., only
158-
available in HTTPS).
159-
</li>
160-
<li>The interfaces no longer use [[WebIDL]]'s legacy
161-
`[NoInterfaceObject]`, so `Geolocation` and other interface of this
162-
spec are now in the global scope. Also, the interfaces were renamed
163-
from `NavigatorGeolocation*` to just `Geolocation*`.
164-
</li>
165-
</ul>
166-
<p>
167-
See the <a href=
168-
"https://github.com/w3c/geolocation-api/commits/gh-pages">commit
169-
history</a> for a complete list of changes.
170-
</p>
171-
</section>
172130
</section>
173131
<section class="informative">
174132
<h2>
@@ -1330,5 +1288,61 @@ <h2>
13301288
Wilde, Matt Womer, and Mohamed Zergaoui.
13311289
</p>
13321290
</section>
1291+
<section class="appendix" class="informative" id="changelog">
1292+
<h2>
1293+
Change log
1294+
</h2>
1295+
<p>
1296+
Since First Public Working Draft in 2021, the <cite>Geolocation
1297+
API</cite> has received the following normative changes:
1298+
</p>
1299+
<script class="removeOnSave">
1300+
function removeCommits(commit) {
1301+
const { message, hash } = commit;
1302+
if (["ef098b1"].includes(hash)) {
1303+
return false;
1304+
}
1305+
return !/^Clarify which FPWD|^Merge pull|^tidy|^editorial|^Editiorial|^edtiorial|^chore|^refactor|^tests?|^docs|^typo|^nit/i.test(message);
1306+
}
1307+
</script> <rs-changelog from="FPWD" filter=
1308+
"removeCommits"></rs-changelog>
1309+
<p>
1310+
Since publication of the Second Edition in 2016, this specification
1311+
received the following substantive changes:
1312+
</p>
1313+
<ul>
1314+
<li>[=Request a position=] only proceeds when a document is visible,
1315+
or the document becomes visible.
1316+
</li>
1317+
<li>Clarified how caching works as part of [=acquiring a position=]:
1318+
only last position is cached, and can be evicted at any time.
1319+
</li>
1320+
<li>Now relies on the [[[Permissions]]] specification to handle
1321+
permission grants, and user interface requirements.
1322+
</li>
1323+
<li>The `errorCallback` is now nullable.
1324+
</li>
1325+
<li>The API can be controlled by [[[Permissions-Policy]]], which
1326+
restricts how/where the API is exposed to web pages.
1327+
</li>
1328+
<li>The `callbacks` are no longer treated as "EventHandler" objects
1329+
(i.e., objects that have a `.handleEvent()` method), but are now
1330+
exclusively treated as IDL callback functions.
1331+
</li>
1332+
<li>The API is now only exposed in Secure Contexts (i.e., only
1333+
available in HTTPS).
1334+
</li>
1335+
<li>The interfaces no longer use [[WebIDL]]'s legacy
1336+
`[NoInterfaceObject]`, so `Geolocation` and other interface of this
1337+
spec are now in the global scope. Also, the interfaces were renamed
1338+
from `NavigatorGeolocation*` to just `Geolocation*`.
1339+
</li>
1340+
</ul>
1341+
<p>
1342+
See the <a href=
1343+
"https://github.com/w3c/geolocation-api/commits/gh-pages">commit
1344+
history</a> for a complete list of changes.
1345+
</p>
1346+
</section>
13331347
</body>
13341348
</html>

0 commit comments

Comments
 (0)