- 17 May, 2019 40 commits
-
-
Vladimir Levin authored
This patch adds size containment implementation for fieldsets in LayoutNG. Tested with LayoutNGFieldset feature flag. Along with the new tests, external/wpt/css/css-contain/contain-size-fieldset-001.html and external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/contain/contain-size-fieldset-001.html are also passing. R=chrishtr@chromium.org, ikilpatrick@chromium.org, mstensho@chromium.org Bug: 958975 Change-Id: I5e735adc65ed9450f84e4c1ab68cba69e3fd85ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613844Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#660866}
-
Sadrul Habib Chowdhury authored
All GLSurfaces now support presentation-callbacks. So remove GLSurface::SupportsPresentationCallback(). TBR=boliu@ for API updates in android_webview/ BUG=883592 Change-Id: I05cecb9c90a0a412615a251936f011e277b31c6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617542 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#660865}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/867bf9d35a9f..23e25e0bb4dc git log 867bf9d35a9f..23e25e0bb4dc --date=short --no-merges --format='%ad %ae %s' 2019-05-17 evanhernandez@chromium.org tree_status: Nuke. Created with: gclient setdep -r src/third_party/chromite@23e25e0bb4dc The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Change-Id: Ic3fc0f918590ca7d35a1c8834ff5ef5c6cb27732 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617130Reviewed-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@{#660864}
-
Jun Mukai authored
Bug: 958467 Test: trybot Change-Id: I8a85cdeb51412becc9353123a109f50c74d11950 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615711Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Jun Mukai <mukai@chromium.org> Cr-Commit-Position: refs/heads/master@{#660863}
-
Jun Mukai authored
Bug: 958467 Test: trybot Change-Id: I163739c1acb5377a6ed19643287a6cd01b3d0ff3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614704Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Jun Mukai <mukai@chromium.org> Cr-Commit-Position: refs/heads/master@{#660862}
-
Andrew Grieve authored
This reverts MinidumpUploadCallable.java in 398ed50f. Reason for revert: Breaking crash uploads Original change's description: > Android: Add FileUtils.copyStream() and FileUtils.readStream() > > And also make use of existing FileUtils functions in a couple > spots. This is mostly a no-behavior-change clean-up. > > Behavior changes: > * Also removes a useless Trace event from ResourceExtractor. > * FileUtils.recursivelyDeleteFile() now succeeds if the file > didn't exist to start with and has a return value. > * MinidumpUploadCallable now makes an extra copy of the response > data (choosing code simplicity of performance for crash logic). > > Change-Id: I367d385e397f48d40ff0a7f9a01e2d661a7def64 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604187 > Commit-Queue: Andrew Grieve <agrieve@chromium.org> > Reviewed-by: Ted Choc <tedchoc@chromium.org> > Reviewed-by: Richard Coles <torne@chromium.org> > Cr-Commit-Position: refs/heads/master@{#659827} TBR=torne@chromium.org,tedchoc@chromium.org,agrieve@chromium.org Bug: 964334 Change-Id: I73a23d193f093d6afaef1c8abed4b8904e2b5b52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617549 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#660861}
-
Johannes Henkel authored
New Revision: 0aafd2876f7485db7b07c513c0457b7cbbbe3304 https://chromium.googlesource.com/deps/inspector_protocol/+/0aafd2876f7485db7b07c513c0457b7cbbbe3304 Change-Id: Ib7597e9edb2d665ef13cffe0d055f7a968a56f17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616521Reviewed-by:
Alexei Filippov <alph@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#660860}
-
Avi Drissman authored
The new bundle structure moves the Chromium Framework into a top-level Frameworks directory (see https://crbug.com/958976). This requires new app shim code to locate the Chromium Framework when launching. App shims function by doing a dlopen on the Chromium Framework and jumping into an entrypoint. While this change alters how that framework is found, it does not change the functionality of that launch. Because the value of kCurrentAppShortcutsVersion is incremented, the AppShortcutManager will automatically rebuild all existing app shortcuts. Therefore, no merge is strictly required, as the first launch of Chromium will cause all existing app shims to be rebuilt. However, because there is a window during which a launch of an old shim will fail (from the update of Chromium to a version with the new bundle structure to the first launch of that Chromium) it might be worth a merge to have the shims rebuilt in preparation. BUG=960886 Change-Id: Ia6f6914c9d6685e15323cae0905bccce8dcbee4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607604 Commit-Queue: Avi Drissman <avi@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#660859}
-
Matt Menke authored
iOS doesn't seem to be using URLFetcher to fetch account information, so remove iOS code to mock out URLFetcher responses. Bug: None Change-Id: I703d71c11decf168541c1181b7836000ef80d129 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611868 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#660858}
-
Mohamed Heikal authored
If in reduced mode, we cannot create PrefetchGCMAppHandler. Instead we pass the prefetch service a closure to create the gcm app handler on demand. This cl also changes the signature of the getter for PrefetchGCMHandler in PrefetchService to require a profile to be passed in. This ensures that: 1) the getter can only be called in full browser mode (there is no profile in reduced mode). 2) if PrefetchGCMHandler hadn't been created yet, then it can be created on demand using the aforementioned profile. > This is a reland, Original CL: > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1495737 This reverts commit a59ecdc7. Reason for reland: Fixed CQ tests being slow by mocking out InstanceIDAndroid during tests. This reland also moves away from deprecated call to PostAfterStartupTask. Bug: 934337, 963688 Change-Id: I8d57b1f96f0b6152ba3271a9a7ef7e023f5f6988 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613672 Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Cr-Commit-Position: refs/heads/master@{#660857}
-
Ryan Hansberry authored
This method was only defined and used within the impl class, EasyUnlockServiceRegular. This change also improves the documentation around this method and the similar GetRemoteDevices. Bug: 959016 Change-Id: Idf849b79a1a249def3f375ae7384b19e6b4e61ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594067 Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#660856}
-
chrome://webrtc-internalsHenrik Boström authored
Adds these calculated graphs: - [targetEncodedBytes/s]: Multiplies the average target bytes per frame (=delta totalEncodedBytesTarget/delta framesEncoded) by the average encode frame rate (=delta framesEncoded/delta timestamp) to estimate what bytesSent/s should be if the target was achieved. This graph can be compared with the actual bytesSent/s to see if the encoder over- or undershoots its target. - [totalEncodeTime/framesEncoded_in_ms]: The average encode time per frame, in milliseconds. Bug: webrtc:10446 Change-Id: I14c0fc7736fd6b48f073e3e4b6217de5afd3f049 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615742Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#660855}
-
Tanya Gupta authored
This CL is one of many to come. It covers: * Creation of the infobar from the SendTabToSelfInfoBarController * Plumbed the call to create the infobar to the native code. * Open the link when user taps on the link In follow-up CLs, the following will be done: * Instantiate the InfobarController in the ChromeActivity * Listen for Model changes in the Controller Bug: 949233,963193 Change-Id: I5df1359debb5f0f35c32c2df3b691bf9129cdeb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604406Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Reviewed-by:
Jeffrey Cohen <jeffreycohen@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Tanya Gupta <tgupta@chromium.org> Cr-Commit-Position: refs/heads/master@{#660854}
-
Maksim Moskvitin authored
Explicit passphrase means either CUSTOM_PASSPHRASE or FROZEN_IMPLICIT_PASSPHRASE passphrase types. This CL contains logic required for MergeSyncData()/ApplySyncChanges() methods to work with explicit passphrase types. It includes validation of received NigoriSpecifics and support for following fields: - passphrase_type - custom_passphrase_time - keystore_migration_time (used instead of custom_passphrase_time if passphrase type is FROZEN_IMPLICIT_PASSPHRASE) - encrypt_everything Note: currently there is no way to set custom passphrase or to decrypt the data encrypted with explicit passphrase in USS implementation of Nigori. We only update local state and notify observers about encryption state changes. Bug: 922900 Change-Id: Ib27169259772f0528d765c10de9a40a5ebd9f235 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613059 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
chrome://webrtc-internalsHenrik Boström authored
When https://webrtc-review.googlesource.com/c/src/+/137044/ lands, this will show the packet average send-side delay over the last second as a graph in chrome://webrtc-internals. Verified manually. Bug: webrtc:10506 Change-Id: Icade78b31ed37509e8769b6b9b9c4b89447c619a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615144Reviewed-by:
-
Elly Fong-Jones authored
This change removes the flag only; the backing feature is still present because it is being used for some experimentation (or will be in future). Bug: None Change-Id: I9f083ea5beac6086cd881653c4d444fc24f1412c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617627 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
-
Takuto Ikuta authored
Now this is the same with linux-rel and corresponding CI builder/tester. I will remove recipes later. Bug: 964197 Change-Id: I58e82885d341d4447523da33e5fa3450906438e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616706 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#660850}
-
Kevin McNee authored
This was recently re-enabled as one source of flakiness was fixed, but this test is still flaky for another reason; it seg faults in chromeos::UserSessionManager::InitializeBrowser. We disable this test again. Tbr: alemate@chromium.org Bug: 961607, 964333 Change-Id: I3bc48798afabfbe004173b5faf9ad810be5bdff7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617377Reviewed-by:
Kevin McNee <mcnee@chromium.org> Commit-Queue: Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#660849}
-
Jordan Demeulenaere authored
This is a reland of 3618cb02 Original change's description: > Autofill Assistant dependencies are now deps instead of classpath_deps. > > Bug: 951489 > Change-Id: I6959c83313aef83976910a56e7c198bcb98d50ea > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613077 > Commit-Queue: Jordan Demeulenaere <jdemeulenaere@chromium.org> > Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> > Auto-Submit: Jordan Demeulenaere <jdemeulenaere@chromium.org> > Cr-Commit-Position: refs/heads/master@{#660769} Bug: 951489 Change-Id: I0003f33665041536a96318825f794b4e73ab3ab9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617356Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Jordan Demeulenaere <jdemeulenaere@chromium.org> Cr-Commit-Position: refs/heads/master@{#660848}
-
David Roger authored
On some platforms (windows in particular), the installer may create a preference file in the profile directory, before the profile is created. This happens in first_run::ProcessMasterPreferences(). In this case, when the profile is created, the preference file is found and the profile is assumed to not be new. As a result, all the code that is intended to be called for new profiles is bypassed, which leaves the profile in a bad state. Bug: 728402, 959188, 145351 Change-Id: Ibfeeebbb72893cc48095ce810d8300718dc24e6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614207Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#660847}
-
Xianzhu Wang authored
Bug: 963782 Change-Id: I8c6faf984321c38765357bf613bdb27a71c282bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616445Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#660846}
-
Rohit Rao authored
This defaults to NSObject, but can be set to a class that implements the XCTestObservation protocol to perform one-time setup in XCTest bundles. BUG=None Change-Id: I3ff7abbf928a16ce6626fc99ed8fd747902cc791 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617623Reviewed-by:
Justin Cohen <justincohen@chromium.org> Commit-Queue: Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#660845}
-
Tim Volodine authored
Add UMA to record invocation counts for some network related callbacks: - onReceivedLoginRequest - onReceivedClientCertRequest - onReceivedHttpAuthRequest - onDownloadStart These are non-error callbacks, so there is no need to have separate histograms with error code distributions. BUG=841556,951885,945922 Change-Id: I88be3ca2dfd831b83099bdbf44ece885b9acad18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609708 Commit-Queue: Tim Volodine <timvolodine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Tobias Sargeant <tobiasjs@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#660844}
-
Moe Ahmadi authored
Add language page allows the user to select a supported language to add to the list of user preferred languages. Existing accepts languages are excluded from the available options. screenshot: https://drive.google.com/file/d/1gV24hPwP1Gpiw_whOW45GQGmfJn_byEi/view?usp=sharing Bug: 957688 Change-Id: I63b261061cc867a1c7d5cd2373cb948eec1581f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611911Reviewed-by:
Peter Lee <pkl@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#660843}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/18ebb45055a5..0559bc475569 git log 18ebb45055a5..0559bc475569 --date=short --no-merges --format='%ad %ae %s' 2019-05-17 chrisforbes@google.com Check for rest of interactions between usage bits and format features Created with: gclient setdep -r src/third_party/swiftshader@0559bc475569 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:b/117974925 TBR=swiftshader-team+autoroll@google.com Change-Id: I6caf11421be26ab4311fc7ebe1a9cecbc92a4d44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617376Reviewed-by:
-
Mounir Lamouri authored
This is a reland of 15c84b57 Original change's description: > Media Engagement: only use/record for HTTPS origins. > > Bug: 958364 > Change-Id: Ifc87e6222df9de526f2900f13899af616604750e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1591878 > Reviewed-by: Becca Hughes <beccahughes@chromium.org> > Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> > Cr-Commit-Position: refs/heads/master@{#659971} Bug: 958364 Change-Id: I2e1c9741946797875fca63524260ad5d066f74cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614442 Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#660841}
-
Tommy Martino authored
TBR=ellyjones@chromium.org Change-Id: Ide1f29008cd3840ec13c2252a279a76a4f5efdec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617628 Commit-Queue: Tommy Martino <tmartino@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Tommy Martino <tmartino@chromium.org> Cr-Commit-Position: refs/heads/master@{#660840}
-
Jan Wilken Dörrie authored
This change moves Lambda capture expressions in the Allowed C++14 Features section and details their usage guidelines. Bug: NONE Change-Id: I2e1b117512ee3262f50d63c379b6d31506cfcd33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617506 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#660839}
-
Justin Cohen authored
Bug: 964323 TBR: mattm@ Change-Id: Ibd0f85b0317804869b4dbc8eee3527fd7ae89359 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617626Reviewed-by:
-
kylechar authored
There is still flake in webgl2_conformance_gl_passthrough_tests on Windows Intel GPU FYI bots. Use a bigger hammer and mark all of deqp/functional/gles3/textureshadow/cube_* flaky. Bug: 963450 Change-Id: I0c1e305e591b6acbcc3768418dcad799c3f4eb99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617065Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#660837}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/0c6daf034b11..e5b3e400b6e9 git log 0c6daf034b11..e5b3e400b6e9 --date=short --no-merges --format='%ad %ae %s' 2019-05-17 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 8c742b26..5ca9f956 (448 commits) 2019-05-17 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 6ddb7768fa25..06de90c66c18 (9 commits) Created with: gclient setdep -r src/third_party/skia@e5b3e400b6e9 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=michaelludwig@google.com Change-Id: I7d49392fc0c917b1765667500351271338a7059e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617375Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/c9178292..92b8322b 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: Iac0d4b87103b6c56b70aad5f27f8a66405e62130 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617067Reviewed-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@{#660835}
-
W. James MacLean authored
This refactor moves the logic in RenderWidget::PageScaleFactorChanged() to RenderWidget::SetPageScaleStateAndLimits(). This removes the need for RenderViewImpl::PageScaleFactorChanged() to call GetWidget(). This is a re-land of https://chromium-review.googlesource.com/c/chromium/src/+/1614080. TBR=dcheng@chromium.org TBR=collinbaker@chromium.org Bug: 924336 Change-Id: Id076ddc805c62069984181914f3722d4d081a3b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617064Reviewed-by:
James MacLean <wjmaclean@chromium.org> Commit-Queue: James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#660834}
-
Justin Cohen authored
Change-Id: I399626094a700d9b8a581591c6080da8277d584f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611107Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
-
John Budorick authored
Follow-up to crrev.com/c/1496656 Bug: 961811 Change-Id: Id7a5e4d09e4ca966e75bcecc6f007e26553d534d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611118Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/4274cc4631b0..cafd7736490e git log 4274cc4631b0..cafd7736490e --date=short --no-merges --format='%ad %ae %s' 2019-05-17 jmadill@chromium.org Fix KHR-GLES dEQP test paths. Created with: gclient setdep -r src/third_party/angle@cafd7736490e The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=syoussefi@google.com Change-Id: Ic13ed7c964a29e4227ad1241d45a709f0740314e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617268Reviewed-by:
-
Henrique Grandinetti authored
Bug: 964296 Change-Id: Ib458bbccb2fe10939a0ec43ad315f0fd6b22c134 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617323Reviewed-by:
Tatiana Gornak <melandory@chromium.org> Commit-Queue: Henrique Grandinetti <hgrandinetti@chromium.org> Cr-Commit-Position: refs/heads/master@{#660830}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/6ffd8ec5ef77..c05031d35df8 Created with: gclient setdep -r src-internal@c05031d35df8 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=beverloo@google.com,collinbaker@google.com,bcwhite@google.com,tasak@google.com Change-Id: I73fc2f1438d25e425125ffe03150141ae621c63f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617262Reviewed-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@{#660829}
-
A Olsen authored
Going through the SAML in-session password change flow will: a) Dismiss any existing notification that your password is expiring b) Delete the expiration time stored for your SAML password, so you will not receive any further notifications - until and unless you go through the SAML login flow again at some point and we receive an updated expiry time for your new password. Bug: 930109 Change-Id: I8561cf3425cc74ef3aa3d50a9ac604521f9fbfbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617357Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: A Olsen <olsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#660828}
-
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: I17c3e6872255d4282816036e1b877250b27dfecd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617386Reviewed-by:
-
