diff options
author | lukasza <lukasza@chromium.org> | 2015-12-30 20:45:29 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-12-31 04:46:34 +0000 |
commit | 902fcc5c3732cf387828f7e0c10a810e5bf85714 (patch) | |
tree | ebbc67d00279ebed26a819edf4fdaa1db81b68e6 /components | |
parent | 64eba5b39620df70320fd0d23e4ba85022670203 (diff) | |
download | chromium_src-902fcc5c3732cf387828f7e0c10a810e5bf85714.zip chromium_src-902fcc5c3732cf387828f7e0c10a810e5bf85714.tar.gz chromium_src-902fcc5c3732cf387828f7e0c10a810e5bf85714.tar.bz2 |
Rename [Web]PageSerializer[Test|Client|Impl] to ...FrameSerializer...
After refactoring needed to support OOPIFs in save-page-as feature, the
html serializers in blink serialize frames, not pages and therefore
their old names (WebPageSerializer, PageSerializer, etc) do not apply
anymore. Therefore this CL renames PageSerializer to FrameSerializer
where applicable.
Note that this rename not only covers PageSerializer class, but also
WebPageSerializer, WebPageSerializerClient, PageSerializerTest, test
data files, etc.
Note that FrameSerializer is more correct than HtmlSerializer, because
- FrameSerializer also serializes subresources (i.e. images)
- Even though WebFrameSerializerImpl deals only with HTML documents,
for now it might make sense to leave it named as WebFrameSerializerImpl:
- it still takes a Frame as input
- it implements part of the public WebFrameSerializer class
(and therefore it is desirable to have a similar name here as well)
BUG=538766,526786
Review URL: https://codereview.chromium.org/1541463002
Cr-Commit-Position: refs/heads/master@{#367227}
Diffstat (limited to 'components')
0 files changed, 0 insertions, 0 deletions