Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Editorial: clarify how to deal with missing platform and form_factor fields. #65

Merged
merged 3 commits into from
Aug 21, 2023
Merged

Editorial: clarify how to deal with missing platform and form_factor fields. #65

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6d88f01
Add note for when no form_factor or platform is set on screenshots
jespertheend Apr 24, 2023
0c3b0a1
run tidy
jespertheend Apr 24, 2023
a09e227
Slight language tweak
aarongustafson Aug 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -340,6 +340,10 @@ <h3>
their platform (e.g., Google Play should not show iOS-specific
screenshots).
</p>
<p>
When no `platform` is set, a user agent should assume the screenshot
was intended for universal usage.
</p>
<p>
User agents can use a screenshot’s aspect ratio
({{ImageResource/sizes}}) in determining if the screenshot should be
Expand Down Expand Up @@ -469,6 +473,10 @@ <h3>
form factor (e.g., mobile phones shouldn't show "wide" `form_factor`
screenshots).
</p>
<p>
When no `form_factor` is set, a user agent should assume the
screenshot was intended for universal usage.
</p>
<p>
List of `form_factor` values:
</p>
Expand Down