- 02 Aug, 2019 40 commits
-
-
Nate Fischer authored
WebView needs to add variations-specific headers to the CORS-exempt headers list, otherwise we may trigger excessive CORS preflight checks. Bug: 990072 Test: Enable "OutOfBlinkCors", WebView still seems to work Change-Id: I9ad69dd52fc53bbbce01a33724050322b642a70a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731555 Commit-Queue: Nate Fischer <ntfschr@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#683677}
-
Carlos Caballero authored
MessageLoopForIO is going away soon. Use SingleThreadTaskExecutor instead. This CL was uploaded by git cl split. R=lambroslambrou@chromium.org Bug: 891670 Change-Id: Id1c49577b98d4adc705d1eec6a164382fb5aba77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731848 Auto-Submit: Carlos Caballero <carlscab@google.com> Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org> Reviewed-by:
Lambros Lambrou <lambroslambrou@chromium.org> Cr-Commit-Position: refs/heads/master@{#683676}
-
Findit authored
This reverts commit 76c1237a. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 683650 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzc2YzEyMzdhYTBmY2RkZDA1MzZmZTE5OWQzMTBlNjVjM2JiOGY0M2EM Sample Failed Build: https://ci.chromium.org/buildbot/chromium/win-archive-rel/3564 Sample Failed Step: compile Original change's description: > Remove "chrome" and "chrome_renderer" services > > This eliminates the existence of the "chrome" and "chrome_renderer" > services as well as general support for embedder-provided process-wide > browser and renderer Service Manager services. > > Remanining browser<->renderer interfaces which used these services have > been migrated to use direct receiver binding via > content.mojom.ChildProcess or content.mojom.ChildProcessHost messages. > > Change-Id: I74f012aafe77fdcbbba8d93d193d3ded8d63d445 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729968 > Reviewed-by: Luke Halliwell <halliwell@chromium.org> > Reviewed-by: Bo <boliu@chromium.org> > Reviewed-by: Tom Sepez <tsepez@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: Ken Rockot <rockot@google.com> > Cr-Commit-Position: refs/heads/master@{#683650} Change-Id: I797753e6cb96874ca92a245bcb493b669689a981 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733026 Cr-Commit-Position: refs/heads/master@{#683675}
-
Sophie Chang authored
This is moving here as this top host provider is what is approved for users with Lite Mode enabled rather than just Previews enabled. It may be confusing to consumers if this was still tied to Previews anyway. Bug: 969558 Change-Id: I698638a3583744f9fb4dd8d5ef4cc1eae2b0554f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731451 Commit-Queue: Sophie Chang <sophiechang@chromium.org> Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Cr-Commit-Position: refs/heads/master@{#683674}
-
Peter Kotwicz authored
The following UMA metrics are removed: Webapp.Splashscreen.Icon.Size Webapp.Splashscreen.Icon.Type Webapp.Splashscreen.BackgroundColor Webapp.Splashscreen.Duration Webapp.Splashscreen.ThemeColor This CL extends the expiry of: Webapp.Splashscreen.Hides R=hartmanng@, dominickn@, rkaplow@ TBR=yfriedman@ for WebappSplashUmaCache.java BUG=975052 Change-Id: Id6b7ae9e7d7e05170bd0474a9da8f239783afeab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716136 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Glenn Hartmann <hartmanng@chromium.org> Cr-Commit-Position: refs/heads/master@{#683673}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/31899ec2ac04..4af1fe027b83 git log 31899ec2ac04..4af1fe027b83 --date=short --no-merges --format='%ad %ae %s' 2019-08-02 tomhughes@chromium.org docs: Copy dev server docs from Chromium sites Created with: gclient setdep -r src/third_party/chromite@4af1fe027b83 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 Bug: None Change-Id: I3104dc15ca1ff799a7fab5a958c222daa767328a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733569Reviewed-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@{#683672}
-
Dan Beam authored
R=pkotwicz@chromium.org BUG=953962 Change-Id: Id13ea7145bc302da3ff427098648517be48b2964 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730258Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Commit-Queue: Dan Beam <dbeam@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#683671}
-
Philip Rogers authored
Non-fast scrollable regions are regions on a cc::Layer where the compositor should not handle scroll events. These are primarily for non- composited scrollers but are also used for resize handles and plugins. This patch paints non-fast scrollable regions for resize handles. The interesting code change is in ScrollableAreaPainter::PaintResizer where we now emit a ScrollHitTestDisplayItem for resizers. This fixes a class of bugs such as non-fast regions being on the wrong cc::Layer (https://crbug.com/968691) and having the wrong offset (https://crbug.com/989038). Design doc: https://docs.google.com/document/d/1IyYJ6bVF7KZq96b_s5NrAzGtVoBXn_LQnya9y4yT3iw/view#heading=h.rrlzkp4v3huj Bug: 864567, 968691, 989038 Change-Id: I8193077279617418433306912d712c31d99149f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730521Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#683670}
-
Ahmed Mehfooz authored
We do not need any bottom inset for the separate message center bubble. Also, need to clip scroller height based on clear all button visibility. Bug: 958020 Change-Id: Ie4f0966f2de97f841cf975fcc7810c82761b2de2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730091 Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org> Reviewed-by:
Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#683669}
-
Tomasz Śniatowski authored
Make the metadata machinery on Android use output_extension in shared_library and similar targets if it is set, so the gathered metadata matches the actual names of built binaries. GN shared_library targets can set a custom 'output_extension' (for example, to explicitly always have a .so extension and never .cr.so) and the Android metadata machinery should work with that. Test: set output_extension on a solib and build Android Bug: 980569 Change-Id: I12fb2b31e753adf81bac86c07e10aa913de51969 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730155 Auto-Submit: Tomasz Śniatowski <tsniatowski@vewd.com> Commit-Queue: Tomasz Śniatowski <tsniatowski@vewd.com> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#683668}
-
Michael Thiessen authored
Fixes handling of intent URLs in touchless mode. window.open('intent://...'); should now fire the BROWSABLE intent as expected. We do this by special casing the 'new window opens in CCT' logic to ignore intent:// schemes, and handle the resulting New Tab View Intent with the ExternalNavigationHandler. Bug: 983699 Change-Id: Ic28930db53686ae46c55496554e7388d12aa937c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733458Reviewed-by:Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#683667}
-
Robbie McElrath authored
This moves Feature set up in SSLErrorHandlerDateInvalidTest to the constructor rather than the SetUp method to make sure it gets set before things start checking for Features. Bug: 989225 Change-Id: If4b781ee37534bb8100a781aa99cecab8ad7f06d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732151Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Cr-Commit-Position: refs/heads/master@{#683666}
-
Richard Knoll authored
While we check the native notification platform bridge for the currently shown notifications, new ones might be added to the database. This will ignore all entries that are added after we started querying the OS. Bug: 988376 Change-Id: I5931a50fc5756987e095a19dbaed62045997f8ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732100Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#683665}
-
Wez authored
Tests use //ui/aura/test/test_screen.cc, which under Fuchsia calls InitializeViewTokenAndPresentView(), which creates a token and invokes fuchsia.ui.policy.Presenter.Present(). This may cause the presenter service to be started, if not already running, which may lead to crashes or logspam. Bug: DX-1801 Change-Id: I65f1ff5e86557d236de8df58cea351b265627a4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729514 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Auto-Submit: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#683664}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/01915c0dd073..149f3f197897 git log 01915c0dd073..149f3f197897 --date=short --no-merges --format='%ad %ae %s' 2019-08-02 halcanary@google.com tools/sk_app: fWindowContext is unique_ptr<> 2019-08-02 mtklein@google.com add vbroadcastss(Ymm, GP64, int) 2019-08-02 halcanary@google.com sk_app, editor: cursor blink Created with: gclient setdep -r src/third_party/skia@149f3f197897 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=benjaminwagner@google.com Bug: None Change-Id: I5a590d56efea8d18df082ffc10083240670d0968 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733474Reviewed-by:
-
Evan Stade authored
Bug: 268984 Change-Id: Ie41cb913d29ad690b9364d9c478c7a3c4771f607 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730591Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#683662}
-
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: I45dcee4561a33901f8c505629d933585662feccf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733570Reviewed-by:
-
Sam Maier authored
Binary-Size: We were mistakenly not doing this Bug: 965189 Change-Id: I03f64ec6b81ab9da97b3ef9258c7dec17706f91d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730845 Commit-Queue: Sam Maier <smaier@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Auto-Submit: Sam Maier <smaier@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#683660}
-
Ken Rockot authored
r680551 landed a partial fix which corrected the issue specifically for single-process mode, but the more general bug is that a UtilityProcessHost can still call UtilityProcessHost::Client::OnProcessTerminatedNormally() even if a process was never launched. This fixes the bug in all cases by ensuring that |launch_state_| is |kLaunchComplete| before invoking OnProcessTerminatedNormally(). This state is only set once process launch has successfully completed. Bug: 987448 Change-Id: I5c419cdb16b8f8b67058fdad0385b499552354e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733011Reviewed-by:
-
Tim Volodine authored
Move files that are still used in the network service code path to the /network_service directory. The idea is that the old /net directory is going to eventually disappear. BUG=989842,989104 Change-Id: I28a39353a9b4f4d6cecf04fb78df328272cfdefa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733547 Commit-Queue: Tim Volodine <timvolodine@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#683658}
-
rbpotter authored
Bug: 965770 Change-Id: I9e78f603d8649bd05ccff37c59a5a3f18c2c1623 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1714324Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#683657}
-
Ian Wells authored
Refresh suggestions in the background with more urgency to bring Feed's background fetching in line with Zine's. Bug: 988165 Change-Id: I412ad34a7ec6c1b6c3ec3bf5e089ee2a0854e77f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730090 Commit-Queue: Ian Wells <iwells@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#683656}
-
Matt Simmons authored
R=yusufo@chromium.org Bug: 989638 Change-Id: I15558b826884ba4762f8d2e30bf3556798cfbb97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730526Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Matt Simmons <mattsimmons@chromium.org> Cr-Commit-Position: refs/heads/master@{#683655}
-
Miah Sanchez authored
Removed because this tast test is no longer failing. BUG=chromium:968155 TEST=Manual. Change-Id: Iaba0c34b16e2fb970af4295f919bf9e878e2f18d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732149Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: Miah Sanchez <miahsanchez@google.com> Cr-Commit-Position: refs/heads/master@{#683654}
-
Peter Kotwicz authored
This CL makes chrome/browser/webapps OWNERS also OWNERS of WebAPK metrics in chrome/browser/metrics BUG=None Change-Id: I874c8560e0bfd393ad85b3ff85030d668bb2b993 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733115Reviewed-by:
-
Matt Menke authored
There is no IOThread anymore, and it's really testing browser/net stuff, so move it in there. The new name is NetworkQualityEstimatorBrowserTest, since that's what all the tests are checking. I removed on test for PAC script downloads that are hung during shutdown, as that's no longer an issue the browser process has to worry about - that's now a concern just for the NetworkService. Bug: 934009 Change-Id: Ic7e042c83c767a2ee8674bad12ce3dea53508c21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730857Reviewed-by:
Eric Roman <eroman@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/b43eb88b..75502974 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: I10ac03e3680f4e8e5fe127c05385da0c1ccab049 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731647Reviewed-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@{#683651}
-
Ken Rockot authored
This eliminates the existence of the "chrome" and "chrome_renderer" services as well as general support for embedder-provided process-wide browser and renderer Service Manager services. Remanining browser<->renderer interfaces which used these services have been migrated to use direct receiver binding via content.mojom.ChildProcess or content.mojom.ChildProcessHost messages. Change-Id: I74f012aafe77fdcbbba8d93d193d3ded8d63d445 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729968Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
-
Max Moroz authored
Also removed "Custom options" section as it doesn't need to be advertised anymore. The only real usecase we still may have is `close_fd_mask`, but it's discouraged and we better use it on a case-by-case basis, when it's inevitable. Bug: 539572, 827228 Change-Id: I036303e1da0c844be4c3970ba5351651a2251a89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729847 Commit-Queue: Max Moroz <mmoroz@chromium.org> Reviewed-by:
Jonathan Metzman <metzman@chromium.org> Cr-Commit-Position: refs/heads/master@{#683649}
-
Eric Foo authored
Bug: 977050 Change-Id: I8d646c24f67bc07d9653c8b42b4e782aaa4b89c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732690 Auto-Submit: Eric Foo <efoo@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#683648}
-
Jan Wilken Dörrie authored
This change modifies the leak_detection_api.proto to have the same package name as the server side definition. Bug: 986298 Change-Id: I259b4c78c59dc9898a212a88f294e9b20414086a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732079 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#683647}
-
Carlos Caballero authored
MessageLoopForIO will go away soon use ScopedTaskEnvironment instead. ScopedTaskEnvironment will per default start a ThreadPool, which should be fine in most of the cases. If you believe your test needs to make sure that no ThreadPool runs let me know and I will update the patch. BUG=891670 This CL was uploaded by git cl split. R=nparker@chromium.org Change-Id: I70d76f6297874ac4a35bfe5e52a5033a081b09be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733533 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Reviewed-by:
Nathan Parker <nparker@chromium.org> Commit-Queue: Nathan Parker <nparker@chromium.org> Cr-Commit-Position: refs/heads/master@{#683646}
-
Mike Reed authored
Bug: skia:9293 Change-Id: I5adae8c65415ffa96af2c636aa93581a2658be2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733435 Commit-Queue: Mike Reed <reed@google.com> Commit-Queue: Florin Malita <fmalita@chromium.org> Reviewed-by:
Florin Malita <fmalita@chromium.org> Cr-Commit-Position: refs/heads/master@{#683645}
-
Changwan Ryu authored
This should be landed after the upstream fix https://chromium-review.googlesource.com/c/chromium/src/+/1730313 and the downstream fix https://chrome-internal-review.googlesource.com/c/clank/internal/apps/+/1560327 land. Bug: 817644 Change-Id: I66a986374804b8e6642275ee08c2412458c12258 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730781Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Commit-Queue: Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#683644}
-
Etienne Bergeron authored
This CL is renaming the GetActualFontNameForTesting to GetActualFontName. This function will be used in future CL. The difference between GetFontName and GetActualFontName is related to font mapping. The requested font name is the one the user is asking for and the mapped is the one used. We are exposing it since we want to get rid of the difference between GDI and DirectWrite: GDI name=Meiryo UI --> font-name:Arial actual-name:Arial DirectWrite name=Meiryo UI --> font-name:Meiryo UI actual-name:Segoe UI The GDI (e.g. PlatformFontWin) was the only one where the requested font was lost and were using the mapped font. Since that class is going away, the use of FontName and ActualFontName make sense. R=robliao@chromium.org, asvitkine@chromium.org Bug: 944227 Change-Id: I7a351c35a13ef07799c783454f206d76851ce02f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733437 Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:Robert Liao <robliao@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#683643}
-
Daniel Cheng authored
Bug: 978579 Change-Id: I382b9da1d8aec0199355374ed6930a730b7e4562 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731788Reviewed-by:
Nate Chapin <japhet@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#683642}
-
Xiaoqian Dai authored
Refactoring CL. No functional change. Bug: None Change-Id: I6e6027b5994e48d3ebafb7ec09062600763b0d28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726665Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#683641}
-
Rayan Kanso authored
Keep track of how often the Contacts API is used by measuring calls to navigator.contacts.select. Bug: 990364 Change-Id: I10177d894d4e68be275fcf2fe7cf7c87ade0b311 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731847 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Commit-Queue: Peter Beverloo <peter@chromium.org> Auto-Submit: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
-
Carlos Caballero authored
MessageLoopForIO will go away soon use ScopedTaskEnvironment instead. ScopedTaskEnvironment will per default start a ThreadPool, which should be fine in most of the cases. If you believe your test needs to make sure that no ThreadPool runs let me know and I will update the patch. BUG=891670 This CL was uploaded by git cl split. R=mmenke@chromium.org Change-Id: I2abffb81e28b6afcf29a9e0d96b1eff8163c130e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733494 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#683639}
-
Carlos Caballero authored
MessageLoopForIO will go away soon use ScopedTaskEnvironment instead. ScopedTaskEnvironment will per default start a ThreadPool, which should be fine in most of the cases. If you believe your test needs to make sure that no ThreadPool runs let me know and I will update the patch. BUG=891670 This CL was uploaded by git cl split. R=carlosil@chromium.org Change-Id: I8a40cda13a2956cddde98da24717da74081f8457 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733609 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:
Carlos IL <carlosil@chromium.org> Commit-Queue: Carlos IL <carlosil@chromium.org> Cr-Commit-Position: refs/heads/master@{#683638}
-
