- 29 May, 2019 40 commits
-
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/98266a4af182..e8e7d7b0bc10 git log 98266a4af182..e8e7d7b0bc10 --date=short --no-merges --format='%ad %ae %s' 2019-05-29 jonaso@webrtc.org Move Connection into it's own .h/.cc file. 2019-05-29 mirtad@webrtc.org Move H.264 SPS VUI rewriting to FrameEncodeMetadataWriter. 2019-05-29 kwiberg@webrtc.org WebRTC Opus C interface: Add support for non-48 kHz decode sample rate 2019-05-29 titovartem@webrtc.org Propagate screenshare info into video track and it's source. Created with: gclient setdep -r src/third_party/webrtc@e8e7d7b0bc10 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I0de0c441d9c79569782813412a4f5f7c7490275e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634952Reviewed-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@{#664251}
-
Polina Bondarenko authored
Log a netwrok error if PerformWebRequest fails. BUG=b:133770869 TEST=build Change-Id: Iaa3f7dadc916fa184370b8dea769030f56aedb0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634693Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Polina Bondarenko <pbond@chromium.org> Auto-Submit: Polina Bondarenko <pbond@chromium.org> Cr-Commit-Position: refs/heads/master@{#664250}
-
Kevin Ellis authored
The patch addresses cases where timeline-dependent code was being called without first checking for an active timeline. Bug: 967507, 967509 Change-Id: I4383bf5cdbcc8dd92e52c4e281d89d3efd36bd83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632615 Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#664249}
-
Yi Su authored
This CL removes the temporary source file items in //ios/web/public/BUILD.gn that were kept to avoid brekaing ios_internal. Since the dependency chain in ios_internal has been updated, these items can be removed now. Bug: 942244,956511 Change-Id: I76153ec5e2f5407299e2c14ec51de9a429619e5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634859Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Yi Su <mrsuyi@chromium.org> Cr-Commit-Position: refs/heads/master@{#664248}
-
Roman Sorokin authored
* Also extracted oobe_screens_utils * Also extracted ExitHandler for enrollment screen Bug: 966887 Change-Id: Ic07357323012944c5c6ec017f4bae129219a91ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628726Reviewed-by:
Denis Kuznetsov <antrim@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#664247}
-
jdragonbae authored
OnAddressListChanged, OnCreditCardsChanged Instead it should have a single OnPersonalDataChanged call Bug: 923868 Change-Id: Ie6bc51cf71f82228df32db551489bf66168a54e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631451 Commit-Queue: sebsg <sebsg@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Auto-Submit: Jaeyong Bae <jdragon.bae@gmail.com> Cr-Commit-Position: refs/heads/master@{#664246}
-
Dominic Battre authored
Bug: 967588 Change-Id: I92bea6a15e96ee09e129467938e0bbc2b45b8de7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631662 Commit-Queue: Dominic Battré <battre@chromium.org> Commit-Queue: Fabio Tirelo <ftirelo@chromium.org> Auto-Submit: Dominic Battré <battre@chromium.org> Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Cr-Commit-Position: refs/heads/master@{#664245}
-
Roman Aleksandrov authored
Update text about data handling. Bug: 959262 Change-Id: I2d25037d87d33c1eb8f964f23da6b0fcae0bc9c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613254Reviewed-by:
Thiemo Nagel <tnagel@chromium.org> Commit-Queue: Roman Aleksandrov <raleksandrov@google.com> Cr-Commit-Position: refs/heads/master@{#664244}
-
Michael van Ouwerkerk authored
Also clean up some redundant code and use lambdas. Bug: 931198 Change-Id: I8a30a6ead0e573fb0ed2f7bd0e46a5376cc5720a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632229 Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#664243}
-
Balazs Engedy authored
This is a reland of 19c977cb. The original CL incorrectly assumed that Blink has a built-in mechanism such that marking `ondevicemotion` as [SecureContext] would implicitly result in calls to `window.addEventHandler('devicemotion', ...)` being ignored when made from non-secure browsing contexts. However, in reality there is no coupling between the event handler IDLs and event types accepted by `addEventListener()`, in fact, there is no validation of event types at all, EventListenerObserver::DidAddEventListener will be dispatched to all observers, even for made up event type names. This CL updates DeviceMotionController and friends to expect this and simply return early if an event listener was added in a non-secure context. Web tests have also been added to verify this behavior and that there are no crashes. Original change's description: > Mark Device Orientation API event handlers as [SecureContext]. > > This CL concludes the work to restrict the API to secure browsing contexts. > It removes the `RestrictDeviceSensorEventsToSecureContexts` flag that could > previously be disabled manually to re-enable the API in non-secure contexts, > tests that verified the behavior with this flag disabled, as well as all > deprecation warnings. > > Bug: 932078 > Change-Id: I742ab162e97017e47b44dfe72e99ef9c24178b36 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632329 > Reviewed-by: Reilly Grant <reillyg@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Commit-Queue: Balazs Engedy <engedy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#664180} Bug: 932078 Change-Id: I40f1e1b6e1deac2bd4387366ace10dc7e8f69e2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634877Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#664242}
-
Julie Jeongeun Kim authored
This CL is a part of onion-souping web_application_cache_host_impl. It moves web_application_cache_host_impl.cc/h, renderer_webapplicationcachehost_impl.cc/h and application_cache_host_for_shared_worker.cc/h to third_party/blink/renderer/core/exported/. For moving them, it adds some interfaces, 1) WebLocalFrameClient::UpdateSubresourceFactory 2) Platform::IsSchemeSupportedForAppCache 3) WebApplicationCacheHost::CreateWebApplicationCacheHostFor{Frame, SharedWorker} Once onion-souping web_application_cache_host_impl is finished, CreateWebApplicationCacheHostFor{Frame, SharedWorker} will be removed. Bug: 950159 Change-Id: I9660fc00f9e15cfbbfc263cb828afdfd5b3ee03e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575057 Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com> Reviewed-by:Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/673784153395..98266a4af182 git log 673784153395..98266a4af182 --date=short --no-merges --format='%ad %ae %s' 2019-05-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 99181c0b..d4906ebd (664078:664184) Created with: gclient setdep -r src/third_party/webrtc@98266a4af182 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I187247b7eae1a4035a289a56ba701dc142ea2970 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634550Reviewed-by:
-
Friedrich Horschig authored
This CL wires the AddressAccessoryController implementation to the UI component which effectively displays Addresses in a bottom sheet. To retrieve the data, the ManualFilling controller will poll the data when another event triggers a UI update. This definitely overtriggers since the password manager updates data for every field while address data may remain stable for the whole lifetime of a tab. Bug: 962548 Change-Id: I52900abd82b0e8773b25f906231c7db7dd9ec31c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614202 Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Cr-Commit-Position: refs/heads/master@{#664239}
-
Alex Chau authored
- Added a skeleton of SharingService with 3 APIs, implementation is empty for now - Added a proto for SharingMessage - Added definition of handler for SharingMessage - SharingService is initialized with a profile - Added OWNERS file Bug: 966028 Change-Id: I8beb1d001b8186b7259c7421f6d6d906bcf4a2f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627367 Commit-Queue: Alex Chau <alexchau@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Auto-Submit: Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#664238}
-
Chromium WPT Sync authored
Using wpt-import in Chromium fedd9a22. With Chromium commits locally applied on WPT: e90c6ef0 "NG/DL: Implement size containment (and display lock) for NG fieldset algo" be76d09e "[ServiceWorker] Reject update() from within installing workers" abf2ac5e "webrtc wpt: avoid race conditions" d9a6ec05 "[MediaStreamTrack] Remove tests and existing support for the 'volume' property." 0882bebe "Change ICE connection state on transceiver changes" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, lpz@chromium.org, robertma@chromium.org: external/wpt/tools NOAUTOREVERT=true TBR=raphael.kubo.da.costa No-Export: true Change-Id: I115f1808854c75850386291d4932cfcbbf4efdf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634711Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#664237}
-
arthursonzogni authored
On Android. TBR=kinuko@chromium.org CC=rsorokin@chromium.org Bug: 966820 Change-Id: If3ce3ecb3f65a370a630f8fc0a1d641f51278e1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634698Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#664236}
-
Dominic Battré authored
This reverts commit 5750ecde. Reason for revert: Test faked again in https://ci.chromium.org/p/chromium/builders/ci/Win7%20Tests%20%281%29/91959 but did not produce usable screenshots. Original change's description: > Enable screenshotting for AutofillInteractiveTests > > A bunch of interactive_ui_tests from AutofillInteractiveTests.* are flakily > timing out on the win7 builders. This CL enables pixel outputs. Hopefully that > reveals why the tests time out. > > Bug: 967588 > Change-Id: Icc6296fbb324fe0e2920807afa6a6ceea121b691 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632330 > Commit-Queue: Fabio Tirelo <ftirelo@chromium.org> > Auto-Submit: Dominic Battré <battre@chromium.org> > Reviewed-by: Fabio Tirelo <ftirelo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#663822} TBR=battre@chromium.org,ftirelo@chromium.org Change-Id: Ib98f0fd43cd1c5dd0784b6b342589109e2521e47 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 967588 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634835Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#664235}
-
Arthur Hemery authored
When navigating back to a frame that has subframes, we should try to restore the subframes to their latest history item. This is currently done by OpenURL and should be done by BeginNavigation instead. Design doc: https://docs.google.com/document/d/13Rqdg1HBmtfnYMUXvg7SpUl3bJisTElfyMc1Ze8hLdE/edit# This is patch 2/2. This patch only modifies the behavior for IsPerNavigationMojoInterface on. See https://chromium-review.googlesource.com/c/chromium/src/+/1596448 for trybots run with the flag on. Bug: 962518 Change-Id: If153cbcb8e1d11bd75be519839c7f36c3907b1dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594576 Commit-Queue: Arthur Hemery <ahemery@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Cr-Commit-Position: refs/heads/master@{#664234}
-
Vadym Doroshenko authored
For HttpAuth NewPasswordFormManager needs only FormDigest, let's make it accept FormDigest instead of whole form. Bug: 831123 Change-Id: I3ba1abe0db5516fa9ff671d77b97099e0330d49a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634696 Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
-
A Olsen authored
The RecheckTask, which only had one ability - it could be cancelled by InvalidateWeakPtrs - is expanded into the Rechecker class, which now contains much of the logic of the saml_password_expiration_notification.cc It still works on much the same lines as previously - only one ever exists at a time (for the primary user), weak pointer invalidation ensures that not too many tasks are posted, and each time it wakes up, it checks to see what has changed and shows a notification / posts a new task for the future. However, it now also listens to lock screen events for the primary user. This will allow us to pop up the notification again immediately after screen unlock, which is a good time for the user to update their password if required. This will be done in a follow up CL. Bug: 930109 Change-Id: Id3d3c238251e4e59ee986fc944b461d966eefa5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631699Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: A Olsen <olsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#664232}
-
Maksim Ivanov authored
Embed all screen_gaia_signin's contents (which is responsible for Gaia/SAML/offline/SAML interstitial/AD authentication) into a Polymer module. This is a first step in the refactoring of screen_gaia_signin from the old-style login.createScreen-based implementation onto the new Polymer-based approach. Bug: 964069 Test: manual Change-Id: I69e079d1d8e6c3c9ecbe08dfb59f397168cbf187 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615744 Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Reviewed-by:
-
Eric Willigers authored
The following shorthand properties now allow any 1 or 2 of the 3 values (width, style, color) to be omitted: - border-block - border-block-start - border-block-end - border-inline - border-inline-start - border-inline-end https://drafts.csswg.org/css-logical-1/#border-shorthands Value: <'...-width'> || <'...-style'> || <color> Bug: 968057 Change-Id: I571ccf0e8bea38d985a96cf3cccf49d7adfe4d76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635169 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#664230}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/82c5fe1de06e..24c961c98efd Created with: gclient setdep -r src-internal@24c961c98efd The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=ricea@google.com,jeffreycohen@google.com,seblalancette@google.com,mkwst@google.com Change-Id: Ice27c73408614377953589b7afcc84fc2c2b7624 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635190Reviewed-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@{#664229}
-
Mikel Astiz authored
This also makes some unreachable paths more obvious and now simplified or, if actually reachable, handled better. Bug: 967417 Change-Id: I63f9c129497d845d149b9549b411de3c4ffa3c83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631405 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#664228}
-
Miyoung Shin authored
This is a part of moving manifest implementation to blink. This CL cleans up the temporary code added for the usage of non-Blink. Bug: 704441 Change-Id: Ib6fcce07dfdd1b817b75d52fe15290ba990da03e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633893Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Cr-Commit-Position: refs/heads/master@{#664227}
-
Caitlin Fischer authored
Bug: 958333 Change-Id: Ia750d141ca4104f57d33a77bf253878d03d97379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632389 Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
-
Carlos Caballero authored
BEST_EFFORT tasks will not run until after startup and only if there is no critical work pending. This patch should not change the current behaviour. Please double check whether the task being posted via BrowserThread::PostAfterStartupTask really cares about being run after startup or just wants to run after any critical work was completed. If you are fine with it just running after critical work has completed LGTM and keep on with your life. If that is not the case let me know and please explain your reasoning in a comment. More details: https://docs.google.com/document/d/1P8PV1qX2cOR2WRFD6v9CjygJkE_mftCtJ7BoqQHCKZI This CL was uploaded by git cl split. R=finnur@chromium.org Bug: 887407 Change-Id: Ia80c2e7d7f09a976239c9325c7fcf5d190b5dd2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631702 Commit-Queue: Finnur Thorarinsson <finnur@chromium.org> Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Auto-Submit: Carlos Caballero <carlscab@google.com> Cr-Commit-Position: refs/heads/master@{#664225}
-
BUG=762641 TBR=mukai@google.com Change-Id: I2c68d7e6aea3357dfa6a467712cc6a557740fc95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634710Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#664224}
-
Dominik Röttsches authored
After clarifying with the Mojo team, the initial approach of waiting for a WaitableEvent before running the asynchronous Mojo callback, this was identified as the incorrect approach. Instead, store the callbacks until the font table builder is ready, then run them on the same sequence on which the Mojo call came in. Bug: 960263, 889864 Tbr: wfh, rsesek Change-Id: Ief3fe6a21df28f5aa27a4daa6d65540bddf2b43e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605985Reviewed-by:
Dominik Röttsches <drott@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#664223}
-
Mark Cogan authored
This CL consolidates the public/app and public/global_state directories into a single /init directory, and groups the corresponding private implementation files to match in //ios/web/init/. Additionally: - ios_global_state.mm was in public/; it's now moved to //ios/web/init. - network_context_owner.h is moved into init/; it was previously in the root public/ directory. - The inexplicable dependency loop in //ios/web/public/app is resolved. - Three TODOs without bugs had bugs created and the TODOs were updated accordingly. - README.md files were added to the public and private init/ directories. Bug: 942244, 728161 Change-Id: I52af0101d1a2f75be8a5b502485f32fbed0763a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624327 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
Misha Efimov <mef@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#664222}
-
Richard Knoll authored
We enabled NotificationViewMD by default on M75, so the legacy NotificationView can be removed with all its dependencies. Bug: 967666 Change-Id: Ie81450d001026fea092541d3fb0c5849eb98493d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632074 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
-
Rune Lillesveen authored
Override the base background color with black for the dark color scheme, but use the base background color with the light color scheme, even if it's not white. Bug: 939811, 925935 Change-Id: I19615387aeb6e1cce42de6ee8e5ed8a024fbd989 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631660Reviewed-by:
-
Jeevan Shikaram authored
This CL adds a back button to the main view of App Management which leads to the settings page and removes the referrer field when opening App Management. Bug: 958733, 966359 Change-Id: Ib579af755eb785c1415f1ad9ebc6844d3ff446bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626924 Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#664219}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: I7e819a372f523cabe9ea4ef2f69db4a0f791012c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634380Reviewed-by:
-
Stephane Zermatten authored
from server. The goal of this change is to allow configuring hardcoded client behavior that can impact execution speed and reliability from the server, so we can experiment with values and choose good ones. Bug: b/129665463 Change-Id: Iea26a703cd3c9181b372d49b4ec317dc18913e90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611687 Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#664217}
-
Arthur Hemery authored
When navigating back to a frame that has subframes, we should try to restore the subframes to their latest history item. This is currently done by OpenURL and should be done by BeginNavigation instead. Design doc: https://docs.google.com/document/d/13Rqdg1HBmtfnYMUXvg7SpUl3bJisTElfyMc1Ze8hLdE/edit# This is patch 1/2. This patch only modifies the behavior for IsPerNavigationMojoInterface off. Bug: 962518 Change-Id: I40c38663f964d3b4e0b09dcbab887d91a2faf282 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1578740 Commit-Queue: Arthur Hemery <ahemery@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
-
Eric Willigers authored
Check that border-inline-... properties match spec grammar. https://drafts.csswg.org/css-logical/#propdef-border-inline-width https://drafts.csswg.org/css-logical/#propdef-border-inline-style https://drafts.csswg.org/css-logical/#propdef-border-inline-color Shorthands border-inline, border-inline-start, border-inline-end are not yet tested. Change-Id: I60d91a47e94852512f50495c6ea5d0f153541bc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633690 Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a2dee8aa..bd353500 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: I20e995431aa5cc4859abbcc47f2a1f8014f329f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634929Reviewed-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@{#664214}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/e9944e4e052c..82c5fe1de06e Created with: gclient setdep -r src-internal@82c5fe1de06e The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=ricea@google.com,jeffreycohen@google.com,seblalancette@google.com,mkwst@google.com Change-Id: I931145d9ba3723b8e3b7bac3fad0b16c4eeef473 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634379Reviewed-by:
-
Yutaka Hirano authored
Bug: None Change-Id: I738423988eee4b5547019e6e01fb2ed2caa0d039 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627838 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#664212}
-
