-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Factor out common logic for img fetching #1643
Labels
Comments
domenic
pushed a commit
that referenced
this issue
Aug 10, 2016
When initiating a fetch as part of the two image-fetching algorithms (see #1643), we should use the element's referrerpolicy attribute to set the referrer policy on the request. See #1531 and w3c/webappsec-referrer-policy#40.
alice
pushed a commit
to alice/html
that referenced
this issue
Jan 8, 2019
When initiating a fetch as part of the two image-fetching algorithms (see whatwg#1643), we should use the element's referrerpolicy attribute to set the referrer policy on the request. See whatwg#1531 and w3c/webappsec-referrer-policy#40.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's "update the image data" and "The user agent may at any time run the following algorithm to update an img element's image in order to react to changes in the environment." both need the same things for fetching, and it's currently duplicated. Not good.
See #1641 (comment)
The text was updated successfully, but these errors were encountered: