Editorial: clarify how to deal with missing `platform` and `form_fact… · w3c/manifest-app-info@08b3478
jespertheend
·
2023-08-22
·
via Recent Commits to manifest-app-info:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -340,6 +340,10 @@ <h3>
|
340 | 340 | their platform (e.g., Google Play should not show iOS-specific |
341 | 341 | screenshots). |
342 | 342 | </p> |
| 343 | +<p> |
| 344 | + When no `platform` is set, user agents should assume the screenshot |
| 345 | + is applicable to all platforms. |
| 346 | +</p> |
343 | 347 | <p> |
344 | 348 | User agents can use a screenshot’s aspect ratio |
345 | 349 | ({{ImageResource/sizes}}) in determining if the screenshot should be |
@@ -469,6 +473,10 @@ <h3>
|
469 | 473 | form factor (e.g., mobile phones shouldn't show "wide" `form_factor` |
470 | 474 | screenshots). |
471 | 475 | </p> |
| 476 | +<p> |
| 477 | + When no `form_factor` is set, user agents should assume the |
| 478 | + screenshot is applicable to all form factors. |
| 479 | +</p> |
472 | 480 | <p> |
473 | 481 | List of `form_factor` values: |
474 | 482 | </p> |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
