- 28 Aug, 2014 1 commit
-
-
Ben Murdoch authored
-
- 27 Aug, 2014 5 commits
-
-
vmpstr@chromium.org authored
Clean cherry-pick of chromium crrev.com/286085 BUG: 16133204 Original description: One previous approach was to try and balance memory usage vs amount of time we spend analyzing tiles. This patch switches it so that we always analyze tiles in order to try and save as much memory as possible. This is due to the fact that there are some cases out there that break the heuristic and use too much memory, when otherwise they would be detected as solid. As well, it enables analysis for gpu rasterization since it also needs to start benefitting from these memory savings. Change-Id: I909295b1ef94ea45b122d1758185f3f768a747b1
-
Hui Shu authored
Merge "Cherry-pick: Only set accessibility focus on page load for browser tabs, not web views." into lmp-dev
-
dmazzoni authored
Clean cherry-pick of chromium https://crrev.com/61c6121a6cb9dc16f9786830655049d68dcde67c BUG: 17000817 Original description: Only set accessibility focus on page load for browser tabs, not web views. BUG=406053 Review URL: https://codereview.chromium.org/490333002 Change-Id: I09130c2598e71c878f85a7d8bf08f2519c337639 Cr-Commit-Position: refs/heads/master@{#291713}
-
vmpstr authored
Cherry-pick with conflict of crrev.com/7fceb77977afd9af22215eb9cd28ab667567668e Conflicts: cc/debug/rasterize_and_record_benchmark_impl.cc cc/layers/picture_layer_impl_unittest.cc cc/resources/picture_layer_tiling.cc cc/resources/picture_layer_tiling_unittest.cc cc/test/fake_picture_layer_tiling_client.cc cc/test/fake_picture_layer_tiling_client.h BUG: 16548433 Original description: This patch removes tiles from the recycle tree that were deleted from the active tree as a result of a shifting live tiles rect. It is important to do this, since if the active tree then would recreate the deleted tile (ie, live tiles rect shift back), we have to ensure that this tile will be shared when the next pending tree is created. If we don't do it, we can run into a situation in which we will continuously raster the same tile. The patch does the following: - Adds a way to get a recycled tree twin tiling. - During LiveTilesRect tile deletion, deletes tiles from the same location from the recycle twin (if one exists). Change-Id: I295cec01b476a97f68b0678d9d4322568662040f
-
vmpstr@chromium.org authored
Clean cherry-pick of crrev.com/285114 BUG: 16548433 Original description: This patch is the second part of ensuring that recycle tree does not contain any unshared tiles. This is done by removing recycle tree tilings when active tree removes those tilings. This includes a check in RemoveTilings for NULL tilings. When the first pending tree activates, it swaps with active tree's NULL tilings, which become the recycle tilings. When removing tilings, we have to ensure that tilings is not NULL before accessing its members. Change-Id: I29b3c0514cac1fc8f31251ff00f65a82631eaf65
-
- 26 Aug, 2014 1 commit
-
-
Selim Gurun authored
Bug: 17177684 The feature requires a public api to share channel IDs or disable them. We will enable the feature after the APIs are added. The chromium counterpart of this code already landed here: https://codereview.chromium.org/497963002/ Change-Id: I2ae0b0bf4a9476cf6b2ebc8759c49805f303db6b
-
- 22 Aug, 2014 2 commits
-
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/291527 BUG: 17177416 Original description: Since r289474, the sync factory nulls out the video context which means the destruction is uncontrolled. Context destruction is synchronous, so can cause deadlocks if there are not webviews attached to view tree to run GL. This is a rewrite of r289474 that just returns null VideoContextProvider if no webview is ready to use it. But still hold on to the reference to the context to avoid destruction. Change-Id: Ia5b855dd579dcdafd4ace1d2557414188d440d97
-
Marcin Kosiba authored
> In the case when the temporary_impl_bounds_ variable is set to > ComputeInnerViewportContainerSize() (which is device_viewport_size_ / > device_scale_factor()) the value should be rounded up, to match > ContentViewCoreImpl::GetViewportSizeDip(). The incorrect rounding > is causing the layer to be scrollable when the physical width > is not cleanly divisible by the dpi scale. > > BUG=405580 > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=291035 BUG: 14810760 Change-Id: I4f1f0d97f3de8f07b404526cd398c99514caad10
-
- 21 Aug, 2014 3 commits
-
-
Dehao Chen authored
-
Marcin Kosiba authored
> Amend 289844 "Simplify android_webview wrap_contents mode." > > When merging r288992 I accidentally omitted the one line from > web_preferences due to a conflicting rename of that file in trunk. > This CL fixes the mistake. > > BUG=392460 > TBR=mkosiba@chromium.org > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=291100 BUG: 15281050
-
Dehao Chen authored
Change-Id: I42092243ae643be62caeaf1c5055fab9149d5ff4
-
- 20 Aug, 2014 2 commits
-
-
boliu@chromium.org authored
Cherry-pick with conflict of crrev.com/r290937 Conflicts: cc/layers/picture_layer_impl.cc BUG: 17033041 Original description: Tiles outside of the visible rect for tile priority but inside the draw viewport should be drawn on a best effort basis. There is no need to redraw or block activations on missing or incomplete tiles in this region. Rename tile priority rect/matrix to activation rect, and use this to control activation as well. Add new counts for missing/incomplete tiles in the activation rect, and only these tiles will lead to redraws. Change-Id: I44ebf9905dab38e042f3f990890a1acdb0ad41ab
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r289997 BUG: 17033041 Original description: Nothing registers for the callback in WasShown if using synchronous compositor, so this does not change any behavior. So this is only removing unneeded RequestVSyncUpdate Change-Id: I7346590b81f03adc31bbc8b8d067d5fe4590582b
-
- 19 Aug, 2014 1 commit
-
-
Bo Liu authored
-
- 20 Aug, 2014 2 commits
-
-
Bo Liu authored
This is the same change for webview as upstream chromium crrev.com/r290764. However the upstream change is large and has conflicts, so this is a smaller change. This should not be submitted to upstream chromium. BUG: 16550863 Change-Id: I84dfeea7c3bbe7827b0741e62e9cbb59ef39d7b2
-
Dehao Chen authored
-
- 19 Aug, 2014 3 commits
-
-
Bo Liu authored
This commit was generated by merge_to_master.py. Change-Id: Ib94d0fbe53117fb95a8829f067e593ceee2e2198
-
Bo Liu authored
This commit was generated by merge_to_master.py. Change-Id: I3f9f26ef388c68b51c867e1f7d1565494e623c61
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r290450 BUG: 16948043 Original description: Without this, the same webview getting attached again but at a different part of the view tree would be getting stale and completely wrong parent draw constraints. A classic example of this is when webview going into full screen video mode. Change-Id: I9d6eafcb83b5fdee4bd9fe17c0f0392ac2d8fd52
-
- 14 Aug, 2014 2 commits
-
-
igsolla@chromium.org authored
NOTE: this cherry-pick will only be landed after these changes https://googleplex-android-review.git.corp.google.com/#/c/523937/ https://googleplex-android-review.git.corp.google.com/#/c/523939/ Added a new method, ie. AwContents.setFullscreenSupported, that will be called by the glue layer when the WebView app supports fullscreen. This is follow-up change to: https://codereview.chromium.org/428633004/ BUG=389496 Review URL: https://codereview.chromium.org/425343002 Cr-Commit-Position: refs/heads/master@{#288723} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@288723 0039d316-1c4b-4281-b951-d872f2087c98 Conflicts: android_webview/javatests/src/org/chromium/android_webview/test/AwContentsClientFullScreenVideoTest.java android_webview/native/aw_settings.cc content/public/common/common_param_traits_macros.h content/public/common/web_preferences.cc content/public/common/web_preferences.h content/renderer/render_view_impl.cc Change-Id: Ie0fb7da4a7ccb5557a22ba5c2ab1d9df2e373876
-
Ignacio Solla authored
NOTE: this cherry-pick will only be landed after https://googleplex-android-review.git.corp.google.com/#/c/523936/ We are setting it here: https://code.google.com/p/chromium/codesearch#chromium/src/android_webview/native/aw_settings.cc&l=437 But we are not yet propagating it to blink because this line was missing. This change will only be landed after the next blink deps roll including: https://codereview.chromium.org/422923002/ Review URL: https://codereview.chromium.org/422963002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286189 0039d316-1c4b-4281-b951-d872f2087c98 Conflicts: content/renderer/render_view_impl.cc Change-Id: I93874959117f2a88555632f0dac0bbbd020d1427
-
- 12 Aug, 2014 1 commit
-
-
Ignacio Solla Paula authored
Merge "Cherry-pick: Don't use webmediaplayer to FullscreenController about fullscreen change" into lmp-dev
-
- 14 Aug, 2014 1 commit
-
-
qinmin@chromium.org authored
NOTE: this cherry-pick should only be submitted after https://googleplex-android-review.git.corp.google.com/#/c/523935 BUG=17021433 --------------------------------------------------------------------- Don't use webmediaplayer to FullscreenController about fullscreen change This is cloned from https://codereview.chromium.org/275163002/ The previous change will break webview because AwWebContentsDelegate::ToggleFullscreenModeForTab is not implemented. This change passes a runtime switch to blink to disable fullscreen for non-media elements for android webview. when AwWebContentsDelegate::ToggleFullscreenModeForTab is called, android webview will send a FullscreenChanged IPC to finish the will/DidEnterFullscreen event for the media element. blink side CL: https://codereview.chromium.org/290643005/ This CL only impacts android webview BUG=367346 Review URL: https://codereview.chromium.org/292573004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@281781 0039d316-1c4b-4281-b951-d872f2087c98
-
- 13 Aug, 2014 1 commit
-
-
Ignacio Solla Paula authored
-
- 14 Aug, 2014 1 commit
-
-
igsolla@chromium.org authored
BUG=17021038 ----------------------------------------------------------- Fix ContentVideoView to support a ContextWrapper. BUG=crbug/400755 Review URL: https://codereview.chromium.org/440143002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287764 0039d316-1c4b-4281-b951-d872f2087c98
-
- 13 Aug, 2014 13 commits
-
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r289252 BUG: 16550863 Change-Id: I48eaa5843313b918f001242f073c762de43e5819
-
boliu@chromium.org authored
Cherry-pick with conflict of chromium crrev.com/r289172 Conflicts: gpu/command_buffer/service/async_pixel_transfer_manager_android.cc BUG: 16550863 Original description: With the workaround in r286800, mailbox synchronizer skips tile textures, so is compatible with async transfer egl. This is a partial revert of r286501. Change-Id: I0a193f464e0a23ab9b9a9af16770058966b6c587
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r288285 BUG: 16550863 Original description: Three related changes: * Only run idle tasks in the queue, not newly added ones. * Move g_request_pending logic to SharedRendererState. This allows pending tasks to be cancelled correctly. * Wait for kModeProcess to happen first before trying to request another to avoid a queue of pending tasks. Change-Id: If50da7ff6af6251654bc985f5cd2b78bf4f390b6
-
boliu@chromium.org authored
Clean cherry-pick of crrev.com/r288283 BUG: 16550863 Original description: Before this, a task is added to the idle queue each time in flush and ScheduleMoreIdleWork. This means that as long as there is idle work, the size of the queue grows by one in each flush. Fix this by not adding any idle tasks if there is already one pending. Change-Id: I77834205d3746e5ac43a804ec9ec173b0c372e6b
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r287713 BUG: 16550863, 16708848 Original description: Track UI and other threads differently in requesting DrawGL. The request itself is posted through UI thread, so not tracking them separately can lead to deadlocks. See bug for more detail. Change-Id: Ic3cd8c30db9f12caaf9a692425447482ea6106fb
-
heejin.r.chung@samsung.com authored
Clean cherry-pick of chromium crrev.com/r286952 Original description: Change all CreateContext() calls to Context() and remove unnecessary code. Change-Id: I81054d0af32dc165464d7f20b9b5a0a46fb824be
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r286935 BUG: 16550863 Change-Id: Ifaee48ed7a5fa80c001781106a02e31aae0d324f
-
boliu@chromium.org authored
Clean cherry-pick of chromium crrev.com/r286834 BUG: 16550863 Original description: Not flushing idle queue on tear down could lead to deadlocks. Change-Id: If8ca7d6cd2c696277e4c60c2551b0c497223a0a9
-
sievers@chromium.org authored
Clean cherry-pick of chromium crrev.com/286800 BUG: 16550863 Change-Id: I69d264e30d5278d365cf366bffaaeffb0e116c71
-
sievers@google.com authored
Cherry-pick with conflicts of chromium crrev.com/r286501 BUG: 16550863 Original description: Disable map_image if draw functor table is not set, and disallow EGL async uploads if MailboxSync is on (doesn't work). Change-Id: I755925327b82acc7c121c8508fbc0d84229c080d
-
sievers@chromium.org authored
Clean cherry-pick of chromium crrev.com/r286171 BUG: 16550863 Change-Id: Ifd76210139e28280030b30756e821900313b2f8a
-
Bo Liu authored
This commit was generated by merge_to_master.py. Change-Id: I939b7cf493e2e9ee021ca1d20098f2b991ad3798
-
Bo Liu authored
This commit was generated by merge_to_master.py. Change-Id: I167d28401e65e520fca24a7cd89b56027205c775
-
- 08 Aug, 2014 1 commit
-
-
Dehao Chen authored
Change-Id: I378e30e0c0f9c717d6a38d3f0148427869e29136
-