- 16 Sep, 2020 40 commits
-
-
Glen Robertson authored
This is a reland of 93d899e2 OCL incorrectly added a dep on telemetry in official build. TBR=dpranke@google.com,blundell@chromium.org,dominickn@chromium.org,ericorth@chromium.org Original change's description: > Enable `gn check` on //chrome/browser. > > Changes are: > - adding deps when missing. > - adding "nogncheck" when needed (see below explanation). > - deleting nonexistent files from sources. > - new target :net_dns_access for files that depend on > //net/dns:host_resolver (which has restricted visibility). > Alternative: could open visibility to all of //chrome/browser instead > of adding a new target that has visibility. > - moving //c/b:test_support sources to //c/b/chromeos:test_support or > //c/test:test_support when they depended on headers there (cannot > add a dependency, there is a cycle). > - moving includes to conditional sections when they are used only in > conditional sections (where it caused deps issues). > - removing unused includes of test code from non-test code. > - merging sections in //c/b/BUILD.gn that had the same if() conditions. > Alternative: revert these changes, they are cosmetic. > - adding some asserts/conditional blocks in build files that only work > under those conditions. > > "gn check" does not understand #if statements in cc/h files so it > complains about missing deps in configurations where those deps were > never actually included. "nogncheck" has been added to the include lines > to suppress these spurious errors where necessary (sometimes it is not > necessary because the include is used outside of #if statements in other > files). > > Bug: 898837, 1125897 > Change-Id: I77e7dd3780fb93edb2b555a82b681a870990b496 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383400 > Reviewed-by: Dominick Ng <dominickn@chromium.org> > Reviewed-by: Eric Orth <ericorth@chromium.org> > Reviewed-by: Colin Blundell <blundell@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@google.com> > Commit-Queue: Glen Robertson <glenrob@chromium.org> > Cr-Commit-Position: refs/heads/master@{#807321} Bug: 898837 Bug: 1125897 Change-Id: If1dc6009b640c0b6ae33b1455b6ccf27c1cf274b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413427Reviewed-by:
Glen Robertson <glenrob@chromium.org> Commit-Queue: Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#807360}
-
Darwin Huang authored
This allows us to avoid an unnecessary and repetitive translation layer in ClipboardAndroid, between ClipboardFormatType and std::string. Bug: 1123230 Change-Id: Idd749fba9bbe13c9e5e13aa0f4ea6d93d7f74b39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383112Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#807359}
-
Alan Cutter authored
This CL adds two fields to the default web app config JSON: - load_and_await_service_worker_registration: bool - service_worker_install_url: URL string These allow default apps to control their service worker registration behaviour during the install flow. Bug: 1123435 Change-Id: Id389c347066a8dbcaa2c2350b884cdb5872e5721 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409057 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I18cab16dfca1199c8d6d6cdbb6ca351866a511a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413390Reviewed-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@{#807357}
-
Jarryd authored
There have been a number of reports about the storage pressure notification being shown, even when there is an absence of storage pressure. This is due to a numerical precision issue, where division of two ints would almost always return 0. This 0 meant that a condition that checked for storage pressure would always pass, and QuotaManger would fire storage pressure notifications for all write errors, regardless of disk availability. This change removes the division operation entirely with a little trick: - Given percent_available = 100 * available_space / total, - percent_available < kStoragePressureThresholdRatio is equivalent to (substitution): - 100 * available_space / total < kStoragePressureThresholdRatio is equivalent to (multiply both sides by total): - 100 * available_space < kStoragePressureThresholdRatio * total TBR=pwnall@chromium.org Bug: 1127237 Change-Id: I79c5ff47f27824d25ff8e47dc4aed859c8d3cd7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412758Reviewed-by:Jarryd Goodman <jarrydg@chromium.org> Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Cr-Commit-Position: refs/heads/master@{#807356}
-
Jimmy Gong authored
Bug: 1106937 Change-Id: I51abad3789200555295b284d5823bdccfbffb11f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413173Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org> Cr-Commit-Position: refs/heads/master@{#807355}
-
John Chen authored
All builds on MacOS are failing on perf waterfall due to Widevine signature errors. Adding a quick workaround with gn flag enable_widevine_cdm_host_verification=false, as suggested by the error message. TBR=wenbinzhang@google.com Bug: 1128811 Change-Id: Iffa58fe5ff0676e185b8cb381268d28482011172 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412934Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#807354}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/3e72b3ff8ca7..4108364efc3f 2020-09-16 mtklein@google.com _mm256_blendv_epi8 needs avx2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC scroggo@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md 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 Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: scroggo@google.com Change-Id: Ide1b54be351734e9c1d491030cab00e2ec9e431a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413389Reviewed-by:
-
Yoichi Osato authored
This reverts commit ad63f7bc. Reason for revert: Causes many CRASHes: https://ci.chromium.org/p/chromium/builders/ci/Linux%20CFI/18398#overview-tab Original change's description: > [XProto] Obtain Xcursor path from libXcursor > > Some distros (eg. Gentoo) use a non-default libXcursor path, so the > path (which was previously hardcoded) must now be obtained from > libXcursor. This patch uses dlopen()/dlsym() to get the path when > available. > > BUG=1127712 > R=sky > > Change-Id: Ib99dff0448c521c1a6cf8ad03bfe981572b9627c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410305 > Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> > Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Cr-Commit-Position: refs/heads/master@{#807158} TBR=sky@chromium.org,thomasanderson@chromium.org Change-Id: I0337fe6838a1bcbde6d71166650db1424a83c8db No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1127712 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413509Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#807352}
-
Ian Kilpatrick authored
Changes the NGPhysicalBoxFragment::RareData fields to all be named consistently, and removes an extra space allocation that isn't needed anymore. There should be no behaviour change. Change-Id: Ib2ff9544c40a63c400b5068f7a5c656e8475439d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412191 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#807351}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/a1f84f4a7300..d22b57cd6cee 2020-09-16 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ib6600e4bdc37dde6560bc6277d2a3bcc818b96d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413387Reviewed-by:
-
Moja Hsu authored
This CL adds whiteBalanceMode(continuous/manual) and colorTemperature MediaTrackCapabilities. Bug: b:148527288 Test: Test controls on krane and eve. Change-Id: I823b7644f5494883161c5bd9567918114c038012 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235145Reviewed-by:
Shik Chen <shik@chromium.org> Reviewed-by:
Wei Lee <wtlee@chromium.org> Commit-Queue: Hsu Wei-Cheng <mojahsu@chromium.org> Cr-Commit-Position: refs/heads/master@{#807349}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/40d3f47d189c..5b4eaf71f78b 2020-09-16 thestig@chromium.org mac arm64: Use the correct page size for this platform in PartitionAlloc 2020-09-15 thestig@chromium.org Download the selected version of hermetic Xcode via custom_vars. 2020-09-15 tsepez@chromium.org Rework pdf_fuzzer_init_public.cc 2020-09-14 thestig@chromium.org Remove unused RenderDeviceDriverIface methods. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1128457 Tbr: pdfium-deps-rolls@chromium.org Change-Id: I9450d2b37c49846415ecee7bf552a8daf0d09b41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412978Reviewed-by:
-
K. Moon authored
Implements DidReceiveData() to save data received from the blink::WebAssociatedURLLoader, and ReadResponseBody() to return the data to the caller. Based largely on whatever ppapi::proxy::URLLoaderResource::ReadResponseBody() does. Bug: 1099022 Change-Id: Ibaa7db0a7af5996e153d8dc106066ca6133ba95c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2407175Reviewed-by:
K. Moon <kmoon@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Daniel Hosseinian <dhoss@chromium.org> Commit-Queue: K. Moon <kmoon@chromium.org> Cr-Commit-Position: refs/heads/master@{#807347}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/1520b4d0fe34..4d3a0f602852 2020-09-16 jmadill@chromium.org GN: Componentize D3D format tables. 2020-09-16 jmadill@chromium.org Test Runner: Fix shard parameter script types. 2020-09-16 jmadill@chromium.org GN: Remove build/ dependency in "Null" GN file. 2020-09-15 jmadill@chromium.org Add feature for disabling compressed formats. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md 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-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: jmadill@google.com Change-Id: I8fa5d860f11ec8365d3d23c945d97b4ae9a08c31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413303Reviewed-by:
-
K. Moon authored
Implements a state machine to bridge the gap between chrome_pdf::UrlLoader's pull model and blink::WebAssociatedURLLoader's push model. This change only handles the basic state transitions; this is sufficient to simulate an empty response. A future change will deal with handling the data received by DidReceiveData(). Also fills in a basic blink::WebURLRequest, since BlinkUrlLoader calls WebAssociatedLoader::LoadAsynchronously() now. Note that RequestContext and RequestDestination must be set to pass certain security checks. Bug: 1099022 Change-Id: I20840e44adda63816f8c7d6a531ffe106dd8bfdf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411547 Commit-Queue: K. Moon <kmoon@chromium.org> Reviewed-by:
-
jongdeok.kim authored
In this CL, has_potential_filter_animation, has_potential_backdrop_filter_animation are considered while calculating node_or_ancestor_has_filters, affected_by_backdrop_filter to avoid rerasterization during the animation. Bug: 1115564 Change-Id: If58e1e71477758fc0c56e46f5dfd5ad6687cd43e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412028 Commit-Queue: jongdeok.kim <jongdeok.kim@navercorp.com> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#807344}
-
Yoichi Osato authored
This reverts commit f1458788. Reason for revert: Still flaky on mac: https://ci.chromium.org/p/chromium/builders/ci/Mac10.10%20Tests/58334 Original change's description: > [WebOTP] Fix flaky test SameSiteNavigationResetsDocumentUsedWebOTP > > Gives more time to propagate the WebOTP bit. > > Bug: 1120305 > Change-Id: Id350a03de42d3ea5895f01f47cdb5fff7ce801e5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405374 > Reviewed-by: Ken Buchanan <kenrb@chromium.org> > Commit-Queue: Yi Gu <yigu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#807065} TBR=kenrb@chromium.org,yigu@chromium.org Change-Id: I00eaf5dad7403127a62af0d8c6e67c580846df9d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1120305 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409466Reviewed-by:
-
Kyle Horimoto authored
This is in preparation for giving this class additional functionality unrelated to BLE. Bug: 1106937 Change-Id: Ib060a446580310df97651d0145e6f7e0d0784961 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412835 Auto-Submit: Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Reviewed-by:
James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#807342}
-
Hiroshige Hayashizaki authored
#1. Remove importScripts() special handling WorkerOrWorkletScriptController has a special logic for exceptions in importScripts(), which plumbs ErrorEvent outside V8 (i.e. via error_event_from_imported_script_) while rethrowing exceptions in V8, in order to transmit the original exception location information, eventually to WorkerGlobalScope's error event. In order to merge WorkerOrWorkletScriptController logic with its counterpart in ScriptController, this CL removes this importScripts() special logic and makes the logic look more spec conformant. This CL: - Uses v8::TryCatch::ReThrow() instead of ExceptionState::RethrowV8Exception(), because ReThrow() seems to preserve the original exception location while RethrowV8Exception() doesn't seem so. - Uses `v8::TryCatch::SetVerbose(true)` to #report-the-error, instead of `DispatchErrorEvent()`. After this CL, WorkerGlobalScope's error event is triggered from inside V8, and the original exception location is plumbed through V8. By doing so, the original exception location is passed using V8's error rethrowing mechanism, and thus the followings are removed: - ExecutionState - RethrowExceptionFromImportedScript This CL makes exceptions around cross-origin importScripts() spec conformant: - Previously cross-origin importScripts() throws `null` when there are parse errors or evaluation errors, and muted errors ("Script error.") is reported to WorkerGlobalScope error event handler. After this CL, it throws and reports to error event handler NetworkError DOMException as spec'ed. (crbug.com/1111750) - This CL also fixes exceptions around same- and cross-origin importScripts() from setTimeout(). As a result of switching to `v8::TryCatch::SetVerbose(true)`, the following things are achieved: #2. Fire WorkerGlobalScope error events before a microtask checkpoint Before this CL: 1. Script evaluation (top-level worker script or setTimeout(string)) 2. Microtasks checkpoint in V8ScriptRunner::RunCompiledScript() 3. WorkerGlobalScope error events in EvaluateAndReturnValue() After this CL: 1. Script evaluation (top-level worker script or setTimeout(string)) 3. WorkerGlobalScope error events in v8::Script::Run() 2. Microtasks checkpoint in V8ScriptRunner::RunCompiledScript() observable changes are: crbug/1114028 and crbug/1120293 are fixed. #3. Fix error's `message` value. This CL fixes the `message` field values of `Error` objects reported to WorkerGlobalScope error events, because the code path for `v8::TryCatch::SetVerbose(true)` handles such cases appropriately while `DispatchErrorEvent()` doesn't. For background and previous attempts, see crbug/590219 and https://codereview.chromium.org/2090953006/#msg42. #4. Use `v8::TryCatch::SetVerbose(true)` for all classic script evaluation This makes easier to unify script evaluation code paths (crbug.com/1111134). An alternative considered was to switch all classic script evaluation to `V8ScriptRunner::ReportException()`, but it would be much harder: - We'll need to fix `V8ScriptRunner::ReportException()` and its underlying V8 code to handle cases like #3 appropriately. _ We'll need more subtle behavior/ordering changes, affecting broader range of script evaluation (i.e. not limited to workers). Bug: 1111134, 1111750, 1114028, 1120293, 590219 Change-Id: I9395088a73ed76e241e89ce7d15e95417ca829d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2328394 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:Dominic Farolino <dom@chromium.org> Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#807341}
-
John Chen authored
Disable failing story system_health.memory_mobile/load:tools:dropbox:2019 on Nexus 5X. TBR=wenbinzhang@google.com NOTRY=true Bug: 1128019 Change-Id: I6ab6b976b57d644d56db92423b2881a4d27fae1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412980Reviewed-by:
-
Glen Robertson authored
This reverts commit 93d899e2. Reason for revert: Breaks on official build due to inclusion of //chromeos/components/telemetry* Original change's description: > Enable `gn check` on //chrome/browser. > > Changes are: > - adding deps when missing. > - adding "nogncheck" when needed (see below explanation). > - deleting nonexistent files from sources. > - new target :net_dns_access for files that depend on > //net/dns:host_resolver (which has restricted visibility). > Alternative: could open visibility to all of //chrome/browser instead > of adding a new target that has visibility. > - moving //c/b:test_support sources to //c/b/chromeos:test_support or > //c/test:test_support when they depended on headers there (cannot > add a dependency, there is a cycle). > - moving includes to conditional sections when they are used only in > conditional sections (where it caused deps issues). > - removing unused includes of test code from non-test code. > - merging sections in //c/b/BUILD.gn that had the same if() conditions. > Alternative: revert these changes, they are cosmetic. > - adding some asserts/conditional blocks in build files that only work > under those conditions. > > "gn check" does not understand #if statements in cc/h files so it > complains about missing deps in configurations where those deps were > never actually included. "nogncheck" has been added to the include lines > to suppress these spurious errors where necessary (sometimes it is not > necessary because the include is used outside of #if statements in other > files). > > Bug: 898837, 1125897 > Change-Id: I77e7dd3780fb93edb2b555a82b681a870990b496 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383400 > Reviewed-by: Dominick Ng <dominickn@chromium.org> > Reviewed-by: Eric Orth <ericorth@chromium.org> > Reviewed-by: Colin Blundell <blundell@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@google.com> > Commit-Queue: Glen Robertson <glenrob@chromium.org> > Cr-Commit-Position: refs/heads/master@{#807321} TBR=dpranke@google.com,blundell@chromium.org,dominickn@chromium.org,ericorth@chromium.org,glenrob@chromium.org Change-Id: I13f4705899734213dd3f82fe60ac431f85584e70 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 898837 Bug: 1125897 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413370Reviewed-by:
-
Youkichi Hosoi authored
We will use UUIDs for the paths of shared external storage volumes (MyFiles, removable devices) in ARC. BUG=b:123377807 BUG=b:123641356 BUG=b:163951541 TEST=$ unit_tests --gtest_filter="FileManagerPathUtilConvertUrlTest.*" TEST=$ unit_tests \ TEST= --gtest_filter="NoteTakingHelperTest.LaunchAndroidAppWithPath" TEST=Open image files in MyFiles / removable devices with the Android TEST=Google Photos app from the Chrome OS Files app. Change-Id: Id2166c3a793bf0eae25fbd5e07c5d1ec6b892067 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275514 Commit-Queue: Youkichi Hosoi <youkichihosoi@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#807338}
-
Glen Robertson authored
Origin Trial on Android only for now. Bug: 1032423,1096428 Change-Id: I8329c798138d800156bbe3f90de6d05f2d9662b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404284Reviewed-by:
Kentaro Hara <haraken@chromium.org> Auto-Submit: Glen Robertson <glenrob@chromium.org> Commit-Queue: Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#807337}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/52fdd1ffcefb..8e500174f4bb 2020-09-16 chanli@chromium.org [depot_tools] Roll led to latest If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC apolito@google.com,ehmaldonado@google.com,sokcevic@google.com,ajp@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1099018 Tbr: apolito@google.com,ehmaldonado@google.com,sokcevic@google.com,ajp@google.com Change-Id: If1d95c2bf1b50ee7d3c87e271e645db5546c88b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413300Reviewed-by:
-
Liquan (Max) Gu authored
Context: According to payment_request.idl, PaymentOptions and PaymentDetailsInit are {} when missing, and so both impossible to be null in non-compromised renderer. When renderer delivers PaymentOptions to browser, it doesn't create null for an empty PaymentOptions, so Java should expect options and details to be non-null, reject the null cases from a compromised renderer, and assert PaymentOptions in rest of the code to be not null. Before this patch, the Java payment codebase does not treat null as invalid for PaymentOptions, in many places spending extra effort in considering this case. This CL changes the payment code to achieve what it should be as stated above. Change: * Assert option not to be null in PaymentOptionsUtils.requestShipping(), inline the method, and do the same for requestPayerName(), requestPayerPhone(), requestPayerEmail(), getShippingType() * CPRImpl adds invalid renderer data check for getShippingType. * Correct the @Nullable annotation of PaymentDetails and PaymentOptions in java payment code. Bug: 1106563 Change-Id: I096cf67543bcba59e9555d157a093e99a47e2866 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404566 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#807335}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-aemu-chromium-autoroll Please CC chonggu@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: chonggu@google.com Change-Id: If5390bfa5184e5a83af221a6f4dfd6602b845dda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413302Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d9c55ce8edbb..3e72b3ff8ca7 2020-09-16 mtklein@google.com jit q14x2 ops If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC scroggo@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md 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 Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: scroggo@google.com Change-Id: Ib121a3b4ed3033ca56632548edccf3bb78f44ba0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413294Reviewed-by:
-
Seokho Song authored
Currently, PaintPropertyTreeBuilder makes an issue about z-order with 3D transform operations such as trasnalteZ(). So we need to check this issue on the tests whether wrong results or not. In this patch, a test will check if rendered correctly. Now it would be expected '[Failure]' It will remove the expectation when we fix the issue Bug: 1116358 Change-Id: I8f5be9e1ed186df1e779cf9e8a7f0462e079232b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409476 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/e4642dac6c25..b10d4a612b87 2020-09-16 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 235f7418..dfb9023b (807145:807259) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I9ea7ad06d2bc6d1c154d7422513a07bc7a28f541 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413295Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/60b89e50eba2..d1be45d6b6ab If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC yoichio@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: yoichio@google.com Change-Id: Id530ec4c9fa15ac97373c0a86de96c8107505ba3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413296Reviewed-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@{#807330}
-
tby authored
Add the skeleton for a new Drive zero-state provider, to eventually replace the existing DriveQuickAccessProvider once it's finished. Currently this does nothing and is unused, but will be expanded in follow-up CLs. The skeleton includes some bits of logic we'll need copied over from the DriveQuickAccessProvider, including a check for the suggested files flag and two weak pointer factories. Bug: 1034842 Change-Id: Idc0883bcf5456cb2e0c1df2e838d6991eb43e458 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410142 Commit-Queue: Tony Yeoman <tby@chromium.org> Reviewed-by:
Rachel Wong <wrong@chromium.org> Cr-Commit-Position: refs/heads/master@{#807329}
-
Kent Tamura authored
This directory has no errors now. This CL has no behavior changes. Bug: 800764 Change-Id: I84ec665b1e48e416ace523ac88b788cc1900b4d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412114 Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#807328}
-
Darren Shen authored
Add a new method to determine whether a feature flag is enabled or not. Unfortunately, Chrome doesn't allow us to query feature flags by raw name, only by base::Feature values. Hence, the API must use an enum instead to represent the feature, and the implementation needs to map the enum to a base::Feature value. Add a feature to the enum as an example. Bug: 1019541 Change-Id: I7e6274b70e7ba13c9bcc9dd0ee1fe3117614d06b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2397304 Commit-Queue: Darren Shen <shend@chromium.org> Commit-Queue: Leo Zhang <googleo@chromium.org> Reviewed-by:
Leo Zhang <googleo@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#807327}
-
Lingqi Chi authored
ExecutionContent-scoped BIB Migrated PeriodicBackgroundSyncService interface; let it be obtained via an ExecutionContent-scoped BrowserInterfaceBroker instead of a Process-wide one. Then it can be controllable when prerendering a page. Bug: 1126758 Change-Id: I8749d3bc6874ba5c04eb984642f9f1734dc8048f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412055 Commit-Queue: Lingqi Chi <lingqi@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#807326}
-
Avi Drissman authored
The stack sampler is broken for now on Arm Macs, so disable a failing v8_unwinder unit test too. Bug: 1102197, 1128464 Change-Id: Ie0091eb8efc7a96d4f917ed394585e1b6595c7d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413023Reviewed-by:
Mark Mentovai <mark@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#807325}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/0063ad80f210..511a82c95fc7 2020-09-16 heiserya@google.com Improve debugability of WPR when running record_wpr or run_benchmark. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC zhanliang@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-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: None Tbr: zhanliang@google.com Change-Id: I69e0d50f311d7db35fe417731d46b6c6f04b647c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412766Reviewed-by:
-
Minoru Chikamune authored
Send message through AgentSchedulingGroup instead of RenderProcessHost. Bug: 1111231 Change-Id: I24bc55d05a18da9e3f1d7eef64f593cb2b7c0e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409394Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Tal Pressman <talp@chromium.org> Commit-Queue: Minoru Chikamune <chikamune@chromium.org> Cr-Commit-Position: refs/heads/master@{#807323}
-
Risan authored
Adapted from youkichi@'s prototype: https://chromium-review.googlesource.com/c/chromium/src/+/2275514/14 The change is simpler now after we split removable watchers to per media watcher. BUG=b:163951541 TEST=The images are indexed with UUID in Photos. Change-Id: I42873445e9fb71947d029140fa9bcc4b512e8995 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409724Reviewed-by:
Satoshi Niwa <niwa@chromium.org> Commit-Queue: Risan <risan@chromium.org> Cr-Commit-Position: refs/heads/master@{#807322}
-
Glen Robertson authored
Changes are: - adding deps when missing. - adding "nogncheck" when needed (see below explanation). - deleting nonexistent files from sources. - new target :net_dns_access for files that depend on //net/dns:host_resolver (which has restricted visibility). Alternative: could open visibility to all of //chrome/browser instead of adding a new target that has visibility. - moving //c/b:test_support sources to //c/b/chromeos:test_support or //c/test:test_support when they depended on headers there (cannot add a dependency, there is a cycle). - moving includes to conditional sections when they are used only in conditional sections (where it caused deps issues). - removing unused includes of test code from non-test code. - merging sections in //c/b/BUILD.gn that had the same if() conditions. Alternative: revert these changes, they are cosmetic. - adding some asserts/conditional blocks in build files that only work under those conditions. "gn check" does not understand #if statements in cc/h files so it complains about missing deps in configurations where those deps were never actually included. "nogncheck" has been added to the include lines to suppress these spurious errors where necessary (sometimes it is not necessary because the include is used outside of #if statements in other files). Bug: 898837, 1125897 Change-Id: I77e7dd3780fb93edb2b555a82b681a870990b496 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383400Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Eric Orth <ericorth@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@google.com> Commit-Queue: Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#807321}
-
