- 19 Jun, 2018 40 commits
-
-
Francois Doray authored
Previously, "zero" was used as the last active time for tabs open in the background, which made them immediately eligible for proactive freeze and discard. With this CL, their creation time is used as the last active time, which will prevent them from being proactively frozen or discarded for at least 10 minutes after creation (note: except when the number of tabs is considered excessive, see tab_manager_features.cc). Bug: 854272 Change-Id: I5398b24fadbd073bd224e2a9e98c8ae610b26e92 Reviewed-on: https://chromium-review.googlesource.com/1106612Reviewed-by:
Sébastien Marchand <sebmarchand@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#568574}
-
Thomas Tangl authored
Change-Id: I3df8e8dce2c62f623db78e7278390802f363aa5d Reviewed-on: https://chromium-review.googlesource.com/1106381Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Thomas Tangl <tangltom@chromium.org> Cr-Commit-Position: refs/heads/master@{#568573}
-
Krzysztof Olczyk authored
The content::ScopedWebCallbacks class is a helper for blink::WebCallbacks and does not do anything strictly related to //content. Moving it to //third_party/blink/public/platform makes it possible to use it in all blink platform consumer, also the ones outside of //content, such as //media/blink. One example is //media/blink/webmediacapabilitiesclient_impl.cc which before had to use specialized local copy of it. This also adds two modifications to ScopedWebCallbacks: * Make make_scoped_web_callbacks take a unique_ptr to WebCallbacks, instead of raw pointer that gets silently WrapUnique'ed inside, to make ownership passing more explicit, * Modernize it to operate on OnceCallback, instead of Callback, * Use default move constructor and move assignment. Bug: 847211 Change-Id: I3d9b8a660dbfd66cf8721331777f36ea42c04bc8 Reviewed-on: https://chromium-review.googlesource.com/1104356 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#568572}
-
Yafei Duan authored
This doesn't decode the JSON, just grabs it from the appropriate endpoint. The CL was originally uploaded by dewittj@. This CL is fixing the test failure and re-uploading to land since dewittj@ is out of office. Bug: 852075 Change-Id: Ib8adc7cad661665c884a2d058c27c99f40ac0a58 Reviewed-on: https://chromium-review.googlesource.com/1105018 Commit-Queue: Yafei Duan <romax@chromium.org> Reviewed-by:
Cathy Li <chili@chromium.org> Cr-Commit-Position: refs/heads/master@{#568571}
-
Robbie McElrath authored
RegisterIOHandler calls CreateIoCompletionPort and will currently fail silently. This adds a return code and propagates it up. Bug: 845612 Change-Id: Ie0685cb7fb6d21a5e23489337158ee0ba0b75154 Reviewed-on: https://chromium-review.googlesource.com/1101644 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#568570}
-
Paul Miller authored
Chrome turns on the studies specified in fieldtrial_testing_config.json for testing purposes. It doesn't respect the difference between android and android_webview platforms, so WebView gets all of Android Chrome's studies enabled, including UseSurfaceLayerForVideo which breaks WebView. As a workaround, disable the test config. BUG=853832 Change-Id: Ib8453ac163c7ce71419d25fc5433d3b31b89e894 Reviewed-on: https://chromium-review.googlesource.com/1105608Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#568569}
-
Kyle Horimoto authored
Initialization of the service is asynchronous due to the need to fetch the Bluetooth adapter asynchronously. This class allows clients to make requests of the service before it is fully initializes; queued requests are then passed on to the rest of the service once initialization completes. Bug: 824568, 752273 Change-Id: I79b5940070b7c3ff6e0a9ed3f7ef4dff8f260038 Reviewed-on: https://chromium-review.googlesource.com/1105616Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#568568}
-
jonross authored
Currently all viz and surface sync tests on the Mojo Android FYI bot are hitting shard timeouts. This updates the tests to use filter lists, to remove tests that were causing the shards to timeout. This also remove viz_content_unittests as I'm currently seeing infra failures from it. It will require local debugging. TEST=surface_sync_content_browsertest, viz_content_browsertests Bug: 849746 Change-Id: I237aab39e1c4a016584940fa0362a39db4be3434 Reviewed-on: https://chromium-review.googlesource.com/1102699Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#568567}
-
Nate Fischer authored
No change to logic. This creates an AndroidManifest.xml file with only a minSdkVersion, which we use to configure lint to correctly verify the boundary interfaces compile down to the support library's minSdkVersion. This code will continue to only be called on >= 21 (Lollipop). R=torne@chromium.org Bug: 828184 Test: code compiles and passes lint Test: code doesn't compile with @TargetApi annotations in BoundaryInterfaceReflectionUtil Change-Id: I270f0f5732c1134ba77b912ece31cf188ee6cb5f Reviewed-on: https://chromium-review.googlesource.com/1105697Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#568566}
-
Nate Fischer authored
No change to production logic. This adds a test for shouldInterceptRequest with server-side redirects because this was previously untested. R=boliu@chromium.org Bug: 768631 Test: run_webview_instrumentation_test_apk -f AwContentsClientShouldInterceptRequestTest#testNotCalledForHttpRedirect Change-Id: I3eccada1e249269a4f66395a8d10a107001e1231 Reviewed-on: https://chromium-review.googlesource.com/1105630Reviewed-by:
-
David Valleau authored
Change-Id: Ie400a16a7d6c91850245dfe1ada290d03697a7cd Reviewed-on: https://chromium-review.googlesource.com/1106640Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: David Valleau <valleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#568564}
-
Bailey Forrest authored
Bug: None Test: Doesn't show up in git status Change-Id: Ia74bba8d5c1c4df6b626784abe65d275eff8ec79 Reviewed-on: https://chromium-review.googlesource.com/1106699Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Commit-Queue: Bailey Forrest <bcf@chromium.org> Cr-Commit-Position: refs/heads/master@{#568563}
-
Stuart Langley authored
Steps I followed: autoninja -C out/Default chrome tools/clang/scripts/generate_compdb.py -p out/Default > compile_commands.json cd out/Default /usr/local/google/code/llvm/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \ -p ../.. \ -clang-tidy-binary /usr/local/google/code/build/bin/clang-tidy \ -clang-apply-replacements-binary /usr/local/google/code/build/bin/clang-apply-replacements \ -checks=-*,modernize-emplace-back \ -header-filter=chrome/browser/chromeos/extensions/file_manager/* \ -fix chrome/browser/chromeos/extensions/file_manager git cl format No logic changes, No new tests. Bug: 841659 Change-Id: Ie194e7cc68289e6ec8d04e699ba7bdaeed5c5c07 Reviewed-on: https://chromium-review.googlesource.com/1106580Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Commit-Queue: Stuart Langley <slangley@chromium.org> Cr-Commit-Position: refs/heads/master@{#568562}
-
Mike Dougherty authored
Bug: 851636 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I63150a67d17d898ef00f3d32270c8b8119306814 Reviewed-on: https://chromium-review.googlesource.com/1106418 Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#568561}
-
Quan Nguyen authored
Bug: 836861 Change-Id: Ib480dfa25b45a1cc6dd1424e8f84d0891eec1a0e Reviewed-on: https://chromium-review.googlesource.com/1092095 Commit-Queue: Quan Nguyen <qnnguyen@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#568560}
-
dpapad authored
Specifically fixing: MaterialHistoryItemTest.All MaterialHistoryMetricsTest.All MaterialHistoryRoutingTest.All MaterialHistorySupervisedUserTest.All MaterialHistorySyncedTabsTest.All MaterialHistoryToolbarTest.All Polymer.dom(element).querySelector no longer returns an Array. Instead it returns an NodeList, and therefore there is no advantage of using it, compared to using the native querySelector. MaterialHistoryRoutingWithQueryParamTest.All will be addressed in separate CL. Bug: 738611 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Ic46c25c87b7d9fcbd06ef21de4c07090e4014ba6 Reviewed-on: https://chromium-review.googlesource.com/1105488Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#568559}
-
Yiming Zhou authored
These tests are the first step in building a test framework for testing chrome autofill on complex, real-world sites pages. Since interacting with live sites are flaky and vulnerable to updates to the sites' features, this framework interacts with captured sites. Sites are captured with the Web Page Replay (WPR) tool. Prior to running the test, the browser test will start WPR locally on the machine using a capture file. The test then navigates to the test site, interact with the site's checkout workflow, and verifies that autofill correctly completes the address and payment information. Tests for 5 sites are included in this code change: Amazon, Zappos, Apple, Ebay and Walmart. This change fixes the build breaks caused by the earlier change, 963800, and it also changes the tests from being driven by test code to being driven by test recipe files. The test recipe files will be generated by a chrome automation extension recording user actions. Bug: 847905 Change-Id: Ib255d52d8870744ff8304a3b908d54d039218dbb Reviewed-on: https://chromium-review.googlesource.com/1091473 Commit-Queue: Yiming Zhou <uwyiming@google.com> Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#568558}
-
Katie D authored
This is phase 3 of a refactor that allows Select-to-Speak to work with Sticky Keys, see go/sts-with-sticky-keys for more on the background for this change. Not only are EventHandlers ordered by priority across all EventTargets, but also the later an EventHandler was added to its EventTarget, the earlier it will appear in the resulting list of EventHandlers. This is a change for kDefault handlers, but kAccessibility and kSystem already had this behavior. This is for consistency across all types and requires a large change to event_dispatcher_unittest. Also adds an additional debugging function to TestEventHandler to get that handler's name. This was useful in writing the unittests for this change and may be useful to others as well. Bug: 819860 Change-Id: I4c5002fdc2cd26f0df5e94600183c3cc0cc2ff56 Reviewed-on: https://chromium-review.googlesource.com/996456Reviewed-by:
-
Lindsay Pasricha authored
This will allow for waterfall coverage with uirefresh off. Bug: 853015 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ie9be170bdfbb66f678bd0bd040c1d53d0cfbf9ba Reviewed-on: https://chromium-review.googlesource.com/1105059Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org> Cr-Commit-Position: refs/heads/master@{#568556}
-
Mikel Astiz authored
Intrusive patch that migrates session sync on Android to identify tabs by a new ID type: Android tab IDs. No direct user-facing changes expected except a) improved robustness due to reduced data redundancy, and b) a one-off loss of placeholder tabs (because no migration path is implemented) in "Tabs from other devices". Design doc (Google employees only): https://docs.google.com/document/d/1gMtPXTmvKnhJQpzSLYNoqBajWtOGYAoBNQ74XmmFe7I The proposed change is feasible after, recently with crbug.com/823798, session IDs increase monotonically (i.e. are not reused across restarts) on all platforms. This means SyncedTabDelegate can now trivially guarantee that there will be no collisions (even across browser restarts) across tab IDs (exposed by SyncedTabDelegate::GetSessionId()), as documented in this patch. On Android, there's yet another concept of tab IDs which adheres to that property and in addition get restored. By migrating to these IDs altogether (i.e. only expose Android tab IDs to sync), there's no need to support sync IDs at all, because the whole purpose of sync IDs is to be able to associate open placeholder tabs (without web contents loaded). Hence, let's simplify the code and avoid all issues related to data redundancy. Bug: 851905,843554 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Icda054906e654c18238b47e7788d4523790e09f3 Reviewed-on: https://chromium-review.googlesource.com/1096942 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#568555}
-
Jan Krcal authored
Before this CL, there was a race condition in addressing DB errors in HistoryBackend. When HistoryBackend::DatabaseErrorCallback got called, it immediately notified TypedURLSyncBridge and posted a task to kill the database. Before the database gets really killed, some other tasks can run such as tasks from the expirer that result in the bridge being notified about history deletions. The bridge does not expect backend notifications after being notified about DB error (which makes sense). This CL resolves this bug and delays the notification to the bridge so that it happens synchronously with killing the DB. This is a merge candidate for M68 Beta. Bug: 853395 Change-Id: I03d1a5c49254184e430c1619049e66895bf6dcfe Reviewed-on: https://chromium-review.googlesource.com/1105821 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
-
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/c5ef6d834a15..f704817cbbab git log c5ef6d834a15..f704817cbbab --date=short --no-merges --format='%ad %ae %s' 2018-06-19 dtu@chromium.org [pinpoint] Increase functional significance thresholds. Created with: gclient setdep -r src/third_party/catapult@f704817cbbab The AutoRoll server is located here: https://catapult-roll.skia.org 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=sullivan@chromium.org Change-Id: I9d5f3470880c9d034546537550d6f125a01c3ca2 Reviewed-on: https://chromium-review.googlesource.com/1106359Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#568553}
-
Christian Fremerey authored
Currently, TestConnectorFactory does not release the Service when it requests to be quit. This CL adds this functionality in order to allow testing of service shutdown behavior using TestConnectorFactory via observing the destruction of the service implementation class instance. Concrete example for which this was added: https://chromium-review.googlesource.com/c/chromium/src/+/1089921 Bug: 829581 Change-Id: I662c531329810fdb3dd1af5603628a0cb0dbba38 Reviewed-on: https://chromium-review.googlesource.com/1097991 Commit-Queue: Christian Fremerey <chfremer@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#568552}
-
Yafei Duan authored
If BrowserActionActivity is invoked without Chrome loaded, download notifications will not be shown since the notification bridge hasn't been created. Calling OCANBUiFactory to create an instance after native initialization is done will fix the issue. Bug: 852741 Change-Id: I1aa8b33a7d8e49e96e4cf892bc1e23ef6b535cdc Reviewed-on: https://chromium-review.googlesource.com/1102089Reviewed-by:
-
Stuart Langley authored
Steps I followed: autoninja -C out/Default chrome tools/clang/scripts/generate_compdb.py -p out/Default > compile_commands.json cd out/Default /usr/local/google/code/llvm/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \ -p ../.. \ -clang-tidy-binary /usr/local/google/code/build/bin/clang-tidy \ -clang-apply-replacements-binary /usr/local/google/code/build/bin/clang-apply-replacements \ -checks=-*,modernize-make-unique \ -header-filter=chrome/browser/chromeos/extensions/file_manager/* \ -fix chrome/browser/chromeos/extensions/file_manager git cl format No logic changes, No new tests. Bug: 841659 Change-Id: Ia04e2880847d34dcc11b071c53c610a7c9afb4fb Reviewed-on: https://chromium-review.googlesource.com/1106579Reviewed-by:
-
Stuart Langley authored
Steps I followed: autoninja -C out/Default chrome tools/clang/scripts/generate_compdb.py -p out/Default > compile_commands.json cd out/Default /usr/local/google/code/llvm/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \ -p ../.. \ -clang-tidy-binary /usr/local/google/code/build/bin/clang-tidy \ -clang-apply-replacements-binary /usr/local/google/code/build/bin/clang-apply-replacements \ -checks=-*,modernize-use-equals-default \ -header-filter=chrome/browser/chromeos/extensions/file_manager/* \ -fix chrome/browser/chromeos/extensions/file_manager git cl format Bug: 841659 Change-Id: I1df81598c3d7b7dc18dc3326de410cc91f5de4b9 Reviewed-on: https://chromium-review.googlesource.com/1106577Reviewed-by:
-
Eugene But authored
Notable changes: - DidFinishNavigation and DidStopLoading order expectations are swapped in tests. This is OK, because WebStateObserver API contract does not guarantee specific order. - NavigationContextImpl::GetDescription was updated to print is_loading_error_page_ flag. - Commit Pending Item if WebErrorPages is enabled and SlimNavigationManager is disabled. Failed navigations must always be committed. - Ignore decidePolicyForNavigationAction: callback if NavigationContext::IsLoadingErrorPage() returns true. This will suppress extra PolicyDecider callbacks. Bug: 725241 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I9bb8fc76ecd51054cd85fb43fd86353035b631de Reviewed-on: https://chromium-review.googlesource.com/1105186Reviewed-by:
Danyao Wang <danyao@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#568548}
-
Stuart Langley authored
Steps I followed: autoninja -C out/Default chrome tools/clang/scripts/generate_compdb.py -p out/Default > compile_commands.json cd out/Default /usr/local/google/code/llvm/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \ -p ../.. \ -clang-tidy-binary /usr/local/google/code/build/bin/clang-tidy \ -clang-apply-replacements-binary /usr/local/google/code/build/bin/clang-apply-replacements \ -checks=-*,modernize-use-nullptr \ -header-filter=chrome/browser/chromeos/extensions/file_manager/* \ -fix chrome/browser/chromeos/extensions/file_manager git cl format Bug: 841659 Change-Id: I61747c05ca97127ad190de3e11337b0045128fea Reviewed-on: https://chromium-review.googlesource.com/1106578Reviewed-by:
-
Andrew Grieve authored
Also - Remove a File.exists() call from the normal start-up flow. Hoping this helps determine root cause of bug. Bug: 849550 Change-Id: Iaadeedbfedeb8e6fd76bc93f3d6729c579c89b44 Reviewed-on: https://chromium-review.googlesource.com/1102905Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#568546}
-
Shakti Sahu authored
Fixed several issues with animation : 1 - Color of the completed download check mark was grey. Changed it to light blue and smoothened the transition. 2 - For API < 25, when onAnimationEnd() is called, isRunning() still returns true, hence restartAnimation bails out early. This is a known android bug, workaround is to post the restart method. 3 - The fill animation was not being reset to correct deep blue color at the beginning of every loop. Fixed it. Bug: 853860 Change-Id: Iff2414f2e94ed85711be19a13776db31e74292ee Reviewed-on: https://chromium-review.googlesource.com/1105500Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Shakti Sahu <shaktisahu@chromium.org> Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> Cr-Commit-Position: refs/heads/master@{#568545}
-
Daniel Rubery authored
Add a PhishGuard event log to chrome://safe-browsing. Currently only logs when triggered by on focus or password reuse events. Will add further logged events in future CLs. Screenshot: http://screen/YPyPv8CbirO Bug: 849351 Change-Id: I7341b79685af1839584a165a7c1e3ee200947329 Reviewed-on: https://chromium-review.googlesource.com/1102665Reviewed-by:
vitaliii <vitaliii@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#568544}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/ba61029c5b49..96aa535b782f git log ba61029c5b49..96aa535b782f --date=short --no-merges --format='%ad %ae %s' 2018-06-19 benjaminwagner@google.com Remove .bat and .exe from commands where possible. Created with: gclient setdep -r src/third_party/skia@96aa535b782f The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;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:852581 TBR=kjlubick@chromium.org Change-Id: I59207c703be4e7429eee0a39a69724e23d9e331b Reviewed-on: https://chromium-review.googlesource.com/1106497Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#568543}
-
Emily Hanley authored
Also turning on sharding on main waterfall for linux and mac configs. Bug:713357 Change-Id: I3aa3c67d5d23b2549455d363bbef374fb70fba4d NOTRY=true # CQ flakes, related tests passed Change-Id: I3aa3c67d5d23b2549455d363bbef374fb70fba4d Reviewed-on: https://chromium-review.googlesource.com/1106428 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by:
Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#568542}
-
Pete Williamson authored
For some apps (Inbox), we discovered the mime type in content uri and contentProvider.getType() doesn't match the mime type in the intent. To prevent that from making chrome think the file is really a download, we now set headers whenever we see a mime type in the intent that is used by MHTML. Bug: 852629 Change-Id: I874e2c976a9817d3a35b8587044f7589c2d498e8 Reviewed-on: https://chromium-review.googlesource.com/1103592Reviewed-by:
Jian Li <jianli@chromium.org> Reviewed-by:
-
Marijn Kruisselbrink authored
Failed() might have caused |this| to be destroyed, and we certainly don't want to call OnFinishLoading after an error, so add a missing return statement. Bug: 788890 Change-Id: Ida617ded94891878d0d3d167ffdcfea2fbb53c03 Reviewed-on: https://chromium-review.googlesource.com/1106296Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#568540}
-
GauthamBanasandra authored
Presently, the isNodeJS() method uses '===' operator which evaluates to true only for JS Capability. This check fails for inspector_main target as multiple capabilities are set for it. As a result, source maps doesn't get applied for inspector_main because the isNodeJS() check fails and prevents prefixing of "file://" to sourceMapURL as a consequence, leading to the source maps resource not being served. In this patch, we set only the JS Capability for inspector_main if the 'v8only' parameter in the URL is set to true. Bug: 846642 Change-Id: I96a01f3b984bf552c89c873d10f3bf0b5ecd67c8 Reviewed-on: https://chromium-review.googlesource.com/1095064 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#568539}
-
Ryan Landay authored
We don't allow taking screenshots in the current overlapping Android tab switcher when incognito tabs are open, even if the normal mode stack is active, because we show the edge of the incognito tabs visible on-screen. For the new horizontal tab switcher, we don't do this, so we can allow taking screenshots in this case. Bug: 853805 Change-Id: Ic7054524735b888c39b9a3373684971c962a6030 Reviewed-on: https://chromium-review.googlesource.com/1105392 Commit-Queue: Ryan Landay <rlanday@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#568538}
-
sebsg authored
Change-Id: If7c15bc7f27bb9a311d28555d1efea4b5c1d0cf2 Reviewed-on: https://chromium-review.googlesource.com/1106287 Commit-Queue: Jared Saul <jsaul@google.com> Reviewed-by:
Jared Saul <jsaul@google.com> Cr-Commit-Position: refs/heads/master@{#568537}
-
Danyao Wang authored
This removes the brief omnibox shadow when animating NTP. With slim-nav, NTP navigation item is still pending at time of |animateNewTab:inForegroundWithCompletion|, so using last committed item URL will not correctly animate. Bug: 819606 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ie6b5ecad62f67f1b380e29e2a97bae0cbc19b45a Reviewed-on: https://chromium-review.googlesource.com/1106420Reviewed-by:
edchin <edchin@chromium.org> Commit-Queue: Danyao Wang <danyao@chromium.org> Cr-Commit-Position: refs/heads/master@{#568536}
-
danakj authored
The impl-side SetTrilinearFiltering() is unused, since it is only used for property tree building, and on the impl-side it comes from the test properties. So it's removed. R=weiliangc@chromium.org Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ib9a726dbaa45665a0cd6c585a69e2f7800db78fa Reviewed-on: https://chromium-review.googlesource.com/1105348 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
weiliangc <weiliangc@chromium.org> Cr-Commit-Position: refs/heads/master@{#568535}
-
