- 26 Mar, 2019 40 commits
-
-
Erik Luo authored
Before, Console logs with an associated Network request would link all links to the request's URL. Now, it uses normal linkifier, for links with a different URL, allowing external ones. Bug: 925508 Change-Id: I96e7aaf75ad1597852a8dd5e1b2a5363df3ff844 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540060Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Commit-Queue: Erik Luo <luoe@chromium.org> Cr-Commit-Position: refs/heads/master@{#644506}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/5ccc6eaadf1a..c8e39ebcf304 git log 5ccc6eaadf1a..c8e39ebcf304 --date=short --no-merges --format='%ad %ae %s' 2019-03-26 jclinton@chromium.org config: Wipe build roots for non-paladin asan, ubsan, and fuzzer Created with: gclient setdep -r src/third_party/chromite@c8e39ebcf304 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: Id6e0164a9e3adfb5f8835589668b85f23ed7df12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540046Reviewed-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@{#644505}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/b66b4e0b328b..cadd2cc7ad7f git log b66b4e0b328b..cadd2cc7ad7f --date=short --no-merges --format='%ad %ae %s' 2019-03-26 fmayer@google.com Merge "Do not fail if ClientConfiguration cannot be read in one chunk." Created with: gclient setdep -r src/third_party/perfetto@cadd2cc7ad7f The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com Change-Id: I0f40b9ea1aac676f7112f4f9ddb1896e48129b2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540039Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/88a0c6d6..e9845b09 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;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I9add0921fda99337c6a3ba84521be82df9317242 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538824Reviewed-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@{#644503}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/213a8ce6d5c2..cc6473f7d80d git log 213a8ce6d5c2..cc6473f7d80d --date=short --no-merges --format='%ad %ae %s' 2019-03-26 capn@google.com Regenerate Windows LLVM configs 2019-03-26 capn@google.com Regenerate Linux LLVM configs 2019-03-26 capn@google.com Add Windows support to LLVM config generation script 2019-03-26 capn@google.com Disable LLVM_ENABLE_THREADS in config generation script Created with: gclient setdep -r src/third_party/swiftshader@cc6473f7d80d The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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 TBR=swiftshader-team+autoroll@chromium.org Change-Id: I82d8e4db58f511f2b9dd6d44639ccb682724524b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540044Reviewed-by:
-
Elly Fong-Jones authored
This change removes the flag and the backing switch. Bug: None Change-Id: I169ca0f1460544e29771b148455d258c971acc9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540095 Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#644501}
-
Dave Tapuska authored
Determine if we are in a sandbox iframe preventing top level navigation. Add a histogram to count the number of navigations starting from such frames that stay within the subtree or affect frames outside of it, to determine if it is feasible to adjust the policy here. BUG=705583 Change-Id: Ie9c808035af367e868b1a422b549aa4a618654a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1524624 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#644500}
-
Robert Ogden authored
Some concerns came up during privacy review about how 'cloud technology' might be translated too literally so this improves the description. Bug: 929532 Change-Id: I82b424d90436e6ae94928f78c56cf0247d3c3a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540075Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#644499}
-
Elly Fong-Jones authored
This change just removes the flag; the backing switch remains (with an added TODO pointing at the cleanup bug). Bug: 945966 Change-Id: I7e6231fe1eb65cbadc580bb5a6538d49e42069c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540296 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Alexander Alekseev <alemate@chromium.org> Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#644498}
-
Tatiana Buldina authored
Bug: chromedriver:2414 Change-Id: I8a30cc59f1282d909da8ef03d5f34a0bbbefed38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531102Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Tatiana Buldina <buldina@chromium.org> Cr-Commit-Position: refs/heads/master@{#644497}
-
Daniel Cheng authored
Also add an OWNERS file for //third_party/smhasher. Next steps are to: - remove dependencies on the old header locations - add //base/hash/README.md - remove direct dependencies on smhasher and provide standard (but gated) interfaces in //base/hash. Bug: 902789 Change-Id: I36bab11b1e3383dc41814867e053e7ea3e0af5ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535124 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Adenilson Cavalcanti <cavalcantii@chromium.org> Cr-Commit-Position: refs/heads/master@{#644496}
-
rajendrant authored
To start with the feature is enabled by default on Android. Bug: 945036 Change-Id: I9383194f5e10c0bc05834a2e5d3fc50934c22794 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536681 Commit-Queue: rajendrant <rajendrant@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#644495}
-
David Tseng authored
TBR=sky@chromium.org Bug: 795840 Change-Id: Idc11aa884c29cd73960355e660ce2219aa674621 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534283Reviewed-by:
David Tseng <dtseng@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#644494}
-
Jonathan Backer authored
This CL makes Android WebView use this mode explicitly whenever SkiaRenderer is asked for. This will allow some further clean of SkiaOutputSurfaceImpl* in follow up CLs. Change-Id: Ibcba761477bbe89829ae647ffd22ff7a80d4247b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1539779 Commit-Queue: Jonathan Backer <backer@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#644493}
-
Gary Kacmarcik authored
When the default display is not leftmost, then the coordinates for the mouse events are not calculated correctly. This fixes that. Bug: 946001 Change-Id: I1d0124c2c5bbb828466ee306e60bb0aedaa2f5d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536769 Commit-Queue: Gary Kacmarcik <garykac@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#644492}
-
Siye Liu authored
The root cause of this issue is that there is a wrong assumption in current TSF implementations for JPN IMEs. IMEs may start new composition at offset prior to current composition. We should not commit current composition if the start of new composition is before current composition. This change also fix an issue in Confirm/cancel composition scenario. We should notify text change for the whole buffer to let IME to terminate composition. Bug: 944004 Change-Id: Iff8759481bfcb2da622483dabecfb6cc4c50da7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536637 Commit-Queue: Siye Liu <siliu@microsoft.com> Reviewed-by:
Yohei Yukawa <yukawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#644491}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7175abb56021..c0b7cfc0b483 Created with: gclient setdep -r src-internal@c0b7cfc0b483 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:891734 TBR=sahel@chromium.org,horo@chromium.org,pkasting@chromium.org,andruud@chromium.org Change-Id: I291b9c7a987803a113abc8bf0bde0b2ad6f17642 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540045Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Sahel Sharify <sahel@chromium.org> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#644490}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/17d55b5dc9ce..069b546ca7bf git log 17d55b5dc9ce..069b546ca7bf --date=short --no-merges --format='%ad %ae %s' 2019-03-26 tsepez@chromium.org Avoid signed integer overflow in CFGAS_StringFormatter::ParseNum. Created with: gclient setdep -r src/third_party/pdfium@069b546ca7bf 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:945836 TBR=dsinclair@chromium.org Change-Id: Ic58c62a296ad2e1b3490cb8faa7ec5f654a861f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540043Reviewed-by:
-
Paul Meyer authored
This makes it more clear that this policy applies only to lossy image types (for now, just JPEG). This patch also makes the implementation more generic in order to make the policy compatible with parsed policy values and to pave the way for implementing a lossless-enforcing version of the unoptimized-images policy as well. These changes have been pulled from a larger partially reviewed CL: https://chromium-review.googlesource.com/c/chromium/src/+/1524869 Bug: 942659 Change-Id: I0242ac900b1653b89d6d8dbd63616003dcaaba62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531354 Commit-Queue: Paul Meyer <paulmeyer@chromium.org> Reviewed-by:
Paul Meyer <paulmeyer@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#644488}
-
Sahel Sharify authored
TBR: pkasting@chromium.org,twellington@chromium.org Bug: 945861 Change-Id: I4cff86cbcaf417a0a3025cb9a61c60fe3aaa461a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540074Reviewed-by:
-
Peter Boström authored
This dialog looks and quacks like a menu, similar to the profile chooser dialog. As a bonus the OK/Cancel buttons are also removed from this dialog, which gets shoehorned in to make this look more like a menu. Bug: chromium:943702 Change-Id: Idf1d617238d9e92f7e8ef5645d2e4938b11ff8ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540065Reviewed-by:
Taylor Bergquist <tbergquist@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#644486}
-
Maks Orlovich authored
Change-Id: Ic5d27813b7388666a4f7a53fe4f641fde125d2cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1524998Reviewed-by:
Mohammad Refaat <mrefaat@chromium.org> Reviewed-by:
Bence Béky <bnc@chromium.org> Commit-Queue: Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#644485}
-
Elly Fong-Jones authored
Bug: None Change-Id: I4bff537460b3e34a95631691d708af959f90d6d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540091 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Azeem Arshad <azeemarshad@chromium.org> Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Azeem Arshad <azeemarshad@chromium.org> Cr-Commit-Position: refs/heads/master@{#644484}
-
Ushesh Desai authored
Removing out of date info in the change and will add the email lists once we figure out which ones to use. R=benhenry@chromium.org Bug: 909866 Change-Id: I06c559e430716b41af94859f1135e2fff10201e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540087Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Reviewed-by:
Annie Sullivan <sullivan@chromium.org> Commit-Queue: Ushesh Desai <ushesh@chromium.org> Cr-Commit-Position: refs/heads/master@{#644483}
-
Alex Cooper authored
Windows was not allowing copying of the temp file while it was still open. However, calling close by default causes the file to get deleted automaticaly. This defers that deletion. Change-Id: I8ce712a4eb3de9d4d14f43389d341b016a64bae1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1539871Reviewed-by:
Klaus Weidner <klausw@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#644482}
-
David Tseng authored
ChromeVox used a tree path based recovery strategy to work around issues on google.com (see crbug.com/885244). https://chromium-review.googlesource.com/c/chromium/src/+/1534283 As of https://chromium-review.googlesource.com/c/chromium/src/+/1889165 the above issue seems to have been resolved without using tree path based recovery. Revert ChromeVox back to using ordinary ancestry recovery. Bug: 945708 Change-Id: I6b8599d2daf42bc1bad036b911fa77d802e66451 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1539262Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#644481}
-
Brandon Wylie authored
Opens the last tab when clicked. Uses the BrowsingHistoryBridge to query the history for the last browsed to URL. first launch/history clear: https://screenshot.googleplex.com/k0WpTH5e0Vt.png after click: https://screenshot.googleplex.com/VrtPDrcQs9Y.png Bug: 936052 Change-Id: Ia1c138d0a88d90ebe92589cc37e5e09ca7a6ade1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1520884 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#644480}
-
Sean Gilhuly authored
SkiaRenderer is ignoring the flag |force_anti_aliasing_off_| in RenderPassDrawQuad and SolidColorDrawQuad. Check for this flag and turn off AA if it is present. The pixel tests also expect alpha blending to be disabled if this flag is present, so use blend mode kSrc instead of kSrcOver. This fixes the tests RenderPassDrawQuadForceAntiAliasingOff and SolidColorDrawQuadForceAntiAliasingOff for SkiaRenderer, so enable them. Also enable TileDrawQuadForceAntiAliasingOff and SolidColorDrawQuad, which are passing after other changes. Bug: 939442 Change-Id: Ifd4092bbeb9925f0db3a1b25a51785755e06b272 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1529296Reviewed-by:
weiliangc <weiliangc@chromium.org> Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Cr-Commit-Position: refs/heads/master@{#644479}
-
Xianzhu Wang authored
Previously we created validation message overlay page during main page lifecycle update, and Microtask::PerformCheckpoint() called when the overlay page FinishedParsing would execute some micro task of the main page in wronglifecycle state. Now create validation message overlay page when the overlay is created. Bug: 945451 Change-Id: I618cd7ffe8c59cfee0b45452dc8dd9c0ee2e2fd8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536992 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
-
Tommy C. Li authored
Previously, we skipped the match classification process if user_input_in_progress_ was false and we were not in Query in Omnibox mode. Actually, we can always skip the classification process if user_input_in_progress_ is false. This CL implements that slight optimization. Bug: NONE Change-Id: Iabde52481e199b60874434f034733f7275af8f92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534282Reviewed-by:
Kevin Bailey <krb@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#644477}
-
Weiliang Chen authored
RenderPass's opacity need to be applied as last step. This is for refection filter case where we expect the opacity to be applied to the combination of original and reflected content. This is done by applying the opacity as a color filter. Bug: 908951 Test: layout tests compositing/reflections/reflection-opacity.html Change-Id: I84226726b6cae0e294d6409d3e8e93f38648c867 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534140Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: weiliangc <weiliangc@chromium.org> Cr-Commit-Position: refs/heads/master@{#644476}
-
Dana Fried authored
Most thumbnail-related tasks are now CONTINUE_ON_SHUTDOWN to avoid the case where, for example, a JPEG compression that we don't care about could briefly hold up browser exit. Bug: 928954 Change-Id: Ice6a100765be46dd555c38f0d2ce2043e85da340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1537649Reviewed-by:
Robert Liao <robliao@chromium.org> Commit-Queue: Dana Fried <dfried@chromium.org> Cr-Commit-Position: refs/heads/master@{#644475}
-
Christopher Cameron authored
When traversing down the AXTree, we expose the tree - views::View - content::RenderWidgetHostViewCocoa This tree is set up in the (strangely idiosyncratic) function WebView::GetNativeViewAccessible, which directly adds the result of RenderWidgetHostView::GetNativeViewAccessible as the accessibility element for views::WebView. When traversing up the AXTree, we expose a different tree - views::View - content::WebContentsViewCocoa - content::RenderWidgetHostViewCocoa This is from RenderWidgetHostViewCocoa having the default parent value (its superview) and WebContentsViewCocoa returning the parent specified by NativeViewHostMac::GetAccessibilityElement. Make this consistent by removing WebContentsViewCocoa from the tree, and moving all AXTree stitching code and tests over to RenderWidgetHostViewCocoa. While in the neighborhood, move SetParentUiLayer from RenderWidgetHostViewBase to RenderWidgetHostViewMac. Bug: 921109 (sort-of) Change-Id: Iac4edd109f341f50d7327d3a5500d22594685ce3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538598Reviewed-by:Avi Drissman <avi@chromium.org> Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#644474}
-
Sahel Sharify authored
Mark external/wpt/content-security-policy/frame-ancestors/frame-ancestors-nested-cross-in-same-star-allow.html as timeout on mac10.13 TBR=pkasting@chromium.org Bug: 945774 Change-Id: I27fdc5ea15dd225b531b412a0cb73e689939a7a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540088Reviewed-by:
-
Paul Meyer authored
This removes the need for ReportingServiceProxyPtrHolder altogether, which is removed. This is part of a larger effort to refactor the reporting code in Blink. Bug: 931863 Change-Id: I1668ca1b6761ef2fd485bb06fe3743f29fde362b TBR: foolip@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534573 Commit-Queue: Paul Meyer <paulmeyer@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#644472}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e4ad58a4e2c1..b23aee3431c0 git log e4ad58a4e2c1..b23aee3431c0 --date=short --no-merges --format='%ad %ae %s' 2019-03-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-03-26 robertphillips@google.com Revert "Fix bug in GrResourceAllocator's intermediate flushing" 2019-03-26 robertphillips@google.com Fix bug in GrResourceAllocator's intermediate flushing 2019-03-26 brianosman@google.com Convert GrPorterDuff test from NullGL to Mock context 2019-03-26 brianosman@google.com Run GrTextureMipMapInvalidationTest on rendering contexts 2019-03-26 brianosman@google.com Convert some unit tests from NullGL to Mock context 2019-03-26 rmistry@google.com Detect and fail when invalid SKPs are created by RecreateSKPs bot 2019-03-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-03-26 rmistry@google.com Fix RecreateSKPs bot page sets Created with: gclient setdep -r src/third_party/skia@b23aee3431c0 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 BUG=chromium:942538,chromium:942538 TBR=stani@chromium.org Change-Id: I42e6e9fa8627b8fb8335b9dcd6063dae3d4cc3e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540041Reviewed-by:
-
Mike Dougherty authored
Bug: 861752 Change-Id: Ie6cb88165e5aa4131ab6c387ff81017cca67eec4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1539872 Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Auto-Submit: Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#644470}
-
Junbo Ke authored
Bug: b/120907590 Test: Manual Change-Id: I922288b91c476d8107fa4188a42e551da4716f33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531465 Commit-Queue: Junbo Ke <juke@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#644469}
-
Sajad Maysam authored
Will be used to implement a scrollview that does not extend beyond the boundaries of a widget with rounded corners. Necessary because scrollviews paint on a layer so they will paint over the parent view's bounds. Also similar code creating rounded backgrounds happens in a bunch of places in the codebase and could be simplified to use a single common background factory method (example: bubble background code). Change-Id: Ie885ca9f71f2722680e6fb709fe3091e71ad88fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1524910 Commit-Queue: Sajad Maysam <sajadm@google.com> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#644468}
-
Mike Jackson authored
When a page makes a 'POST' XHR request, and then sends a typed array as binary data, there is no request content type. If the user, then exports the contents of the network tool to a HAR file, the postData section is missing the mimeType field. HttpWatch requires the MimeType field, otherwise it treats the file as if its incorrectly formatted. The fix is to ensure we always generate the mimeType field for the postData section. Change-Id: Id110887fac50057ccab7a257a8de770a9d92b03c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535348 Commit-Queue: Mike Jackson <mjackson@microsoft.com> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#644467}
-
