- 21 Oct, 2019 40 commits
-
-
Sidney San Martín authored
Web content refreshes its desired cursor on every mouse event, but TouchEmulator did not, so the custom "grey circle" touch cursor could get lost when, say, you move your mouse out of and back into its bounds. This change make the touch emulator work like web content and refresh its cursor on every mouse event. Bug: 989006 Change-Id: If9a943b276b250363541384878cea9a2ddab117e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867090Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Commit-Queue: Sidney San Martín <sdy@chromium.org> Cr-Commit-Position: refs/heads/master@{#707837}
-
François Doray authored
This reverts commit a913d408. Reason for revert: Tentative revert to try to understand https://crbug.com/1006940. Original change's description: > [threadpool] Remove _MayBlock suffixes. > > Since the blocking and non-blocking have been merged, there is no > need to report data for blocking tasks in separate histograms. > > This CL also makes passing an |histogram_label| to the constructor > of ThreadPoolImpl optional. If no |histogram_label| is provided, no > histograms are recorded. This CL takes advantage of that to not record > histograms from TaskEnvironment. > > Bug: 1002318, 995496, 982145, 980409, 972890, 972888, 972883 > Change-Id: Ib192f80fc7a706780f0e75bed14df6b58a7db9ec > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1813780 > Auto-Submit: François Doray <fdoray@chromium.org> > Reviewed-by: Alexander Timin <altimin@chromium.org> > Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org> > Commit-Queue: Alexander Timin <altimin@chromium.org> > Commit-Queue: François Doray <fdoray@chromium.org> > Cr-Commit-Position: refs/heads/master@{#698458} TBR=fdoray@chromium.org,altimin@chromium.org,etiennep@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1002318, 995496, 982145, 980409, 972890, 972888, 972883 Change-Id: Ia94d381699e5c660e6f0b2d8d4e9ea0a50708ecc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872311Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Etienne Pierre-Doray <etiennep@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#707836}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/f11f58996811..63aaa927a3c7 Created with: gclient setdep -r src-internal@63aaa927a3c7 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: Ifda67fe7e0342c4ff9b9e899ed5e6c3c60fc7706 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871732Reviewed-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@{#707835}
-
Julian Pastarmov authored
This first change only adds the owners verbatim. This in most cases is enough but some policies refer to OWNERS file in the code tree. Since the people involved with translation are not Chromium engineers it will be beneficial to also dereference OWNERS files to their contents. BUG=1005850 TEST=grit unit tests Change-Id: I21630b74ea34af6697b90402566358191a1a717c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814693Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#707834}
-
Peter Kasting authored
Bug: 82078 Change-Id: Ia44c6badc61728a483203809df4f4d4153a42d23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871289 Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#707833}
-
Olivier Li authored
Prepare explore_sites unittests for imminent switching on of the HistoryServiceUsesTaskScheduler experiment. The feature will soon be flipped to ENABLED_BY_DEFAULT. This will make HistoryServiceBackend's task runner dispatch to the ThreadPool instead of a dedicated base::Thread. The tests need to be prepared to stay functional when that happens. This is done as the last mile of the chrome-wide effort to coalesce as much work as possible to the ThreadPool. Bug: 661143 Change-Id: I7e08e21c212c2852891d30d0db70b946d932dd4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865595Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Commit-Queue: Oliver Li <olivierli@chromium.org> Cr-Commit-Position: refs/heads/master@{#707832}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/682dabd1c153..72cc71cd70d4 git log 682dabd1c153..72cc71cd70d4 --date=short --no-merges --format='%ad %ae %s' 2019-10-21 saza@webrtc.org Harmonize APM config logging, update config ToString Created with: gclient setdep -r src/third_party/webrtc@72cc71cd70d4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=webrtc-chromium-sheriffs-robots@google.com Bug: None Change-Id: I61b10d5d2c658ef16cb5b289bdbb4dec9d7de5fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872114Reviewed-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@{#707831}
-
Xianzhu Wang authored
This reverts commit 093809a5. Reason for revert: The test has been all green since crrev.com/707576: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=compositing/video/video-poster.html Original change's description: > Disable test compositing/video/video-poster.html > > compositing/video/video-poster.html > is flaky from 10/18 on Windows, Mac and Linux. > https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyUgsSBUZsYWtlIkdjaHJvbWl1bUBibGlua193ZWJfdGVzdHNfZXhwYXJjaGl2ZUBjb21wb3NpdGluZy92aWRlby92aWRlby1wb3N0ZXIuaHRtbAw > > TBR=wangxianzhu@chromium.org > > Bug: 1015764 > Change-Id: I3701bb7ea8cdacd3324469ab779239c80c903545 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868981 > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Reviewed-by: Lan Wei <lanwei@chromium.org> > Cr-Commit-Position: refs/heads/master@{#707494} TBR=wangxianzhu@chromium.org,lanwei@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1015764 Change-Id: Ic02c83b3c8c689e580b9a9b7af7d3a9067fd715b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872454Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#707830}
-
Thomas Tangl authored
... and use bubble background for sync badge background. Bug: 995720 Change-Id: Id9f0d68eb1695c2b74fc41a6a888d9db38e413d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872213 Commit-Queue: Thomas Tangl <tangltom@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Auto-Submit: Thomas Tangl <tangltom@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#707829}
-
Mikhail Khokhlov authored
'pixels' is not a valid unit name, should use 'count' instead. Bug: 1016295 Change-Id: Ib24aef1c912b28d2ca5377490a2bc3bfb1de4b94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871875Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/master@{#707828}
-
Jan Wilken Dörrie authored
This change moves the check to conditionally disable Touch To Fill on secure origins to the renderer. Checking this in the browser is not sufficient, as it can lead to UI bugs where the renderer believes Touch To Fill is shown while it reality it is not. Bug: 1014042 Change-Id: Ie6e1ef57bad0dc3991e38f3c535836935561b569 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871512Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#707827}
-
Laís Minchillo authored
A null String shouldn't be passed to findAllAsync. This CL throws an IllegalArgumentException so developers have an easier way debugging (what would otherwise be a native crash). Also add a new test in AwContentsTest. Bug: 1014948 Change-Id: I7dd06dd4b09b3024c3f72ecbe3f227fec496fa25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865172Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Laís Minchillo <laisminchillo@chromium.org> Auto-Submit: Laís Minchillo <laisminchillo@chromium.org> Cr-Commit-Position: refs/heads/master@{#707826}
-
Ella Ge authored
Flaky on Linux and Mac dbg bot TBR=alph@chromium.org No-Try: true Bug: 1016364 Change-Id: Id9f45fa49309ed5e5838799867f1211dc0e6f833 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872451Reviewed-by:
Ella Ge <eirage@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#707825}
-
Thomas Tangl authored
Bug: 995720 Change-Id: I9616c6c0e270059fb220df87b5d60936e69f8a34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864663 Commit-Queue: Thomas Tangl <tangltom@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#707824}
-
Yuki Shiino authored
Bug: 839389 Change-Id: Id18d8b2048d757ac0c27f68726d3d4ebee9f02f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872072 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#707823}
-
Francois Doray authored
This is a reland of 9d6a01ba We now handle negative values returned from ::GetThreadPriority(). https://chromium-review.googlesource.com/c/chromium/src/+/1829570 Original change's description: > Add field trial testing config for BoostThreadPriorityOnLibraryLoadingAndBackgroundMode. > > This experiment enables: > - Use THREAD_MODE_BACKGROUND_BEGIN/END to set the priority of > background threads. This affects memory and IO priority in addition > to CPU priority. > - Increase thread priority to "normal" in scopes where background > threads load modules. > > The expectation is that this will improve responsiveness of Chrome > (input delay, first contentful paint), without regressing jank. > > We are adding the testing config in preparation for enabling this > via Finch in M79. > > Bug: 973868 > Change-Id: I467cae12503e3ad724b665f3aebdaeb94e1325c9 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1835023 > Commit-Queue: Robert Kaplow <rkaplow@chromium.org> > Reviewed-by: Robert Kaplow <rkaplow@chromium.org> > Auto-Submit: François Doray <fdoray@chromium.org> > Cr-Commit-Position: refs/heads/master@{#705960} TBR=rkaplow@chromium.org Bug: 973868 Change-Id: I392cfb2f92e2ac0fa888fa1e323557ab35055b48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872312Reviewed-by:
-
Kevin Ellis authored
This reverts commit af74d157. Reason for revert: pref regression in queuing durations Original change's description: > Web-animation: Remove some uses of PlayStateUpdateScope. > > PlayStateUpdateScope is problematic for handling timing of finished > promises in addition to not conforming with the algorithm outlined in > the web-animations spec. This patch removes several uses of > PlayStateUpdateScope and refines handling of pending flags. > > Bug: 960944 > Change-Id: I093a3aa86084adfbe128a5aedd36206d67dd12c8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851927 > Commit-Queue: Kevin Ellis <kevers@chromium.org> > Reviewed-by: Stephen McGruer <smcgruer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#705966} TBR=kevers@chromium.org,majidvp@chromium.org,smcgruer@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 960944 Change-Id: Ib16d862d5834f837717e64bb86277860e50ec11a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866624Reviewed-by:
Kevin Ellis <kevers@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#707821}
-
Martin Robinson authored
The introduction of text-change signals for the omnibox included a regression that prevented the emission of AtkValue property change signals. Fix this error and also add an implementation of atk_value_set_value. The implementation is used in a test to verify the correct behavior. The fix is that we correct the misuse of a logical operator and now always try to emit AtkValue property change events when receiving the kValueChanged event in AXPlatformNodeAuraLinux. Bug: 1015387 Change-Id: I18baa44a52190913ff70708bd5133bdcdea83b9e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871692 Auto-Submit: Martin Robinson <mrobinson@igalia.com> Reviewed-by:
Joanmarie Diggs <jdiggs@igalia.com> Commit-Queue: Martin Robinson <mrobinson@igalia.com> Cr-Commit-Position: refs/heads/master@{#707820}
-
Sergey Poromov authored
DeviceStatusCollector is used only for enterprise reporting, consumer (child) reporting is extracted to ChildStatusCollector, so it's safe to remove this flag for simplicity and ensure that DeviceStatusCollector is initialized only for enterprise reporting. Test: Run trybots. Change-Id: Ib64ca56c3e402b6c99ededc856a96674a2e025c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864992Reviewed-by:
Aga Wronska <agawronska@chromium.org> Commit-Queue: Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#707819}
-
Raymond Toy authored
The values of an AudioParam are supposed to be clamped to the nominal range. We do this already, but we forgot the case where there is a connection to the AudioParam. This can cause the values to go outside the nominal range and cause issues for the nodes that expected the values to be clamped appropriately. Manually tested ASAN build with this CL and crashes don't happen anymore. Without this, the crash was very reliable. Bug: 1015737, 1016165 Change-Id: Ia02bac7b60a7e20bdc5165dbfbb17df56d4d3171 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869373 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by:
Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#707818}
-
Benjamin Beaudry authored
When calling AXPosition::ToPositionWithAffinity() on a position with a |container_object_| of type AXInlineTextBox, the position returned is always in the parent node, the StaticText object. Think of it as a modification from a relative position to an absolute position, based in the StaticText object. However, when an InlineTextBox object has siblings (i.e. the parent node has multiple InlineTextBox children), the position returned is only valid for the first non-empty child. This bug was due to the fact that we wrongfully assumed that the text offset in the child object would be the same as the text offset in the parent position. This is only true for the first non-empty child. This CL introduces a fix for this bug. Instead of creating a position in the parent node at the exact same offset, we add to it the sum of the previous siblings MaxTextOffset(). It also adds a unit test for this case. Bug: 928948 Change-Id: I1b52c7506e726956bca8b2d41d5a33bee3a84597 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846563Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Benjamin Beaudry <benjamin.beaudry@microsoft.com> Cr-Commit-Position: refs/heads/master@{#707817}
-
Yuki Shiino authored
clang-format takes care of formatting, but it's still newline- sensitive. So, make CodeNode family generate/remove appropriate newlines. Also renames |cond_node| and |body_node| simplifying to |cond| and |body|. Bug: 839389 Change-Id: Ic339fcc906ef3d9c5b26c29ebfac17291651d608 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871713Reviewed-by:
-
Ben Mason authored
TBR=agrieve TBR_REASON=Breaking translation script Change-Id: I1e7bdbf4d4bfdba6446ed9596415bdcfb7a1ce06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872117 Commit-Queue: Ben Mason <benmason@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#707815}
-
Juan Antonio Navarro Perez authored
Replace instead with a simpler csv based implementation. Bug: 981605 Change-Id: I901601136a43833b8c83ef2f77117e4ba22014cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869417 Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by:
Christopher Grant <cjgrant@chromium.org> Reviewed-by:
Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#707814}
-
Francois Doray authored
As documented at https://cs.chromium.org/chromium/src/components/performance_manager/graph/frame_node_impl.h?l=215&rcl=2b413514ddc9679893b20235eb2cecbbca4d8245, lifecycle state of a frame/page is updated independently from navigations. There is no need to filter out updates generated prior to the last navigation. Bug: 857472 Change-Id: Ifd64c437349ed218847a6ca4486b8cd0248fb375 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869473 Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org> Auto-Submit: François Doray <fdoray@chromium.org> Reviewed-by:
Sigurður Ásgeirsson <siggi@chromium.org> Cr-Commit-Position: refs/heads/master@{#707813}
-
Ella Ge authored
TBR=rsorokin@chromium.org No-Try: true Bug: 1015948 Change-Id: I971b24ba40310d9c368e26127a275e2677d51e81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872150Reviewed-by:
-
Miyoung Shin authored
This CL converts Camera3DeviceOps{Ptr, Request} in media to the new Mojo type, and uses pending_receiver<Camera3DeviceOps> in camera_common.mojom. Bug: 955171 Change-Id: I8c751cf880c39e80e00cab5055e96c583bf908ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862443 Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Reviewed-by:Sam McNally <sammc@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Tommi <tommi@chromium.org> Cr-Commit-Position: refs/heads/master@{#707811}
-
Olivier Li authored
Create a function to allow clients of TestingProfile to wait on the destruction of its HistoryBackend. The HistoryServiceUsesTaskScheduler feature will soon be flipped to ENABLED_BY_DEFAULT. This will make HistoryServiceBackend's task runner dispatch to the ThreadPool instead of a dedicated base::Thread. Tests using TestingProfile need to be prepared to stay functional when that happens. This is done as the last mile of the chrome-wide effort to coalesce as much work as possible to the ThreadPool. Bug: 661143 Change-Id: Iddb851d00ea64693f669bcb656829abcb2303b10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868913Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Oliver Li <olivierli@chromium.org> Cr-Commit-Position: refs/heads/master@{#707810}
-
François Doray authored
This reverts commit fe93195d. Reason for revert: This is a spurious failure caused by an unrelated issue https://crbug.com/1012445. Individual test should not be disabled because of this (a lot of tests are affected -- it wouldn't make sense to disable all these tests because of a single problem). Original change's description: > Disable flaky PerformanceManagerTabHelperTest.PageIsAudible > > TBR=fdoray > > Bug: 1012601 > Change-Id: I9540e12715b4b431af0b886c280f609b51851b10 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852429 > Reviewed-by: David Roger <droger@chromium.org> > Commit-Queue: David Roger <droger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#704622} TBR=droger@chromium.org,fdoray@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1012601 Change-Id: Icb00d26109eac1d532740b992acba94255c023a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872310Reviewed-by:
-
Vladislav Kaznacheev authored
Currently many tests check for kShelfScrollable and return early. This causes missing regressions (such as crbug.com/1015688). This CL removes early returns at the start of test methods and instead force-disables force-disable kShelfScrollable (and also kShelfHotseat which triggers kShelfScrollable) for these methods. This ensures that these methods will be run even when kShelfScrollable and/or kShelfHotseat are enabled by default. A few tests remain that have a flag check in the middle of the test, those are left unchanged. Replacing those will require extra work. Bug: 1015891 Test: ash_unittests --enable-features=kShelfScrollable Test: ash_unittests --disable-features=kShelfScrollable Change-Id: Ic7a0987fbc4ffb8b68e262deb5830e832461583c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868984Reviewed-by:
Manu Cornet <manucornet@chromium.org> Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org> Cr-Commit-Position: refs/heads/master@{#707808}
-
Torne (Richard Coles) authored
Move ResourcesContextWrapperFactory to the embedder_support component so that weblayer can share it. In the process, rename it to ClassLoaderContextWrapperFactory, which better reflects what it actually does: it has little to do with resources (which are always just delegated directly to the context it is wrapping), and the primary thing it overrides is getClassLoader(). Downstream code still refers to the old class, so leave a forwarding version in place for now. Change-Id: I3c22c390012289d7c91aeb6986f1bf44fd34dda1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867230 Auto-Submit: Richard Coles <torne@chromium.org> Reviewed-by:
Tobias Sargeant <tobiasjs@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#707807}
-
Himanshu Jaju authored
SyncMode is not available when GetDeviceName is called. So we have to manually update the device name and merge it with sync data. Bug: 1009454 Change-Id: Icf0760eabf41171b9d7f222b620b0c41bc32bc59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866651 Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Reviewed-by:
Alex Chau <alexchau@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#707806}
-
Yann Dago authored
Bug: 818872 Change-Id: I92a988afdae4862772717a4251f20e05d645bdc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868912 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#707805}
-
Javier Ernesto Flores Robles authored
Increased the section header. Decreased the section footer. Increased the space between title and top of the cells. Bug: 949060 Change-Id: I48501c665d7ff77388171bb0ac7bbf43ae23b976 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865328 Auto-Submit: Javier Ernesto Flores Robles <javierrobles@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#707804}
-
Maksim Moskvitin authored
This CL adds recording for some missed histograms: CustomPassphraseKeyDerivationMethodStateOnStartup CustomPassphraseKeyDerivationMethodOnNewPassphrase CustomPassphraseKeyDerivationMethodOnSuccessfulDecryption Bug: 922900 Change-Id: I9e05b771a22c3480413d32788a2a59bd320bfa1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871549 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
Marc Treib authored
Bug: 1004205 Change-Id: Ib5759c9c112cff7915eef128a21b12b89de30d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871593Reviewed-by:
-
Maksim Moskvitin authored
The test was disabled (crrev.com/c/1849426) because it instantiates FeatureLists after the browser threads have been created. It was needed to inject NigoriSpecifics with scrypt key derivation method, while test assumes that scrypt is disabled. The fix is just initialization of NigoriSpecifics in test fixture constructor, where it's safe to override features. The test also used to inject an encrypted bookmark to the server, but this part wasn't exercised further in test, so this CL just drop it. Bug: 1013073 Change-Id: I8d2947484a0192cf99fd2b84e44325ea1d6220fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872190 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
Maksim Moskvitin authored
crrev.com/c/1787610 removed cryptographer checks in custom passphrase unittests, because used KeyDerivationMethod became an implementation detail. This CL restore those checks by bridge providing custom passphrase key derivation params through getter. Bug: 922900 Change-Id: I31abbf54e162c779cea50020231aed85e2e1a9d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869221 Auto-Submit: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
Maksim Moskvitin authored
Exposing last keystore key name allows the following: 1. Avoiding unnecessary copies of underlying CryptographerImpl in NigoriState::NeedsKeystoreKeyRotation(). 2. Removing ComputePbkdf2KeyName() from nigori_state.cc 3. Exposing HasKey(key_name) instead of HasKey(key_proto) from CryptographerImpl. This CL also adds unittests for KeystoreKeysCryptographer. Bug: 922900 Change-Id: If7004c658adeae2bd03d77f08b39fa63dd278b6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868873 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
Yang Guo authored
https://chromium.googlesource.com/devtools/devtools-frontend/+log/4fd355cc40..032591d692 TBR=bmeurer@chromium.org Change-Id: I8492a0fcfc98580b74b1874ee0abd6cdb3f1d2f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871997Reviewed-by:
-
