- 11 Jul, 2019 40 commits
-
-
Min Chen authored
Bug: 972162 Change-Id: I960d903c2e7e9cd86c34019fa30d677ff78557de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696050Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Min Chen <minch@chromium.org> Cr-Commit-Position: refs/heads/master@{#676504}
-
Alex Moshchuk authored
It might be useful to keep these for informing issue 621724, which is still not fixed. Bug: 975015, 975234, 621724 Change-Id: Ie6cf1d2784cc7aaeb52039865723184fb74be3d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696683 Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Auto-Submit: Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#676503}
-
Julian Kung authored
Previously, each function MinimizeWindow, MaximizeWindow, etc... had their own code to change window state to normal before calling GetWindowBounds. This changelist refactors the code so window state normalization only occurs in one place. R=johnchen@chromium.org Change-Id: I0a865adf6e9e1d64afc0694930a6982789f6656a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696451 Commit-Queue: Julian Kung <juliankung@google.com> Reviewed-by:
John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#676502}
-
Bryan McQuade authored
Now that we are making FID4 the official metric, this change brings the AMP-specific FID metrics in line with the core FID metrics. Change-Id: Ida5d91e6b06749b25fb9d3e0b47bf768c1cd9d54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697956Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Bryan McQuade <bmcquade@chromium.org> Cr-Commit-Position: refs/heads/master@{#676501}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/db9e714c8b2c..360b8d795ccb Created with: gclient setdep -r src-internal@360b8d795ccb The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=wjmaclean@google.com,mpearson@google.com,hayato@google.com,pmarko@google.com Change-Id: Ibd1cdd202aa0722f5b1d898a2e82ede11a8ccb1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697075Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#676500}
-
Takuto Ikuta authored
Let me add a sanity check just to confirm UdevLoader::Get() works. I will use this test to investigate loader behavior in msan on xenial. Bug: 981731 Change-Id: I824f95767cb4ccdb73f544e8cea670571b1cc8d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697661 Commit-Queue: Reilly Grant <reillyg@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#676499}
-
yilkal authored
This cl removes KioskNextShelfView and updates the shelf widget. Bug: 977019 Change-Id: Ie47157bf6c1ccc85de1c9d2b7aea1b7ce0f637ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1684757 Commit-Queue: Yilkal Abe <yilkal@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#676498}
-
Yi Gu authored
This reverts commit 52b6364a. Reason for revert: It caused some unexpected crashing. See https://crbug.com/983166. Suspecting that something is wrong with using GURL::GetOrigin(). Original change's description: > [VizHitTesting V2] Add dump without crash to identify sites with mismatch results > > This patch adds more info into the crash report, i.e. the report now > includes url, event type, global and local coordinates. > > Bug: 976284 > Change-Id: I70568ade1c94e018d5a42ef023b0eb65d9c40c55 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1689960 > Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org> > Commit-Queue: Yi Gu <yigu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#675995} TBR=sadrul@chromium.org,yigu@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 976284 Change-Id: I2ebc9e51b6e59578555ab5e70f9fa9c6d68c0d0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697072Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#676497}
-
Sinan Sahin authored
This CL changes the click target for the URL from the URL itself to the title and URL together (+some extra vertical padding) to make it easier to touch. Bug: 655359 Change-Id: I611cd198338610e85eff56623c560f82dade6566 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695858 Commit-Queue: Sinan Sahin <sinansahin@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#676496}
-
Yi Gu authored
Hit testing is skipped for MouseUp with mouse capture which is enabled by the OOPIF renderer. In such case we used to apply the coordinate transform in the browser process instead of the renderer process as we did for MouseDown. This leads to a mismatch between the two coordinate transforms in different processes. In this patch we cache the transform from the MouseDown event and apply it upon MouseUp such that the same coordinate transform is applied to both events. Bug: 934434 Change-Id: I828d663066ff402e5fe40281b3f68349531e5050 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1690717 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#676495}
-
Esmael El-Moslimany authored
Bug: 977936 Change-Id: I0ab6ef9fc26c532b86fbccadc75bcc2b91b616fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696357 Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#676494}
-
Mugdha Lakhani authored
Bug: 976041, 975857, 975365, 975317 Change-Id: I2ecd2b1d8b7b72492370773beaebb74f1d1544a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695299 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Auto-Submit: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#676493}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/455c41a014c7..7825d4983f90 git log 455c41a014c7..7825d4983f90 --date=short --no-merges --format='%ad %ae %s' 2019-07-11 benjaminwagner@google.com Add comparison of rendered SkPictures to Serialization unit test 2019-07-11 egdaniel@google.com Add kRGBA_8888_SRGB GrColorType and remove GrSRGBEncoded. Created with: gclient setdep -r src/third_party/skia@7825d4983f90 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=fmalita@google.com Change-Id: I103710a8affa60a19ec229901cb38c37e1a0b9f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697074Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#676492}
-
Friedrich Horschig authored
By adding the password to PSL labels, we make more clear that we fill not only username but also passwords when tapping a chip. Bug: 982784 Change-Id: Iea3fb6a537a47b16a32ea39c4ca4baa435885191 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695269 Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#676491}
-
Mohammad Refaat authored
The main problem was that a weak tab was provided to the existed method to generate the thumbnail from Tab. This can't be done with webState as by default WebState* is a weak ptr but it doesn't get invalidated after the webState is destructed. The solution is to change the thumbnailGenerator to a class instead of a method. An object from this class will contain a webState and will implement WebStateObserver, so it can invalidate the pointer when the webState is destructed. Then change all users to use the object instead of the block to generate the thumbnail image. Change-Id: Ia918723c9190ce9d1c1977fe595a1f02bbc7ab5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697051 Commit-Queue: Mohammad Refaat <mrefaat@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#676490}
-
Richard Knoll authored
This will use the extension name as context message for notifications shown via the notifications api to have the same behaviour as with chrome.notifications. The context message can not be overridden with this as the notifications api does not have support for that. It's still possible to do that via chrome.notifications though. Bug: 981655 Change-Id: I5fc8e97b3fa697a608c945b30429ef37b0469c97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692748 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
-
Juanmi Huertas authored
If the canvas has a mode fixed (acceleration or not acceleration), ShouldAccelerate should not change it even though the hint is set to the other side. This CR fixes that when the canvas is accelerated will stay accelerated. Changing unittest and fixing a series of tests that were affected as a side effect of blurriness. For the browsertests I'm making some test to activate pixels (as now these test are using accelerated canvas and we need to generate the pixels). Bug: 947532, 973448, 977179 Change-Id: I8814794e774f78aa3ad8147ff5dd6cc249c8b272 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617636Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Commit-Queue: Juanmi Huertas <juanmihd@chromium.org> Cr-Commit-Position: refs/heads/master@{#676488}
-
Fei Ling authored
Note that the change https://chromium-review.googlesource.com/c/enterprise/cel/+/1696026 is also required to fix all test cases. Change-Id: I2994ec2162d6443ed85407f746c0ad99ce050832 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695732 Commit-Queue: Fei Ling <feiling@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#676487}
-
Avery Musbach authored
See bug 982838 (linked below) for what is wrong with ending overview, and bug 982849 (linked below) for what is wrong with starting overview. Test: manual Bug: 982838, 982849 Change-Id: I07a8c46081b758f530c78b4a6be2067cba53dfc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696184 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#676486}
-
Victor Costan authored
Change-Id: I1c287f2a776bcbca749b58172dae274449cf1e43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695646 Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Reviewed-by:
Jarryd Goodman <jarrydg@chromium.org> Auto-Submit: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#676485}
-
Liquan(Max) Gu authored
Currently, the renderer crashes when creating mark entry in worker. The crash is because PerformanceMark::Create() return nullptr without setting exception_state. The caller of the function assumes that no exception indicates the PerformanceMark entry exists. Thus, when the entry is visited, the crash occurs. There is another bug hidden in this issue. Currently, when window-performance is not found, Create() returns nullptr directly. It should instead also check whether worker-performance exist. This CL fix these issues. To verify the change, the CL also changes the related web tests from *.html to *.any.js, which enables these tests in worker's context. Bug: 981982 Change-Id: Ia20ce1c194e4db2810ff3f1c52070e5970951600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696085 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#676484}
-
Esmael El-Moslimany authored
In paper-ripple, removing style "transform: translate3D(0, 0, 0)". Once the paper-ripple is created, the element shows up in layers as a slow scrolling rect due to this property. After removing I did not see a difference with ripples for cr-button or cr-icon-button. Bug: 982733 Change-Id: I0a4d10da136690cb46c9a3bde02d05613fbeb509 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696000 Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#676483}
-
Jack Steinberg authored
Additionally, this CL adds support for passing Elements as action in showToast, using the action setter. This change is the latest in a series of changes implementing new behavior added to the toast explainer in PR #43 https://github.com/jackbsteinberg/std-toast/pull/43. Bug: 972945 Change-Id: I46004883cb3b794981029aa02369918dd0077391 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1686786 Commit-Queue: Jack Steinberg <jacksteinberg@chromium.org> Reviewed-by:
Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#676482}
-
Robert Sesek authored
If the browser terminates shortly after launching a child process, the child will fail to look up the bootstrap server the browser was exposing in order to perform Mach port rendezvous. When this happens, rather than crashing due to follow-on failures, simply terminate the process cleanly. This situation occurs when when launching Content Shell with `--run-web-tests` but then not specifying a test case (so the browser exits cleanly right after launching child processes). It also appears to happen infrequently in production when the browser crashes. The crash reports that are generated from the child processes in this case are uninteresting, so exiting cleanly is a better solution that generating uninteresting reports. Bug: 980696 Change-Id: Id4733482b63c0d33931f25923744a103072dd5a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695961Reviewed-by:
Mark Mentovai <mark@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#676481}
-
Mike Frysinger authored
Migrate all print statements to functions, and have all modules import the print_function future even if they aren't using print directly. This will help keep bad print statements from slipping back in. Bug: 983071 Test: `./grit/test_suite_all.py` passes Change-Id: I818d2b69c1280ad0f0f7ef02acea8a68444920d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1698162 Commit-Queue: Mike Frysinger <vapier@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#676480}
-
Yao Xiao authored
Tested by expanding the existing service_worker_network_isolation_key_browsertest.cc and rename it to worker_network_isolation_key_browsertest.cc. Bug: 955476 Change-Id: I8d9dcca983049a870d33175550fbef958ef4054e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692968 Commit-Queue: Yao Xiao <yaoxia@chromium.org> Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#676479}
-
Mohammad Refaat authored
Extend them till 2020-07-01 Bug: 975840, 975669, 975532, 975084 Change-Id: Id3172dec81c0f5d47c8f31ffe118f51148b1e3c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695999Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Mohammad Refaat <mrefaat@chromium.org> Cr-Commit-Position: refs/heads/master@{#676478}
-
Jun Cai authored
Per comment at: https://chromium-review.googlesource.com/c/chromium/src/+/1682870 This CL creates a subdirectory device_dialog under: //chrome/android/java/src/org/chromium/chrome/browser/ //chrome/android/javatests/src/org/chromium/chrome/browser/ //chrome/browser/ui/android/ and moves device api related files into this subdirectory. This CL also adds OWNERS files for these subdirectory. Bug: None Change-Id: Id109e016b35876511ae2f211993b463a19ce8138 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696454Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
-
Daniel Rubery authored
For PhishGuard pings, we care about the originator of the currently visible content, not the URL of a pending navigation. Change-Id: I850782f31c0f5a604aeabc19cf21f26fd53bb98b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696386Reviewed-by:
-
Friedrich Horschig authored
For now, we always want to fill the entire name into a name field. This CL therefore replaces uses of the three separated name fields with the FULL_NAME field for addresses. Small fixes: * The empty state tests don't need to wait for suggestions. * The margin of fields should be at the end so they remain left-aligned. Bug: 962548, 965494 Change-Id: I09016638b31c3d8443dcc8d6c4adc4a170e9a80b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697190Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Reviewed-by:
-
Doug Arnett authored
This will allow Dev and Canary channel users the ability to try out the new intervention. Bug: 965277 Change-Id: I7c9db7f469f0d82881118777a2f57c2d9e825ff2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696351 Commit-Queue: Doug Arnett <dougarnett@chromium.org> Reviewed-by:
-
Kevin Bailey authored
Enabled by flipping feature, so we can disable it. Also tweaked a test which relied on old behavior. Bug: 118094 Change-Id: I680fb072d5c6a16a006a0e9144a6b7db6035c267 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695888 Commit-Queue: Kevin Bailey <krb@chromium.org> Reviewed-by:
manuk hovanesian <manukh@chromium.org> Cr-Commit-Position: refs/heads/master@{#676473}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ca160215c9d1..741b96b175cb git log ca160215c9d1..741b96b175cb --date=short --no-merges --format='%ad %ae %s' 2019-07-11 sprang@webrtc.org Pass RtpRtcp::Configuration to RtcpReceiver ctor and initialize ssrcs 2019-07-11 sprang@webrtc.org Optimize PacketRouter/RTPSender interactions. 2019-07-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision fff68b41..8bdf10df (675999:676126) 2019-07-10 sukhanov@webrtc.org Move datagram_dtls_adaptor from p2p/base/ to pc/ 2019-07-10 mbonadei@webrtc.org Add wrapper to normalize flags. 2019-07-10 titovartem@google.com Use 16000Hz audio in PC test when specified 2019-07-10 sukhanov@webrtc.org Implements method on RtpPacket to extract extension. 2019-07-10 kuddai@google.com Make force_fieldtrials persistent string during entire program live. 2019-07-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 34d38f69..fff68b41 (675873:675999) 2019-07-10 titovartem@google.com Reland "Fix collection of audio metrics from PC test framework for audio test" Created with: gclient setdep -r src/third_party/webrtc@741b96b175cb The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:None,chromium:None,chromium:None,chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I0fd8848395c08edef6240a384b20b9ed79fad54c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697237Reviewed-by:
-
Brandon Wylie authored
This change displays the google g in the omnibox (unfocused + focused). There is some tint jank when transitioning from the search loupe which will be fixed by a follow-up CL. Bug: 973153 Change-Id: I53940ee67bac3065b18505822a784e22bbb900be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653842 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Ender <ender@google.com> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Reviewed-by:
-
Daniel Nicoara authored
Drag interface has changed. Fixing compile error. BUG=None TEST=Compiled cast_shell Change-Id: I52f96f8f355a7cb80deb73ea8145111948c47144 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697308Reviewed-by:
Kevin Schoedel <kpschoedel@chromium.org> Commit-Queue: Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#676470}
-
Edvard Thörnros authored
The monolithic SMILTimeContainer->UpdateAnimations() method has been split into two methods, one for calculating the values and one for calculating the progress of the animation. This will later lead to more refactoring and is the first step. Bug: 641437 Change-Id: I93bb6f9cb514f899537e8aca4c8574839e48be7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697191 Commit-Queue: Edvard Thörnros <edvardt@opera.com> Auto-Submit: Edvard Thörnros <edvardt@opera.com> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#676469}
-
Tatiana Buldina authored
These commands are not standard, and were never fully implemented in Chrome. Change-Id: I018d1ecf292ffb16f360c0ba7636e16a7425c913 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695622Reviewed-by:
-
Daniele Castagna authored
viz::BufferQueue currently implements partial swap reading back from the previously swapped buffer contents that are outside the current swapbuffer damage. This introduces a dependency on a GPU API, that we want to get rid of (crbug.com/958670). This technique also assumes it is safe to read back from a buffer that is used from another driver (crbug.com/457511). This CL removes the readback and solves the same problem exposing a rectangle that the compositor needs to redraw to make sure contents damaged during all the swapbuffers before the current one are recomposited. Bug: 958670, 457511 Test: BufferQueueTest.PartialSwapCurrentBufferDamage Change-Id: I2d4a70b0122f665b68e25e043d57de6044092fc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1685909Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Commit-Queue: Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#676467}
-
Robert Liao authored
BUG=979530 Change-Id: I7d1a987b5d9f15bf285f730ec0269c3765f227bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696188Reviewed-by:
Wei Li <weili@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Auto-Submit: Robert Liao <robliao@chromium.org> Commit-Queue: Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#676466}
-
Martin Robinson authored
When we get a reference to an AtkObject child, we need to unref it. Bug: 961029 Change-Id: I6fbd4b81daf2af048ca2a0443955a5af2a77745d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697645Reviewed-by:
Joanmarie Diggs <jdiggs@igalia.com> Commit-Queue: Martin Robinson <mrobinson@igalia.com> Cr-Commit-Position: refs/heads/master@{#676465}
-
