-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.
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
Add MIME Checks for link rel=manifest #24446
Conversation
html/links/manifest/mime-type-application-manifest+json.headers
Outdated
Show resolved
Hide resolved
<h1>Test JSON MIME Type support for web manifest</h1> | ||
<p> | ||
To pass, the use agent must treat the manifest valid (name is "pass"). The | ||
response's Content-Type metadata is a JSON MIME type "text/json". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to test an "invalid" media type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea... will add an actual invalid type.
@marcoscaceres the checks for this PR will be blocked due to the Taskcluster Checks migration. You can either rebase/merge-from-master the PR to bring in the new Taskcluster config, or just let me know when you want it merged and I can admin-merge it for you :) |
Thanks @stephenmcgruer! I'll rebase. |
5f311e6
to
b895983
Compare
The lint is failing because html/links/manifest/mime-type-none.html and html/links/manifest/mime-type-invalid.html are being interpreted as (misnamed) visual tests. To avoid this, one can put them in a resources/ or support/ subdirectory. |
Thanks for the tip, @foolip! Fixed the naming... they should have been "-manual.html" - so thankfully the linter caught those! |
Part of #24389