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.

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

Refactor data-feeding for ImageDocument/ImageDocumentParser #20889

Merged
merged 1 commit into from Dec 20, 2019

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Dec 20, 2019

ImageDocumentParser keeps the ImageResource for ImageDocument and passes
the associated ImageResourceContent to the HTMLImageElement used for the
ImageDocument.

This eliminates ImageDocument::CachedImageResourceDeprecated and cleans
up ImageDocument<->ImageDocumentParser interaction a bit.
The creation of the ImageResource now takes place in the first call to
ImageDocumentParser::AppendBytes rather than indirectly via a call to
ImageDocument::CachedImage.

Set ImageLoader::image_complete_ in the same as for regular image-loads,
and start dispatching 'load' (and 'error') events for the <img> element
in the image document. This behavior matches Gecko.

Bug: 958339
Change-Id: Iacdab89f6894adf70163f0d5300aefc9b2fce4e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975921
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726803}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

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

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot changed the title [RFC] Refactor data-feeding for ImageDocument/ImageDocumentParser Refactor data-feeding for ImageDocument/ImageDocumentParser Dec 20, 2019
ImageDocumentParser keeps the ImageResource for ImageDocument and passes
the associated ImageResourceContent to the HTMLImageElement used for the
ImageDocument.

This eliminates ImageDocument::CachedImageResourceDeprecated and cleans
up ImageDocument<->ImageDocumentParser interaction a bit.
The creation of the ImageResource now takes place in the first call to
ImageDocumentParser::AppendBytes rather than indirectly via a call to
ImageDocument::CachedImage.

Set ImageLoader::image_complete_ in the same as for regular image-loads,
and start dispatching 'load' (and 'error') events for the <img> element
in the image document. This behavior matches Gecko.

Bug: 958339
Change-Id: Iacdab89f6894adf70163f0d5300aefc9b2fce4e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975921
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726803}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants