- 02 Oct, 2019 5 commits
-
-
Christopher Thompson authored
This triggers showing new security strings in Page Info when a connection uses legacy TLS versions. This is gated on the feature flag security_state::features::kLegacyTLSWarnings. Bug: 989607 Change-Id: Ic00380c240471e18e1cb09aff4444a1d2fd4b38b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832665 Commit-Queue: Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#701831}
-
Piotr Bialecki authored
Previously, if the device did not provide stage parameters and the app requested `local-floor` space, the standing transform would be set to a default value by XRReferenceSpace::SetFloorFromMojo(). This CL does not change that behavior - instead, it makes ARCore return staging parameters so that default values won't be filled out by blink for ARCore sessions. Change-Id: I9eead334f4135a2a1786c892f77b50b8b73a86b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833299 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Auto-Submit: Piotr Bialecki <bialpio@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#701830}
-
Haiyang Pan authored
fuchsia-x64-dbg and the mirrored trybot fuchsia-compile-x64-dbg are verifying if the fuchsia compile is OK. Currently the trybot does not have any compile targets. Adding the additional_compile_targets should make the trybot compiling as expected Bug: 1001643 Change-Id: I07819abe01c22eadd2edbe8674f074876a8e784a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1815612 Commit-Queue: Haiyang Pan <hypan@google.com> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#701829}
-
Peter K. Lee authored
CreateViewController() needs an additional parameter to open a new tab. 1-parameter version of CreateViewController() API is considered obsolete and will be deleted in a followup CL. Bug: 1007242 Change-Id: Ic8f9a8a4ebd06aecf39e7f427ccedbf3f3d2df34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833788 Commit-Queue: Peter Lee <pkl@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#701828}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0b1d16c42ae5..f0ba4163ae14 Created with: gclient setdep -r src-internal@f0ba4163ae14 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 jbudorick@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/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: I6148541e30d68d6440b94910a689e1e1ae0a8640 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834524Reviewed-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@{#701827}
-
- 01 Oct, 2019 35 commits
-
-
Julie Jeongeun Kim authored
This CL converts TraitsTestService from network_traits_test_service.mojom to new Mojo types using PendingRemote, Remote, and ReceiverSet. Bug: 955171 Change-Id: Ia296a254a2cea718e2a36a8c804572ff28546a49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829636Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Julie Kim(OoO until 4 Oct) <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#701826}
-
Robbie McElrath authored
aw_features_list.h is used by //aw/browser/gfx, so it needs to be split off //aw/browser:browser to break a circular dependency. This also renames it to aw_features.h to make it consistent with the rest of Chromium. Test: gn check out/aw 'android_webview/*' Bug: 934152 Change-Id: I8e589df0283edfb7f20a20deef4e882fbbbf8a28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833703Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Cr-Commit-Position: refs/heads/master@{#701825}
-
Manas Verma authored
Ensuring we limit the amount of times we offer FIDO authentication to users. 3 <- Max strikes. 1 <- Strikes added when user declines opt-in offer. 2 <- Strikes added when user verification failed. 3 <- Strikes added when user opts-out from settings page. Strikes expire in 6 months. Bug: 949269 Change-Id: Id15e949ec1189ea453a794ab93a3e698017a5ece Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824362 Commit-Queue: Manas Verma <manasverma@google.com> Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Tommy Martino <tmartino@chromium.org> Cr-Commit-Position: refs/heads/master@{#701824}
-
Xianzhu Wang authored
Use viewport properties instead. This is required by CompositeAfterPaint and also works for pre-CompositeAfterPaint. R=bokan@chromium.org, pdr@chromium.org TBR=# passive change in content/renderer Bug: 909750 Change-Id: Ia1b09fe2ae94f67732e8449449532d73191c9c7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1818717 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#701823}
-
Kent Tamura authored
The purpose of the state restore feature is to restore user input. So, we should not restore states for disabled/readonly controls, which users can't update. Bug: 1000926 Change-Id: Iec5ad3999e814fbd248751c2608422fc26315417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1830486Reviewed-by:
Mason Freed <masonfreed@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#701822}
-
Matthew Mourgos authored
Bug: 1009834 Change-Id: I18d88a77f43f2aa5a2f0b923838d3726038bb0c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834565Reviewed-by:
Manu Cornet <manucornet@chromium.org> Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Cr-Commit-Position: refs/heads/master@{#701821}
-
Matthew Mourgos authored
Bug: 1009662 Change-Id: I5e7626b59d05d8302091afee6cea2ed0e6effb9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833708Reviewed-by:
Manu Cornet <manucornet@chromium.org> Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Cr-Commit-Position: refs/heads/master@{#701820}
-
Kyle Horimoto authored
In the InternetDetailDialog, the field didn't have the proper padding, and in the settings page, it had an extra border-top. This CL fixes both of these issues. Bug: 1009985 Change-Id: Icf90d70db51e93fc5eed33bdb13149830f978733 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834245 Auto-Submit: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#701819}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/f1b21e4633f6..b9aca9494e40 git log f1b21e4633f6..b9aca9494e40 --date=short --no-merges --format='%ad %ae %s' 2019-10-01 ehmaldonado@chromium.org gclient: Skip calling update_depot_tools if DEPOT_TOOLS_UPDATE is 0. Created with: gclient setdep -r src/third_party/depot_tools@b9aca9494e40 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 agable@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/+/master/autoroll/README.md TBR=agable@chromium.org Bug: None Change-Id: I370aac39ee107b238045b622e4727bae59b5cc1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834207Reviewed-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@{#701818}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/e90e73e0..b3ced8d6 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I6134fe64a38f8670518889587386547b1f0449d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834365Reviewed-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@{#701817}
-
Austin Eng authored
Bug: dawn:208 Change-Id: I25523465ccdcb721477437a5ee31614127ea47ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1804035Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#701816}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/ca0d0564630e..16236fcfbe31 git log ca0d0564630e..16236fcfbe31 --date=short --no-merges --format='%ad %ae %s' 2019-10-01 rmhasan@google.com [typ] Update artifacts module to handle web tests artifacts Created with: gclient setdep -r src/third_party/catapult@16236fcfbe31 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 skyostil@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/+/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_optional_gpu_tests_rel TBR=skyostil@google.com Bug: chromium:982208 Change-Id: I5887340eb9995ea06d2e313e34b89edbc96f796a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834522Reviewed-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@{#701815}
-
Julie Jeongeun Kim authored
This CL converts ServiceProcessPtrto new Mojo types using ReceiverSet, Remote, and PendingReceiver. Bug: 955171 Change-Id: Ia215917271955a80c677bf8222d06f25dd5d950f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829630Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Julie Kim(OoO until 4 Oct) <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#701814}
-
Weiliang Chen authored
Set up output surface capabilities correctly so SkiaRenderer could initialize its own overlay candidate validator for Adnroid classic case. Bug: 979795 Change-Id: I505758515313007cfdd07045ce6c1d65bf3c1a43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1809811 Commit-Queue: weiliangc <weiliangc@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#701813}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5be3c1326391..674f77a24b62 git log 5be3c1326391..674f77a24b62 --date=short --no-merges --format='%ad %ae %s' 2019-10-01 csmartdalton@google.com Clear and discard stencil buffers on tilers, take 2 2019-10-01 halcanary@google.com doc: cleanup release notes 2019-10-01 egdaniel@google.com More bounds fixes for StrokeRect and DefaultPath when using MSAA for non-aa. Created with: gclient setdep -r src/third_party/skia@674f77a24b62 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 rmistry@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/+/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 TBR=rmistry@google.com Bug: None Change-Id: If8e1bfbe967cf7df1242d7eed207bac6a2e724ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834462Reviewed-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@{#701812}
-
Nate Fischer authored
This adds a README for //aw/renderer/. This mostly talks about WebView's renderer support, and how it varies from Chrome. Bug: 1009884 Test: tools/md_browser/md_browser.py Test: Upload to gerrit > open file > click "gitiles" Change-Id: I1164c363c90aba95a69df6d85363592cb4d52639 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832984Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#701811}
-
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/+/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: I5246dc5ef0e40bef54415d243c8e8652abbf0c95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834483Reviewed-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@{#701810}
-
Klaus Weidner authored
This is intended to address concerns where detached layers are left alive with a potentially-stale paint controller, i.e. for fullscreen overlay video. GraphicsLayers in this state will not have GraphicsLayer::Paint called on them, and Paint updates the GraphicsLayer's display item's references back to the layout tree, so failure to do that could lead to stale references. The method added by this change recursively invalidates the paint controllers on the parent node and its subtree. See also https://crrev.com/c/1802823 which invalidated in RemoveFromParent, but that got rolled back due to performance alerts. This new version is intended to be used as needed before calling RemoveAllChildren to avoid slowing down the typical case. Change-Id: I3f81b78b41823f749f212bf88b931d72f201ca76 Bug: 1009011, 991747 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1828075 Commit-Queue: Klaus Weidner <klausw@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#701809}
-
Xing Liu authored
Revert in https://chromium-review.googlesource.com/c/chromium/src/+/1833927. Reason: Need a rebase for a recent change. When running the background task or during a user action, we may call into platform background task API for multiple times, which is unnecessary. This is caused by multiple calls through ImpressionHistoryTracker::Delegate. This CL fixed this issue and added a browser test to enforce only one background task API is invoked. ImpressionHistoryTracker::Delegate will be deleted in a following CL. TBR=hesen@chromium.org Bug: 965133 Change-Id: I47c6dd13b7866947bbcca306434329185f36a938 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832488 Commit-Queue: Xing Liu <xingliu@chromium.org> Reviewed-by:
Hesen Zhang <hesen@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#701764} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834563Reviewed-by:
Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#701808}
-
Alex Newcomer authored
Remove the custom event routing, this fixes the bug. Bug: 1009041 Change-Id: I88a096a18ce70f459afcf7ecaa328c4ac2296d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832283 Commit-Queue: Alex Newcomer <newcomer@chromium.org> Auto-Submit: Alex Newcomer <newcomer@chromium.org> Reviewed-by:
Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#701807}
-
Theresa Wellington authored
As a follow-on, we might also want to update the touch target size. BUG= Change-Id: I48740f8504f16b434373ad96140601098dcc246c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834246 Commit-Queue: Theresa <twellington@chromium.org> Commit-Queue: Matthew Jones <mdjones@chromium.org> Auto-Submit: Theresa <twellington@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#701806}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/a66d10dcbbfc..40b3bbb9073b git log a66d10dcbbfc..40b3bbb9073b --date=short --no-merges --format='%ad %ae %s' 2019-10-01 jclinton@chromium.org Remove bluestreek-pre-cq hardware tests 2019-10-01 dburger@chromium.org Master Chrome PFQ no longer publishes uprevs. 2019-10-01 ahassani@chromium.org chromeos_config: Mark lakitu paladin builders experimental 2019-10-01 ahassani@chromium.org paygen: Deprecate sha1_hex and md5_hex Created with: gclient setdep -r src/third_party/chromite@40b3bbb9073b If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I7949f5a744f1df4757b366eefc8f18c4401022b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834482Reviewed-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@{#701805}
-
Alex Newcomer authored
Per the spec, the hotseat should paint over everything. Bug: 1009049 Change-Id: I1a967c28c82a5aab1e92cb2264a830fc4798a2a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834564 Auto-Submit: Alex Newcomer <newcomer@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Commit-Queue: Manu Cornet <manucornet@chromium.org> Reviewed-by:
Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#701804}
-
Christopher Thompson authored
This adds a check to SecurityStateTabHelper to mark whether a page was loaded over legacy TLS versions in the VisibleSecurityState struct. This status is then used by the security_state code to downgrade the security level to WARNING. The SecurityStateTabHelper code also checks the pref set by the SSLVersionMin enterprise policy to determine whether to set the flag in the VisibleSecurityState. This version can be racy at browser startup, due to how the component proto is loaded from disk (as BEST_EFFORT). A followup CL will change that task to USER_VISIBLE to avoid this. Another followup CL will change the Page Info security summary for pages with the legacy TLS flag set in their VisibleSecurityState. Bug: 989607 Change-Id: I510eafc0124f433ec4e4ce81e4ece4f1321bde6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829462 Commit-Queue: Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#701803}
-
Ken Rockot authored
This eliminates the one remaining use of Connector from Content child process code, also eliminating ChildThread::GetConnector(). This is a precursor to moving all Content process management infrastructure off of the Service Manager. Bug: 977637 Change-Id: I75a25688d5cd1a3f18bf06db667d40d9ca8d5bbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832316Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#701802}
-
Joel Hockey authored
* ClipboardOzone updated to: - keep separate OfferedData for each buffer type - Call ClipboardMonitor::GetInstance() ->NotifyClipboardDataChanged() in the same way that the aura clipboard currently does. - handle mime types for chromium/x-web-custom-data in the same way that aura clipboard currently does. * Update update_sequence_cb_ comment from crrev.com/c/1800849 Bug: 985187 Change-Id: I67ed507de42ca3e7ebf943710ae6c14f19f8c594 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1804694Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#701801}
-
chrome://downloadsHector Carmona authored
Bug: 986004 Change-Id: Ied27010d6860940bb6444f764cb442cae22ea545 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825581Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#701800}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/988f71701886..616a4dc0f2fb git log 988f71701886..616a4dc0f2fb --date=short --no-merges --format='%ad %ae %s' 2019-10-01 timvp@google.com Vulkan: Full support for program interface queries 2019-10-01 jmadill@chromium.org Vulkan: Implement multi-threaded GL. Created with: gclient setdep -r src/third_party/angle@616a4dc0f2fb 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 cwallez@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/+/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_optional_gpu_tests_rel TBR=cwallez@google.com Bug: None Change-Id: Idb5f537bc8ec90ec15e2b26c575524dd27c359a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834461Reviewed-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@{#701799}
-
Aran Gilman authored
The slider is a placeholder and will likely be replaced by paper-slider in the future. Bug: 952034 Change-Id: Ib42b5ea4191883a3032df12aa6e50183ae06b3b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829928Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Aran Gilman <gilmanmh@google.com> Cr-Commit-Position: refs/heads/master@{#701798}
-
Peng Huang authored
With Intel GPU, chrome doesn't use virtualized gl contexts, so the WebGL should have a dedicated gl context. The ExternalVkImageBacking's methods will change the current gl context, in some case, the method could be called from GLES2CmdDecoder. After returning from those methods, the current gl context will be changed. It cause the problem. This CL fixes the problem by only make a gl context current, if there isn't a gl context current. Bug: 1005227,1004840,1004837 Change-Id: I5cca398a8e4216d5efb0d3f36e9aceae6ce1b78c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834030Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Saman Sami <samans@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Auto-Submit: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#701797}
-
Toni Barzic authored
If masked apps grid fadeout zone is disabled (which happens if background blur is disabled), increase the apps grid margins to cover the full fadeout zone (so the app list items are not shown in the empty border space during apps grid drag) BUG=1009548 Change-Id: I3a5895e1f71764dc689e8a58feb4214a89e021a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833295 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#701796}
-
Michael Thiessen authored
No functional changes intended, please revert if things break. This function is a large, and hard to follow. I'm hoping to break out a bunch of functions that are clearer about what they're doing and make ordering clearer. Bug: 1006927 Change-Id: I895c746bb5edbb04a9ad06b0cb643deb1f6945a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832521 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#701795}
-
Chris Cunningham authored
NOTE: this CL replaces, https://chromium-review.googlesource.com/c/chromium/src/+/1828226 which was submitted in error. This changes the behavior implicit resizing of for VP8/9 video. By implicit, we mean streams where the dimensions change without a new MSE init segment that explicitly describes the new size. Prior to this CL, we took whatever resolution was specified by the container metadata and scaled any later differing resolution into an element of that original size. Many of our decoders worked this way before https://chromium-review.googlesource.com/c/chromium/src/+/1026992/, which shifted the consensus is to allow dynamic resize. This CL makes the libVPX wrapper consistent with those. When the size changes we will update videoWidth and videoHeight and fire a 'resize' event. Bug: 992235,837337 Test: https://github.com/web-platform-tests/wpt/pull/19030, with --disable-features=FFmpegDecodeOpaqueVP8 Change-Id: I7c65810c545511cfa3441c7cbb9e2771159bc88a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832478 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#701794}
-
Yuchen Liu authored
Add a method to support media::mojom::Renderer with CastRenderer. This provides a separate channel for internal usage on media::Renderer over mojo. Merge-With: eureka-internal/319345 Bug: internal b/131591346 Test: as mentioned in the bug. Change-Id: Ie44155354db3ad0d59669cc5ee4b721c3ec3b4b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832688Reviewed-by:
Sean Topping <seantopping@chromium.org> Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Commit-Queue: Yuchen Liu <yucliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#701793}
-
Avery Musbach authored
MaybeRestoreSplitView reconstructs split view state from window states, which only makes sense in tablet mode. It shall bail out in clamshell. Test: ash_unittests DesksWithSplitViewTest.SwitchToDeskWithSnappedActiveWindow Bug: 1009663 Change-Id: I3e043a847d3d3b594dcf7c78dd4745eced4b2752 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832902 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#701792}
-