- 11 Jul, 2019 40 commits
-
-
David Staessens authored
This CL changes the logic used to disable frame validation when running the video_decode_accelerator_tests binary. Currently when '--disable_validator' is specified the frame validator will be disabled and the thumbnail test will be run. This CL changes this logic to automatically switch to the thumnail test when support for import mode is not detected. The '--disable_validator' parameter is now used to both disable the video frame validator (on platforms supporting import mode) and the thumbnail test (on platforms only supporting allocate mode). TEST=./video_decode_accelerator_tests on nyan_big BUG=None Change-Id: Ia79acd8557ad102ac6ab4c97a5d1502818a14a83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1688493 Commit-Queue: David Staessens <dstaessens@chromium.org> Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#676238}
-
Alex Khouderchah authored
Bug: 975280, 975081 Change-Id: Iffa7f24ea7c8eeb7c2df2e4f5540e9794edfa2c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696082 Auto-Submit: Alex Khouderchah <akhouderchah@chromium.org> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#676237}
-
Alex Cooper authored
For immersive sessions the XRFrameProvider checks if the session is still present before continuing execution, but no similar checks are done to the inline sessions. This fixes that behavior. Bug: 982971 Change-Id: I63c9476bde10e4b399b432fd446966436919e68f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696685 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Bill Orr <billorr@chromium.org> Reviewed-by:
Bill Orr <billorr@chromium.org> Auto-Submit: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#676236}
-
Jinsuk Kim authored
https://crrev.com/c/1659652 introduced flickering in toolbar in TWA. There is a race between BrowserControlsOffsetHelper and FullscreenManager which get its current tab updated via observer. The issue happens when the former calls the latter which still refers to the old tab. This CL addresses it by merging BrowserControlsOffsetHelper into ChromeFullscreenManager to use a single tab observer. Bug: 978941 Change-Id: Ifb8e2f404c9070a51d418a5f232b62dfd6819c39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1683355 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#676235}
-
Alex Danilo authored
Adds support for the 'error' status returned from file operations in progress. Also allows the error panel item to be dismissed. The error message can be too long to show on one line with the maximum width of the panels, so it's split into 2 lines using regexps. This will need an integration test to make sure translations fit in the maximum width without generating ellipsis. Bug: 947388, 979374 Change-Id: I3d33a5ab821c574cc454fb3520089cd949898e4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692422Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Alex Danilo <adanilo@chromium.org> Cr-Commit-Position: refs/heads/master@{#676234}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/fba3e64e8086..8db211bc8d28 git log fba3e64e8086..8db211bc8d28 --date=short --no-merges --format='%ad %ae %s' 2019-07-10 jonahr@google.com Fix CopyTexture to support GL_LUMINANCE/ALPHA/LUMINANCE_ALPHA Created with: gclient setdep -r src/third_party/angle@8db211bc8d28 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:773861 TBR=cwallez@chromium.org Change-Id: Ieb6bcfc4f3f164cb14f4552d9383efd57676e2d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696535Reviewed-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@{#676233}
-
Ionel Popescu authored
This change adds support for adjusting the default styling for HTML elements as defined in core/html/resources/html.css in order to provide an updated style when using the refreshed controls UI. Also this change is updating the UI for text related types as an example of how the default styling is adjusted when the FormControlsRefresh is enabled. Bug: 981983, 981984 Change-Id: I8fd32cc090cb8e5d785f758acbed7c3900e5e482 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691321Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Ionel Popescu <iopopesc@microsoft.com> Cr-Commit-Position: refs/heads/master@{#676232}
-
BUG=762641 TBR=stevenjb@google.com Change-Id: If963a7ac93e0cd6648a0bd07538861bed20dae7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696764Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#676231}
-
Ben Kelly authored
This CL also adds the cache-storage-sequence virtual test suite for cache_storage and service worker wpt tests. Bug: 960012 Change-Id: I959a7ba5dd7a3336744301a158a5bd06bf5d158b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670487Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#676230}
-
Min Qin authored
Some servers don't handle range request very well, they can send a different range of the content that cannot be decoded if content-encoding is used. In that case, we should treat the interrupt reason as SERVER_NO_RANGE. Currently, bad range is treated as SERVER_BAD_CONTENT. That will cause download to no longer resume as the resume mode is invalid. And decoding failure is treated as NETWORK_FAILED. That causes the download to resume over and over without making any progress. BUG=978584 Change-Id: Ic83bf0e050b98730ff1b82f111bb45ae6cb71509 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696176 Commit-Queue: Min Qin <qinmin@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#676229}
-
Jeevan Shikaram authored
This CL removes the pin to shelf toggle from the metadata view and places it as the first row item. The pin to shelf item is also hidden for the main browser app. Bug: 977054, 971528, 965906 Change-Id: I4699adff9effb61711407ffa7876b2e10195d876 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670630 Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#676228}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/edc9d42942af..b79dda949e88 git log edc9d42942af..b79dda949e88 --date=short --no-merges --format='%ad %ae %s' 2019-07-10 benjhayden@chromium.org Servicify upload and api. 2019-07-10 bikineev@chromium.org Add metrics for Blink GC background sweeping events Created with: gclient setdep -r src/third_party/catapult@b79dda949e88 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:941888,chromium:917914,chromium:918193,chromium:967258 TBR=sadrul@google.com Change-Id: I97210b01164eabf01f383dec973c9faccf264192 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696538Reviewed-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@{#676227}
-
Dana Fried authored
Method was never implemented. Change-Id: Ide33c82c110888e0b4075eb7403f2cbb067e524f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696342 Commit-Queue: Dana Fried <dfried@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#676226}
-
Noel Gordon authored
ImageLoaderClient is throwing DOM exceptions while processing requests {ImageLoaderRequest} that have no request URL. Odd, the request URL is required (it keys the ImageLoader caches). Tracked the source of these “no-url” requests down to the FileList thumbnail loader. The FileList thumbnail loader sends ImageLoaderClient requests for the file list entries while the user is scrolling the FileList. So it is a good idea to avoid doing unnecessary work therein (it’s hot code). Change the FileList thumbnail loader to setup the URL first and reject early with an ImageLoaderResponse error if there is no URL to request. Enjoy the faster scrolling, CPU and power savings, that result. Bug: 965370 Change-Id: I5dd9a1390bc1f92010aea1b4ca2e8a50b67177df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695661Reviewed-by:
Alex Danilo <adanilo@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#676225}
-
John Emau authored
Bug: 963183 Change-Id: I66347f5fae2e327127d9c06a2b4db0518af7c6c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1683132Reviewed-by:
Erik Luo <luoe@chromium.org> Commit-Queue: John Emau <johnemau@microsoft.com> Cr-Commit-Position: refs/heads/master@{#676224}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/f970253a5d41..c538b5d796fb git log f970253a5d41..c538b5d796fb --date=short --no-merges --format='%ad %ae %s' 2019-07-10 johnkslang@users.noreply.github.com Merge pull request #1832 from jeffbolznv/issue1828 Created with: gclient setdep -r src/third_party/glslang/src@c538b5d796fb The AutoRoll server is located here: https://autoroll.skia.org/r/glslang-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. TBR=radial-bots+chrome-roll@google.com,cwallez@chromium.org Change-Id: Ic5d679f14142c6476acbd259035ff96fbd03ff39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696118Reviewed-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@{#676223}
-
chrome://gpuSunny Sachanandani authored
Bug: 926173 Change-Id: I04dfcd239ccacd1c68ca7a2b170aa5f22c4d349e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696349 Auto-Submit: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#676222}
-
Alex Danilo authored
Remove the file and migrate any needed selectors to custom elements that use them, and the main file_manager.css file. Also removes the file reference in the python testing script. Bug: 947388 Change-Id: I0673fa6cb819fdee0f50cc6749e87e1e25020430 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691949 Commit-Queue: Alex Danilo <adanilo@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#676221}
-
Josh Nohle authored
In v2 DeviceSync, CryptAuth will not return the encrypted group private key in a SyncMetadata response if other devices in the group have not uploaded the encrypted key yet, for instance if they are offline when a new device joins the group. And, devices without the group private key cannot decrypt device metadata sent in the SyncMetadata response. This metadata contains a public key used for multidevice (BetterTogether) features and a PII-free device name at the moment. In this CL, we allow devices to be stored without decrypted metadata. This is necessary to preserve the existing multidevice setup flow after migrating to v2 DeviceSync; only device names and supported features are needed to preserve the flow. See go/cros-devicesync-v2-multidevice. Bug: 951969 Change-Id: Id2986f866be5a86ea0b20afe5fffc1b9693c070c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695963 Commit-Queue: Josh Nohle <nohle@chromium.org> Auto-Submit: Josh Nohle <nohle@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#676220}
-
Evan Stade authored
This covers all non-mac tests that used these notifications. They now use BrowserListObserver instead. Additionally, some includes are cleaned up. Specifically, includes removed from interactive_test_utils.h are added to some testing files which relied on these transitive includes. Bug: 268984 Change-Id: I27b68e14e83401e6d938fcf6eb38c431bc1f7b58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1684512Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#676219}
-
Adam Langley authored
https://boringssl.googlesource.com/boringssl/+log/cfcb0060e8b8fba92d275fa4ac27d369890ea9bf..09050cb498336655883157c6e6055db9e5542857 The following commits have Chromium bugs associated: 365b7a0fc Remove android_tools checkout 3f98fde5a Add android_sdk checkout Bug: 428426 Change-Id: I01262fddf972896d23591d722ae2343729abbfcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696178 Commit-Queue: Adam Langley <agl@chromium.org> Commit-Queue: David Benjamin <davidben@chromium.org> Reviewed-by:
David Benjamin <davidben@chromium.org> Cr-Commit-Position: refs/heads/master@{#676218}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/41300af8768c..16850598db2b git log 41300af8768c..16850598db2b --date=short --no-merges --format='%ad %ae %s' 2019-07-10 titovartem@webrtc.org Add support of quick test mode into PC framework Created with: gclient setdep -r src/third_party/webrtc@16850598db2b 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. TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ib16a0687a458fd42cbb014670291edd8c6b37d82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695894Reviewed-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@{#676217}
-
David Staessens authored
This CL fixes the new video decoder tests failing on platforms that don't support import mode. Even if no actual rendering is done in the tests, we still need to create a video frame object as this is the expected output format. TEST=./video_decode_accelerator_tests on nyan_big BUG=981714 Change-Id: I4c9dc33516a76f2b0b87589b0682ec15e150f319 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1688770 Commit-Queue: David Staessens <dstaessens@chromium.org> Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#676216}
-
Josh Nohle authored
Change-Id: Ibf2f317ec469144d854c78d34acdf596f65c50ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696645 Commit-Queue: Josh Nohle <nohle@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Auto-Submit: Josh Nohle <nohle@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#676215}
-
Ted Meyer authored
Splitting up the CL for D3D11 reporting max resolutions Change-Id: I974fd24d49ce086398caf3bec0a7daa92eff8e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696177 Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#676214}
-
Thoren Paulson authored
On Android, this was a dangling reference, causing crashes at startup. Bug: internal b/136249537 Test: CQ Change-Id: I532e45fc2199ef4e4043931fa10088f4df201216 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1685687 Commit-Queue: Thoren Paulson <thoren@chromium.org> Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Auto-Submit: Thoren Paulson <thoren@chromium.org> Cr-Commit-Position: refs/heads/master@{#676213}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Ic858519ec2c6d071b1ef43b17aa61c11b6346d28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696117Reviewed-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@{#676212}
-
Katie D authored
The autoclick scroll bubble animation was jumpy because the arrow and anchor rect changes both kicked off animations. This gives subclasses of BubbleDialogDelegateView the option to set the arrow without creating an animation, in order to fix the visual bug. Bug: 978163 Change-Id: Id4feb50e35a3945c24e5759d953261a02dd4970c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691549 Commit-Queue: Katie Dektar <katie@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Reviewed-by:
Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#676211}
-
Rob Schonberger authored
By doing so, note that a break in a for loop is not appropriate when not all items are cancelled. So only cancel if all items are cancelled, etc. Bug: 982118 Bug: 946868 Change-Id: I098eb046b9e0407493033b865ad6bb38a1ec5231 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1694281 Commit-Queue: Rob Schonberger <robsc@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Cr-Commit-Position: refs/heads/master@{#676210}
-
Anubha Mathur authored
Fixed the following accessibility issues in Sources Panel navigator pane and editor pane: - Problem: No way to access nodes under FileSystem and Overrides panes in the Navigator view using keyboard Fix: Fixed by autoselecting the first node in these trees, so when you tab into the div containing the tree, some node is selected, and you can use keyboard to navigate through them - Problem: Color contrast issue with lineNumbers in the editor Fix: Replace rgb(128, 128, 128) with equivalent hsl(0, 0, 50.2) and make it darker by changing lightness percentage to 46%, i.e. hsl(0, 0, 46) Added following tests: - a11y-axe-core\sources\sources-left-pane-a11y-test.js: Axe test for Sources panel Navigator pane - a11y-axe-core\sources\sources-editor-pane-a11y-test.js: Axe test for Sources panel Editor pane Images showing new colors in the Editor pane: https://imgur.com/orA26yS (dark theme) https://imgur.com/VSeTXck (light theme) Video showing selection of FileSystem contents by default https://imgur.com/l7wMKx6 Change-Id: I191d915818039455aeb7d9c6869c16b76d7ceeb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593550Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Commit-Queue: Anubha Mathur <anubmat@microsoft.com> Cr-Commit-Position: refs/heads/master@{#676209}
-
Fabrice de Gans-Riberi authored
* Implement Frame.GetRemoteDebuggingPort. * Move all remote debugging handling in the Context process to WebEngineRemoteDebugging. * Change the debug DevTools behavior to not fallback on attempting to listen on IPv6 localhost in case of failure on IPv4 localhost. * Refactor the GetDevToolsListFromPort() test utility out of WebEngineDebugIntegrationTest to be shared with WebEngineIntegrationTest. * Fix a potential issue when the DevTools service fails to start and the debug DevTools listeners were not notified. In ContextImpl, the OnDevToolsPortReady() callback was only called when the DevTools service opened. It is now systematically called during browser process start-up and |devtools_port_received_| keeps track of that call in ContextImpl, rather than assuming a 0 value for |devtools_port_| means the service start was never requested. Bug: 973268 Change-Id: I58d15c0656ebe1adfe6c254e4aefc0c7bfd54176 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670441Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org> Cr-Commit-Position: refs/heads/master@{#676208}
-
Nathan Zabriskie authored
This CL starts adding more timestamps to the new FrameTimingDetails that is sent back to Viz clients after a frame is presented. Eventually these timings will be used to determine abnormally long stages of the rendering pipeline in the case of missed frames. This CL simply adds the timestamp of when the display compositor receives a submitted compositor frame and when it begins the DrawAndSwap. Bug: 963780 Change-Id: I3ca4715689401d0544c7efb17a9a096e2534131d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655738 Commit-Queue: Nathan Zabriskie <nazabris@microsoft.com> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#676207}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/5fcd7aab39b8..9231ac5e1c68 git log 5fcd7aab39b8..9231ac5e1c68 --date=short --no-merges --format='%ad %ae %s' 2019-07-10 nigi@chromium.org Fix issue with missing thin diagonal lines. 2019-07-10 thestig@chromium.org Roll build/ 5a8b627ed..f52a9d0c5 (268 commits) 2019-07-10 tsepez@chromium.org Pass CPDF_Font itself to CFGAS_GEFont::LoadFont() 2019-07-10 nigi@chromium.org Fix undo and redo actions for replacing string. 2019-07-10 thestig@chromium.org Make IXFA_DocEnvironment::PopupMenu() pass a CFX_PointF by const-ref. 2019-07-10 tsepez@chromium.org Observe CXFA_FFWidgets in CPDFSDK_XFAWidget. Created with: gclient setdep -r src/third_party/pdfium@9231ac5e1c68 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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:982828 TBR=pdfium-deps-rolls@chromium.org Change-Id: Ia7a1f47c5e31820d6d16e44e5dca6aeffb8bae77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695830Reviewed-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@{#676206}
-
Evan Stade authored
Follow up to a70c7dd5 TBR=tsepez@chromium.org Bug: 958208 Change-Id: Iae4f56e9e9fca775a15567db619b527030ddfd48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1693769 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#676205}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9b7fc04d3edb..2bf119af6d9c Created with: gclient setdep -r src-internal@2bf119af6d9c 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=hcarmona@google.com,hajimehoshi@google.com,jbroman@google.com Change-Id: I88d247835ee76c7893be2c6d94cb448ab18acb6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696127Reviewed-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@{#676204}
-
Eric Willigers authored
Check that CSS Alignment properties accept only the values permitted by the spec https://drafts.csswg.org/css-align-3/#property-index Change-Id: I93b00ac2280ca4991c24b3ee35a17047e165b8a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1694928Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#676203}
-
siashah authored
https://screenshot.googleplex.com/PX7Cx2S77mP Change-Id: I2198461696e6bc3d5dd1e6cad2530f3e27598c1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1688335 Commit-Queue: Siddharth Shah <siashah@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Cr-Commit-Position: refs/heads/master@{#676202}
-
Antonio Gomes authored
This CL is a preparation step to Onion soup webmediaplayer_ms.cc|h and webmediaplayer_ms_compositor.cc|h It adds to blink::Platform a methods that expose SharedMainThreadContextProvider() functionality of RenderThreadImpl needed by WebMediaPlayerMS. It is part of the phase 4.4 in the design doc [1]. [1] https://docs.google.com/document/d/1rHJGi1U72qZsOGIctIf7GKRaY8d7BgtVW8MaMYumzYY/ BUG=704136 R=guidou@chromium.org, haraken@chromium.org Change-Id: I3e6534e1a7e362da905ddd78e7e88d51adb5e6eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1693241 Commit-Queue: Antonio Gomes (use @igalia instead) <tonikitoo@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#676201}
-
Evan Stade authored
Bug: none Change-Id: I685d189ce5b58e8eb699d8ecece4c8985053b737 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1693767Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#676200}
-
Dale Curtis authored
Seems we need to repaint always when the first frame is available, not just in lazy load circumstances. This is a speculative fix, since I have not been able to reproduce the issue locally. BUG=982415,980897 R=sandersd Change-Id: I318ebb03f749fab9112a592047d1c45b77ceed12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695829 Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#676199}
-