@@ -1309,6 +1309,15 @@ <h3>
1309
1309
< li > Return < var > manifest</ var > and < var > manifest URL</ var > .
1310
1310
</ li >
1311
1311
</ ol >
1312
+ < p class ="issue ">
1313
+ There is currently no specified way to obtain a manifest without an
1314
+ associated < a > top-level browsing context</ a > . However, several user
1315
+ agents do just that (when they install a web application directly
1316
+ from a manifest URL, without a document). This algorithm, and the
1317
+ < a > steps to install the web application</ a > , should similarly be
1318
+ written to not require a document. See < a href =
1319
+ "https://github.com/w3c/manifest/issues/668 "> #668</ a > .
1320
+ </ p >
1312
1321
< div class ="note ">
1313
1322
< p >
1314
1323
Authors are encouraged to use the HTTP cache directives to
@@ -1401,14 +1410,6 @@ <h3>
1401
1410
URL</ var > . The output from inputting an JSON document into this
1402
1411
algorithm is a < dfn > processed manifest</ dfn > .
1403
1412
</ p >
1404
- < p class ="issue ">
1405
- There is currently no way to invoke this algorithm without a
1406
- < var > document URL</ var > . However, several user agents do just that
1407
- (when they install a web application directly from a manifest URL,
1408
- without a document). The algorithms that invoke this one should
1409
- similarly be written to not require a < var > document URL</ var > . See
1410
- < a href ="https://github.com/w3c/manifest/issues/668 "> #668</ a > .
1411
- </ p >
1412
1413
< p class ="issue ">
1413
1414
We need to catch throws associated with enumerations in IDL
1414
1415
conversion as the spec might gain new values over time not supported
0 commit comments