Skip to content

Make loading images sync in the parser case, and make selecting an image... #179

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

Merged
merged 3 commits into from
May 27, 2014

Conversation

zcorpan
Copy link

@zcorpan zcorpan commented May 21, 2014

... async in the scripted case. Fixes #152 Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=25848

attribute, or both. A user agent that obtains images immediately must also synchronously
data</span> of an <code>img</code> element that has the
<span data-x="img-parser-created">parser-created flag</span> set to true whenever that element is
inserted into a <code>Document</code>. A user agent that obtains images immediately must also synchronously
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Document/node/

Should support the cloneNode() case

Need to look into the implications of running the algorithm for an element without src/srcset

yoavweiss added a commit that referenced this pull request May 27, 2014
Make loading images sync in the parser case, and make selecting an image...
@yoavweiss yoavweiss merged commit 9c0d9bd into ResponsiveImagesCG:gh-pages May 27, 2014
@zcorpan zcorpan deleted the fix-152 branch May 27, 2014 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should source update algorithm run asynchronously?
2 participants