- 04 Jun, 2019 40 commits
-
-
Julie Jeongeun Kim authored
This CL is a precursor CL to moving WebApplicationCacheHostImpl to loader. It renames RendererWebApplicationCacheHostImpl to ApplicationCacheHostForFrame in order to mirror ApplicationCacheHostForSharedWorker and prepare merging WebApplicationCacheHost into ApplicationCacheHost. Bug: 950159 Change-Id: I31928152f6a58de93d5b6264676cbfc64b1b3de1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642848Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#665850}
-
Henrique Ferreiro authored
These were missing from https://crrev.com/c/1486337. Bug: 796544 Change-Id: Ib9fcf8a49a88f3351c49fe67a922dac0c7b9d8f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635521Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com> Cr-Commit-Position: refs/heads/master@{#665849}
-
Kamila authored
Change-Id: I413da11c398066f6be545660afe5512abde16fc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639386Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Commit-Queue: Kamila Hasanbega <hkamila@google.com> Cr-Commit-Position: refs/heads/master@{#665848}
-
Edward Jung authored
Allows these Web UI interstitials to respond to OS level theme preferences. Bug: 934901,947840 Change-Id: Ibb6f6c58ca9938cd2539900458007eb7b0e25cd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634883Reviewed-by:
Carlos IL <carlosil@chromium.org> Commit-Queue: Edward Jung (EMEA) <edwardjung@chromium.org> Cr-Commit-Position: refs/heads/master@{#665847}
-
Victor Hugo Vianna Silva authored
Bug: 955475 Change-Id: I8a393c33dabe8a974acee4cf27acdc7f8a08c4d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634695Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Auto-Submit: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/master@{#665846}
-
Hugo Holgersson authored
When two candidates are equally close to our current focus F, SpatNav now prioritizes the candidate that can "absorb" most of F's horizontal or vertical projection. The spec calls this "projected overlap" [1]. When a document is focused (or when activeElement is null), SpatNav projects the document's edge onto each candidate. More generally, when looking inside (and outside) any focused box, we project the box's _edge_ onto each candidate. Note: The current spec [1] suggests us to remove |navigation_axis_distance| from the formula but if we do, snav-symmetrically-positioned.html will fail. So let's keep it until we find a simpler/more robust formula that can handle this pattern. [1] https://drafts.csswg.org/css-nav-1/ Bug: 958845 Change-Id: Id90bce78c9e9d985e6936716b8dafce883b07540 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594724Reviewed-by:
David Bokan <bokan@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Commit-Queue: Hugo Holgersson <hholgersson@fb.com> Cr-Commit-Position: refs/heads/master@{#665845}
-
Alexander Hendrich authored
This CL adds a new device policy to whitelist certain USB devices for certain urls in order to be used by the WebUSB API. We already have a user policy for that, so this device policy reuses the existing user policy's infrastructure. Bug: 968373, 854329 Change-Id: I21a80f0b6557a1270a8fd6243f07e2fc8682004a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636350 Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#665844}
-
Maksim Sisov authored
Previously, unittests for the buffer manager exercised only the host part. Now, they are also exercising the buffer manager gpu part and reinitialization of the mojo connection between the gpu and host. Bug: 969608 Change-Id: I07af295d5a75ba6cf3f73caa7a74e3e6ec24f180 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640538 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Cr-Commit-Position: refs/heads/master@{#665843}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/7b275a5af161..e13c1f46dc1a git log 7b275a5af161..e13c1f46dc1a --date=short --no-merges --format='%ad %ae %s' 2019-06-01 apodtele@gmail.com Solidify VC2005 builds. Created with: gclient setdep -r src/third_party/freetype/src@e13c1f46dc1a The AutoRoll server is located here: https://autoroll.skia.org/r/freetype-chromium 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:linux_chromium_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:mac10.13_retina-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel TBR=bungeman@google.com,drott@google.com Change-Id: I514a69db3efb9c1462a5d9afa4bece25205eb72f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641212Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
Dominik Röttsches <drott@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#665842}
-
Mathias Carlen authored
Before this patch the terms section was always shown. There are occasions where that section does not make sense. This patch introduces a new flag to hide the T&C section altogether. Bug: b/134096141 Change-Id: I83dd88f35151934ad4c8c4b8e276582024294441 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640991 Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#665841}
-
Carlos IL authored
Bug: 967750 Change-Id: Ic02e70a59aec016fe204deb09fac8d95daf2858c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631672 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Auto-Submit: Carlos IL <carlosil@chromium.org> Cr-Commit-Position: refs/heads/master@{#665840}
-
David Jean authored
Bug: 968114, 968115 Change-Id: Id7911c21f1609839994b742f38bac0eb6cea0864 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640540Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: David Jean <djean@chromium.org> Cr-Commit-Position: refs/heads/master@{#665839}
-
Max Morin authored
Bug: 965235 Change-Id: I9a172d2d549ed459f85b23133d7e046e01cefdec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630158 Auto-Submit: Max Morin <maxmorin@chromium.org> Reviewed-by:
-
David Tseng authored
1. the <input> for this preference was actually missing. 2. when enabled, we should also dump the output log to the console Change-Id: I7852dc3dcc6ef8b8164d4e74e1483e1664bd049d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639326Reviewed-by:
David Tseng <dtseng@chromium.org> Reviewed-by:
Sara Kato <sarakato@chromium.org> Commit-Queue: Sara Kato <sarakato@chromium.org> Auto-Submit: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#665837}
-
Maksim Sisov authored
Previously, the manager had been rerouting calls to GpuMainThread to make mojo calls. That thread is not really meant for IPC. Instead, make calls on IOChildThread for consistency. Bug: 969603 Change-Id: I351768c4a36973bd791c02c1f65080c65b9a0a7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640398 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Michael Spang <spang@chromium.org> Cr-Commit-Position: refs/heads/master@{#665836}
-
François Degros authored
Bug: 778674 Change-Id: If24284710325335dc9a33d61773fbf69a9167cc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642435 Auto-Submit: François Degros <fdegros@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#665835}
-
Alexey Baskakov authored
Fix error handling if WebContents gets closed/destroyed or a blink renderer process dies. Drive-by: Avoid posting caller's callback to ThreadTaskRunnerHandle, let's PostTask with weak |this| and call the callback via std::move(calback) instead. Typically, an owner owns WebAppDataRetriever and posts Unretained |this| pointer for data retrieval completion. Bug: 901226 Change-Id: I3ed1928ae3acb0f5c89f62b7bfbe3772689ff7a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637016Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#665834}
-
Maksim Sisov authored
Currently, WaylandWindow may attach a null buffer to a surface, which makes the Wayland compositor skip the buffer release call even though there was a buffer attached. The skipped buffer release call results in a missed submission callback, and the Chromium display compositor starts to lag behind one frame. What is more, we no longer trigger a buffer swap completion callback before presention feedback is provided, which also results in DCHECK when checking the order of the callbacks. Bug: 968497 Change-Id: I12494e78fa376d6c421b7366d0bddb52ae59a5af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636354 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
-
Darren Shen authored
Causing failures on mac. TBR=hayato@chromium.org Bug: 970135 Change-Id: Ib8b96084ad5bfee19cabbe011524c7fa8419bf46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642611Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#665832}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/8893ef1b..cd6e781b Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ia67adbc2d4e83d086c129a8eecc5237dde7eeee9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643048Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#665831}
-
Maksim Sisov authored
This is a prerequisite CL to make WaylandCanvasSurface listen to OnSubmission and OnPresentation callbacks. The following changes have been made to avoid code duplicates: * Added WaylandSurfaceGpu interface, which has two methods: OnSubmission and OnPresentation. * Moved RegisterSurface, UnregisterSurface, GetSurface from WaylandSurfaceFactory to WaylandBufferManagerGpu * Overrode WaylandSurfaceGpu methods in: ** GbmSurfacelessWayland and removed usage of WaylandSurfaceFactory. Now, everything is managed by the WaylandBufferManagerGpu instead. ** WaylandCanvasSurface and added NOTIMPLEMENTED. The idea is to propagate the results to a VSyncProvider and avoid tearing when submitting new frames. Bug: 963854 Change-Id: Ia91b359e505c152512db244b540d175ce1eeb0aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640977Reviewed-by: -
Maksim Sisov authored
Wayland code uses "wayland" category. "Wayland" was added here by mistake. Thus, remove it. Bug: 578890 Change-Id: Ia8988559c6fc52177910c15a118ecd1602f21dbb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640409Reviewed-by:
Ehsan Chiniforooshan <chiniforooshan@chromium.org> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#665829}
-
Ramin Halavati authored
ContentSettingsPref and ContentSettingsPrefProfovider classes receive an |incognito| argument that actually triggers the off-the-record behavior and is not necessarily an incognito mode specifier. The argument and all related items are renamed to off_the_record to remove ambiguity. Bug: 968028 Change-Id: Ida0818f993baef9ebc3c9521d24c2b8ae2b10c66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634729 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Auto-Submit: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Raymes Khoury <raymes@chromium.org> Cr-Commit-Position: refs/heads/master@{#665828}
-
Darren Shen authored
This reverts commit 207c5a51. Reason for revert: Possible culprit for 970084 Original change's description: > [ChromeDriver] Implements ExecuteAsyncScript promise-handling. > > Handles promises according to W3C-spec > (https://w3c.github.io/webdriver/#execute-async-script) for asynchronous > user scripts. This removes the global "result" object that contains > results of the latest script to execute and allows for scripts to wait > until results are ready before returning (instead of polling for > results after the script completes). > > run_py_tests.py. > > Tested: WPTs webdriver/test/execute_async_script, and python > Bug: chromedriver:2398 > Change-Id: I9f6cdeb5b3e93fcfd3e63090ce8b3aed275d71be > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636627 > Commit-Queue: Rohan Pavone <rohpavone@chromium.org> > Reviewed-by: John Chen <johnchen@chromium.org> > Reviewed-by: Caleb Rouleau <crouleau@chromium.org> > Cr-Commit-Position: refs/heads/master@{#665589} TBR=crouleau@chromium.org,johnchen@chromium.org,rohpavone@chromium.org Change-Id: I9e6c7aa0ac7f3df265c584a841afa9828a2cec4f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromedriver:2398 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642431Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#665827}
-
Alexandre Courbot authored
This is a reland of 91b0391f. Original change's description: > media/gpu/v4l2svda: fix stateless API specification violation > > The stateless API states that resolution of frames should be set on the > OUTPUT queue, and the coded resolution read back from the CAPTURE queue. > However we were setting the resolution on the CAPTURE queue and > expecting the ioctl to update it to the coded resolution. > > This works with our current kernel drivers, but is not correct with > respect to the stateless codec API specification. The kernel drivers > have been updated to support the correct behavior, so carry that change > into Chromium as well. > > Bug: 948534 > Test: Checked that VDA unittest passes on Kevin and Minnie with kernel > driver fixes. > > Change-Id: I8f589f81ae1a7d8223235739f0748e58ac25e342 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553124 > Reviewed-by: Hirokazu Honda <hiroh@chromium.org> > Commit-Queue: Alexandre Courbot <acourbot@chromium.org> > Cr-Commit-Position: refs/heads/master@{#659876} Bug: 948534 Bug: 968392 Test: Checked that video_VideoSeek.vp8.switchres passed on Minnie. Change-Id: Id7b2e60947a275175622ac9cfcce3a604caeb0f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635125Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Cr-Commit-Position: refs/heads/master@{#665826}
-
Takashi Toyoshima authored
This is a reland of 0fdf975b Original change's description: > OOR-CORS: Setup virtual layout tests for non OOR-CORS mode > > Now the OOR-CORS is enabled by default at m76, but we want to > run some of layout tests w/o OOR-CORS for the potential risk > to postpone the launch beyond the m76. Legacy code path should > work well until then. > > Bug: 905971 > Change-Id: Ife79c90a031c9b729c629509da83e1ff2ac2a2c4 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635081 > Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> > Reviewed-by: Yutaka Hirano <yhirano@chromium.org> > Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org> > Cr-Commit-Position: refs/heads/master@{#665506} NOAUTOREVERT=true TBR=yhirano@chromium.org Bug: 905971 Change-Id: I897730a276841da5c0b274ba446f84064ca8469b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642907Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#665825}
-
Yoichi Osato authored
This CL splits the interface to two parts so that WebRequestProxyingWebSocket or extensions proxy only handshake of WebSocket: interface WebSocketHandshakeClient { OnStartOpeningHandshake(WebSocketHandshakeRequest request); OnFinishOpeningHandshake(WebSocketHandshakeResponse response); OnAddChannelResponse(string selected_protocol, string extensions); }; interface WebSocketClient { OnDataFrame(bool fin, WebSocketMessageType type, array<uint8> data); OnFlowControl(int64 quota); OnDropChannel(bool was_clean, uint16 code, string reason); OnClosingHandshake(); OnFailChannel(string reason); }; Performance gain of receive-arraybuffer-1MBx100.html: Mine: 1050 ms ToT : 1221 ms Relanding: The previous patch was reverted because of a browser test of "--disable-features=NetworkService". This patch fixes it to adapt a WebRequestAPI test to both expectations. Reverted-change: https://chromium-review.googlesource.com/c/chromium/src/+/1628497 Bug: 865001, 942989 Test: browser_tests --gtest_filter=*ExtensionWebRequestApiTest* (--disable-features=NetworkService) Change-Id: I24d573c0a977d4557cc8c211900a110e73fb996e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630084Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#665824}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/b75606a39adb..40ec586a32ab git log b75606a39adb..40ec586a32ab --date=short --no-merges --format='%ad %ae %s' 2019-06-04 tsepez@chromium.org Make fpdfdoc layer live above all of fpdfapi. Created with: gclient setdep -r src/third_party/pdfium@40ec586a32ab 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. TBR=pdfium-deps-rolls@chromium.org Change-Id: Ia5465fb7e1acc11844c89420263866d67d23c10b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640810Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/9005e23a2639..bd002715a898 git log 9005e23a2639..bd002715a898 --date=short --no-merges --format='%ad %ae %s' 2019-06-04 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 584b49b1..1070231d (665633:665750) 2019-06-03 sukhanov@webrtc.org Move datagram transport to JsepTransport Created with: gclient setdep -r src/third_party/webrtc@bd002715a898 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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I50d9292906e6a0b892e6f9dfb00a4c5fb98ddf0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640806Reviewed-by:
-
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: Iab12971e8996897b10c96a62b2b776e6f6a3b666 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642280Reviewed-by:
-
Yuzu Saijo authored
This CL reverts back a part of https://chromium-review.googlesource.com/c/chromium/src/+/1627834 and making IPC task runner unfreezable for now. In the long run (after the next CL https://chromium-review.googlesource.com/c/chromium/src/+/1640738 is ready), it will be freezable again. This is just to make sure that we are not breaking anything by making the messages frozen. Change-Id: I97f06320dd9c65c1bc73e08fca55ca4aa4bfcfe1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642609Reviewed-by:
-
Alexandre Courbot authored
The stateless codec API requires us to set the resolution on the OUTPUT queue. This however can only be done if the queue is streamed off. Do this when changing resolution so we can conform to the stateless codec API. Bug: 968392 Test: Checked that video_VideoSeek.vp8.switchres passed on Minnie. Change-Id: I44e50fada7472d159b75711cde3fc0c5661e08e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635124Reviewed-by:
-
John Abd-El-Malek authored
Bug: 934009 NOPRESUBMIT=true Change-Id: Ib803d9eefd306ffb43f5550f9e9502668d0b6511 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639350 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#665818}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4c5f9b2027a6..4b1386c027fe Created with: gclient setdep -r src-internal@4b1386c027fe The AutoRoll server is located here: https://autoroll-internal.skia.org/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 BUG=chromium:967762,chromium:947531,chromium:947531 TBR=harringtond@google.com,orphis@google.com,shend@google.com Change-Id: Icd2b96ee9165b7cc033c8f172957104a37046f3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640746Reviewed-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@{#665817}
-
rajendrant authored
The WarmupURLFetcherCallback histogram could get recorded more number of times depending on retries. Bug: 969795 Change-Id: I13b65dfe4a0fd7a70047f912ff960c201c2eb719 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641811Reviewed-by:
Robert Ogden <robertogden@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#665816}
-
Abhijeet Kandalkar authored
ListHashSet is deprecated in favor of LinkedHashSet. HeapLinkedHashSet's invalidate iterators when the container is modified. This does not happen in this usage, so replacement is simple. Bug: 614112 Change-Id: I33452c4957e20babb222e6e0257cfd119e861896 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639725Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Abhijeet Kandalkar <abhijeet@igalia.com> Cr-Commit-Position: refs/heads/master@{#665815}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/0f6dd926..8893ef1b Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I76826d6563eaa4aa5e56796e91bb973a6e6c053e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641441Reviewed-by:
-
Kenichi Ishibashi authored
Using CrossThreadWeakPersistent should be fine to hold a reference to an object that lives on the same thread, but there seems to be a mysterious behavior on CrossThreadWeakPersistent when we do that. To mitigate a risk of touching stale objects, use Member when we create WorkerResourceTimingNotifier for an inside fetch context. This is a speculative fix of crbug.com/959508. Bug: 959508 Change-Id: I28d398ece23973db67a20e9a8d864361c88c2b4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638304 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#665813}
-
Maksym Onufriienko authored
Convert sync-methods to compile under EG2: -numberOfSyncEntitiesWithType -injectBookmarkOnFakeSyncServerWithURL -triggerSyncCycleForType -injectTypedURLOnFakeSyncServer -deleteAutofillProfileOnFakeSyncServerWithGUID Bug: 922813 Change-Id: I0b74ecf5061915c9424721845be830128956aea6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628605 Commit-Queue: Maksym Onufriienko <monufriienko@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#665812}
-
Kent Tamura authored
Our serializer detected serialization type with |node.GetDocument() .IsHTMLDocument()|. Usually it stays with a single value during a single serializer call. However, <template>'s content can be owned by a document different from the <template>. We should store serialization type detected with the specified node. * Change SerializationType enum items: kAsOwnerDocument / kForceXML ==> kHTML / kXML * SerializeAsHTMLDocument() doesn't need an argument. Also, rename it to SerializeAsHTML() for simplicity. Bug: 968079 Change-Id: I4e7b20068eb4518a53d0fbf0341fd114498a3231 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640584Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#665811}
-
