Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(750)

Issue 2541903002: PDF pinch zoom: Update layer transform for a zoom out after a zoom in. (Closed)

Created:
4 years ago by Kevin McNee
Modified:
4 years ago
Reviewers:
Lei Zhang, bokan, raymes
CC:
chromium-reviews
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

PDF pinch zoom: Update layer transform for a zoom out after a zoom in. Currently, whenever we pinch zoom out, we clear any layer transform and reraster at the new zoom level. However, during a pinch zoom in (and especially when slowly panning), we may get occasional zoom out events which cause us to clear the layer transform. As the zoom in continues we will then set the layer transform again. This repeated setting and clearing causes noticeable jumping back and forth of the PDF content. In this patch, when we get a pinch zoom out, if a layer transform is already set due to a previous zoom in, we update the layer transform instead of clearing it. BUG=664157 Committed: https://crrev.com/a6e4fc5905ae3e09f54d0c7a2e0fb9d89badb435 Cr-Commit-Position: refs/heads/master@{#436640}

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+7 lines, -1 line) Patch
M pdf/out_of_process_instance.cc View 1 chunk +7 lines, -1 line 0 comments Download

Messages

Total messages: 22 (10 generated)
Kevin McNee
Hello, thestig@. Here's a change to fix the jittery panning when pinch zooming PDFs.
4 years ago (2016-11-30 18:02:49 UTC) #2
Kevin McNee
Oops.. I see thestig is on leave. raymes@: Could you take a look at this?
4 years ago (2016-11-30 18:14:15 UTC) #6
raymes
I don't know too much about pinch zoom. Would it make sense for bokan@ to ...
4 years ago (2016-11-30 22:57:57 UTC) #10
bokan
Looks reasonable to me. Is there a way we can test this behavior?
4 years ago (2016-12-01 16:26:12 UTC) #11
bokan
On 2016/12/01 16:26:12, bokan wrote: > Looks reasonable to me. Is there a way we ...
4 years ago (2016-12-01 16:55:13 UTC) #12
raymes
On 2016/12/01 16:55:13, bokan wrote: > On 2016/12/01 16:26:12, bokan wrote: > > Looks reasonable ...
4 years ago (2016-12-05 01:49:43 UTC) #13
raymes
On 2016/12/05 01:49:43, raymes wrote: > On 2016/12/01 16:55:13, bokan wrote: > > On 2016/12/01 ...
4 years ago (2016-12-05 01:50:07 UTC) #14
Kevin McNee
On 2016/12/05 01:50:07, raymes wrote: > On 2016/12/05 01:49:43, raymes wrote: > > On 2016/12/01 ...
4 years ago (2016-12-05 16:31:02 UTC) #15
raymes
Ah I see. It would be great to make those things testable but I won't ...
4 years ago (2016-12-05 23:43:54 UTC) #16
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2541903002/1
4 years ago (2016-12-06 16:59:35 UTC) #18
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years ago (2016-12-06 18:04:56 UTC) #20
commit-bot: I haz the power
4 years ago (2016-12-06 18:06:49 UTC) #22
Message was sent while issue was closed.
Patchset 1 (id:??) landed as
https://crrev.com/a6e4fc5905ae3e09f54d0c7a2e0fb9d89badb435
Cr-Commit-Position: refs/heads/master@{#436640}

Powered by Google App Engine
This is Rietveld 408576698