@@ -1341,6 +1341,15 @@ <h3>
1341
1341
< li > Return < var > manifest</ var > and < var > manifest URL</ var > .
1342
1342
</ li >
1343
1343
</ ol >
1344
+ < p class ="issue ">
1345
+ There is currently no specified way to obtain a manifest without an
1346
+ associated < a > top-level browsing context</ a > . However, several user
1347
+ agents do just that (when they install a web application directly
1348
+ from a manifest URL, without a document). This algorithm, and the
1349
+ < a > steps to install the web application</ a > , should similarly be
1350
+ written to not require a document. See < a href =
1351
+ "https://github.com/w3c/manifest/issues/668 "> #668</ a > .
1352
+ </ p >
1344
1353
< div class ="note ">
1345
1354
< p >
1346
1355
Authors are encouraged to use the HTTP cache directives to
@@ -1433,14 +1442,6 @@ <h3>
1433
1442
URL</ var > . The output from inputting an JSON document into this
1434
1443
algorithm is a < dfn > processed manifest</ dfn > .
1435
1444
</ p >
1436
- < p class ="issue ">
1437
- There is currently no way to invoke this algorithm without a
1438
- < var > document URL</ var > . However, several user agents do just that
1439
- (when they install a web application directly from a manifest URL,
1440
- without a document). The algorithms that invoke this one should
1441
- similarly be written to not require a < var > document URL</ var > . See
1442
- < a href ="https://github.com/w3c/manifest/issues/668 "> #668</ a > .
1443
- </ p >
1444
1445
< p class ="issue ">
1445
1446
We need to catch throws associated with enumerations in IDL
1446
1447
conversion as the spec might gain new values over time not supported
0 commit comments