- 04 Sep, 2019 40 commits
-
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/142d30cdaa58..d1b014babc86 Created with: gclient setdep -r src-internal@d1b014babc86 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,chromium:None Change-Id: I21aeafb8dfdb4432f2620cfd687cbc999d643409 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785617Reviewed-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@{#693430}
-
John Budorick authored
Follow-up to crrev.com/c/1775074 Bug: 990885 Change-Id: I44fdf83d6872bd264fb3e50d53fc34b47abbe09b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1786181 Commit-Queue: John Budorick <jbudorick@chromium.org> Commit-Queue: Stephen Martinis <martiniss@chromium.org> Auto-Submit: John Budorick <jbudorick@chromium.org> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#693429}
-
Sophie Chang authored
Bug: 854413 Change-Id: I3d2910b5c23200038777f0b80f7e6c2d05d82df2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785658Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Commit-Queue: Sophie Chang <sophiechang@chromium.org> Cr-Commit-Position: refs/heads/master@{#693428}
-
Toby Huang authored
Add step in commit_checklist.md for squashing commits into a single commit on the local branch before running `git rebase-update` to avoid commit-by-commit merge conflicts. Bug: None Change-Id: Icccf48d6fe739a3f20f8dd3f7d101ecdad46e3a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784162 Commit-Queue: Toby Huang <tobyhuang@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#693427}
-
rbpotter authored
Only trim whitespace from the beginning and end before validation, not from the entire value. Bug: 1000147 Change-Id: I9d6f0a105eef2c886d999d0a4799f02ac13758bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784008Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#693426}
-
Brandon Wylie authored
The following errors are present if you try to change ToolbarPhone: .../ToolbarPhone.java:481: 'if' construct must use '{}'s. .../ToolbarPhone.java:1888: 'if' construct must use '{}'s. .../ToolbarPhone.java:2479: 'if' construct must use '{}'s. I'm not sure what let these sneak in or why they're bubbling up now. Change-Id: I96d7308aaafb57773a0c8a18e653db522f18a40d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784350Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/heads/master@{#693425}
-
James Cook authored
SplitSettings is on-by-default. However, if we have to turn it off, we don't want the combined settings page to show the promo banner linking to OS settings (which won't exist). Test: Run chrome --disable-features=SplitSettings with an empty user data directory. Open settings. No promo banner shown. Bug: 1000307 Change-Id: If87d7cf3049353a2a1a322c042adb4bfa886f462 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785478 Auto-Submit: James Cook <jamescook@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#693424}
-
dalyk authored
These metrics will be used to compare the performance of DNS-over-UDP with DoH for each of the providers in the hardcoded mapping, to understand whether the probe-first approach to automatic mode successfully limits negative performance effects, to understand how the probes are behaving, and to understand the overall effect on start-to-finish DNS resolution times. Bug: 985589 Change-Id: I2d35eb6a11e52220a0af540ffc978c4576c31570 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771990 Commit-Queue: Katharine Daly <dalyk@google.com> Reviewed-by:
Nik Bhagat <nikunjb@chromium.org> Reviewed-by:
Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#693423}
-
David Bokan authored
This reverts commit ad308d5f. Reason for revert: Reverting since M78 is branching and this hasn't gone through IntentToShip yet Original change's description: > Enable FractionalScrollOffsets > > This enables fractional scroll offsets which allows non-integer values > in Blink's scrolling data structures. > > https://github.com/bokand/RenderingIndependentScrollOffsets/blob/master/README.md > > Bug: 414283 > Change-Id: I145899dd4a3ae9f3b3c936749fbe0b52cbc9ba3e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1766355 > Auto-Submit: David Bokan <bokan@chromium.org> > Commit-Queue: Nasko Oskov <nasko@chromium.org> > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Reviewed-by: Nasko Oskov <nasko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#690942} TBR=nasko@chromium.org,bokan@chromium.org,chrishtr@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 414283 Change-Id: If35d080634a399f8d2425df1ea258bfe0e578685 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785838Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#693422}
-
Toni Barzic authored
Move app list config creation from AppListConfig::instance to a newly introduced class AppListConfigProvider. Having a dedicated "factory" class for AppListConfig instances is cleaner than creating new configs off of a global AppListConfig instance. In addition to CreateAppListConfigForAppListWidget (which was moved from AppListConfig::instance), adds getter for app list configs per AppListConfigType, which will be used in a later cl to provide apps grid configuration to app list model (needed to generate folder image for app list config type). Adds some test for AppListConfigs, and fixes the app list item title margins and fonts. BUG=998207,996808 Change-Id: Id6c395d1087cbc17982ce7a9e263e1dbbdc7752d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783518 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#693421}
-
Matt Mueller authored
Remove old and broken PaypalNullCertParsing test. Bug: 605457 Change-Id: Ibbc501c336058e2bad2044c12da5c61f4fbcd73b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785742Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Matt Mueller <mattm@chromium.org> Cr-Commit-Position: refs/heads/master@{#693420}
-
Adrienne Walker authored
This plumbs a new optional relaxedDurability flag from the IDBDatabase transaction web api in the renderer to the IndexedDBBackingStore in the browser. Flushing after every file write is very expensive and burns power, and so it's desirable to eventually experiment with turning this option off by default. It is currently implicitly on. This patch doesn't change the default, but only exposes the option. Results from my local Linux machine on the issue 785305 test case: num | master | patch ------+-----------+--------- 1000 | 41386 ms | 1843 ms 5100 | 214892 ms | 14283 ms 10000 | 423271 ms | 34271 ms This test case had extremely variable output times, but this seems to be about a 10x performance improvement on that test case. Bug: 965883, 785305 Change-Id: Id54b65bd462f0983f8af44abc26575135d35f535 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1775557 Commit-Queue: enne <enne@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#693419}
-
Jacques Newman authored
This change allows nodes marked with aria-hidden="true" to be exposed to the browser-side AX tree with the State::kIgnored. This allows elements these nodes be returned from UIA_DescribedByPropertyId and UIA_LabeledByPropertyId. This change can be observed in the update to AXObject::ComputeAccessibilityIsIgnoredButIncludedInTree(). Change-Id: Ia1c4230326af7f3196c49b9666c567b451505dc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760862 Commit-Queue: Jacques Newman <janewman@microsoft.com> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Kevin Babbitt <kbabbitt@microsoft.com> Cr-Commit-Position: refs/heads/master@{#693418}
-
James Cook authored
When users open OS settings we show a dismissable banner that tells them where to find browser settings. We intend to remove the banner after a few milestones, when the click-through rate falls. Record: * If banner is shown or hidden when OS settings open * When user clicks the browser settings link * When user dismisses the banner (which is persistent) Clean up an unnecessary <a> that contained neither text nor an icon. Refactor show logic into a function and add tests. Bug: 999438 Test: browser_tests OSSettingsMainTest.* Change-Id: I2d1ea02c726535d04e13f68e67a57828f8636a75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1779165 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#693417}
-
Abigail Klein authored
Apply WebVTT captions styles in the correct order by introducing overridable styles for mac. A design doc for this change is here (and partly transcribed below): https://docs.google.com/document/d/1-yj3YhRYKRQqizp7ivxHHZBWla228l5MAJRdOuN6AqY/edit# --What was happening before this change?-- Styles are being applied in the following order: 1. User agent styles 2. Author styles 3. Styles the user set in their OS or Chrome (as inline styles on the VTT cue element) WebVTT inline styles are not applied at all. In MacOS, there is an option for an author style to override a user style. This is currently not observed. ---In what order should the WebVTT captions styles be applied?--- According to the WebVTT spec, they should be applied in the following order: 1. User agent styles 2. Overridable OS/Chrome styles (MacOS has styles which do not allow the video to override them) 3. Author styles 4. WebVTT inline styles 5. Not overridable OS/Chrome styles In MacOS, there is an option for an author style to override an OS style. We’ll explicitly separate those OS/Chrome styles which are allowed to be overridden by author styles and those OS/Chrome styles which cannot be overridden by author styles (we’ll name them “important OS/Chrome styles”). Styles from all other OS’s (Windows, Android, and ChromeOS) are important OS/Chrome styles. There should not be a clause where the presence of any of these styles should override all of another type of style. Safari does not do this, so for browser consistency, Chrome should not either. In addition, there was a complaint from a customer about this policy. ---Design--- 1. User agent styles are always applied first as per the StyleResolver::MatchAllRules. No work to be done. 2. Overridable OS/Chrome styles should be injected as another user agent stylesheet. This will ensure that they are injected before the user stylesheets (step two of StyleResolver::MatchAllRules), which are user extensions. This will be done on load, when all of the user agent style sheets are added (in CSSDefaultStyleSheets::EnsureDefaultStyleSheetsForElement). 3. Author styles are applied next as per the third step of StyleResolver::MatchAllRules. No work to be done. 4. Handling WebVTT inline styles is done as part of https://chromium-review.googlesource.com/c/chromium/src/+/1685677. 5. Important OS/Chrome styles will have the CSS !important, which will be added in caption_style_mac and piped over IPC to blink. User agent importance takes priority over user and author importance, so the important OS/Chrome styles will take precedence over all video styles, even those marked !important. Note that while the implementation is changing here, the effect is the same with respect to OS/Chrome styles before this change (they were previously applied as inline styles on the caption cue elements). Bug: 979649 Change-Id: I877ce4bb665b8f3b1bc8d6c2e2c285187d97a891 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1764966 Commit-Queue: Abigail Klein <abigailbklein@google.com> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#693416}
-
Ryan Powell authored
Updates the MultiSourceMemoryPressureMonitor's timer to use a callback to a new function, RecordCurrentPressureLevel, as the previous implementation bound the MemoryPressureLevel observed at the time at which the timer was started, meaning the same level was recorded every time the timer went off. Bug: 980965 Change-Id: I2bcab3631bd0f0185bcb054bf28e748a35cd72d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785258 Commit-Queue: Ryan Powell <ryanpow@google.com> Reviewed-by:
Sébastien Marchand <sebmarchand@chromium.org> Cr-Commit-Position: refs/heads/master@{#693415}
-
Kayce Basques authored
Bug: 986998 Change-Id: Iab7bef3f45b6a6ae03fff1f048cfb8787990ed68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785797 Auto-Submit: Kayce Basques <kayce@google.com> Commit-Queue: Kayce Basques <kayce@google.com> Commit-Queue: Erik Luo <luoe@chromium.org> Reviewed-by:
Erik Luo <luoe@chromium.org> Cr-Commit-Position: refs/heads/master@{#693414}
-
Tommy Li authored
There's already an about:flags entry for on-focus suggestions here. It currently has a variant for the NTP realbox. This just adds an additional variant to cover the NTP omnibox. Bug: 996516 Change-Id: I0e037116caf2826c0458808c0d636c557d80f759 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783750Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#693413}
-
Charlene Yan authored
Bug: 997151 Change-Id: I8cac4c9f56a271201de62af0d250365372f1a95d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784967Reviewed-by:
Peter Boström <pbos@chromium.org> Commit-Queue: Charlene Yan <cyan@chromium.org> Cr-Commit-Position: refs/heads/master@{#693412}
-
David Black authored
Experiment IDs will be provided via finch and passed to the proactive suggestions server for triggering on the backend. This will allow us to reconcile server side logging and UMA logging with respect to experiment arms. Bug: b:139199715 Change-Id: I208b606f607ef165bd7ddbc18a912dc3dcd34c85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783698 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#693411}
-
rbpotter authored
Change cr-toast-manager's cr.define to use: cr.define(... () => { function foo() {} let bar = ... return { foo: foo, }; }); syntax, to make it simpler to autogenerate the Polymer 3 version of this code by matching the polymer autogeneration script's approach to that of the JS modulizer script. It is possible to modify the autogeneration script to handle the code as-is, but this requires adding more annotations (e.g. to indicate whether variables should be let or const) and more complexity in the script (e.g. to replace ": " with "= " and to correctly handle arrow syntax). Also fixing some typechecking errors that were found by the compiler after changing the syntax. Bug: 965770 Change-Id: I7a725ad8513f4141bba13e13cd842133105cb60a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784101Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#693410}
-
Lambros Lambrou authored
This fixes an issue reported on recent MacOS version, where the ContinueWindow was not hidden after pressing either of the buttons. This is the same issue that affected the Share confirmation window, which was fixed in http://crrev.com/c3ed375625dabcfe3ceaf2ca17146a6b10fc3bf1 Change-Id: Id2a3e913a3e9fa5c47d05fbbc2e2b314eae3612d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785997 Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org> Commit-Queue: Jamie Walch <jamiewalch@chromium.org> Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org> Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Cr-Commit-Position: refs/heads/master@{#693409}
-
Haiyang Pan authored
This includes: - platforms;android-23 - system-images;android-23;google_apis;x86 Bug: 997376 Change-Id: I376c588d625c6ffb6ebdcd87a08a93d0a3be5c3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769798Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#693408}
-
Albert J. Wong authored
Attempt to reland: https://chromium-review.googlesource.com/c/chromium/src/+/1773878 CFI bot identified a lifetime issue that manifested in a hang during TouchSelectionForCrossProcessFramesTests/TouchSelectionControllerClientAuraSiteIsolationTest.BasicSelectionIsolatedIframe/0 === Original commit message === RenderWidgetHost::GetVisualProperties() was doing 3 separate things (1) Actually calculating the VisualProperties (2) Checking against the last stored VisualProperties to determine if the stored copy needs updating. (3) Determining if an ack should be expected if an update is eventually sent with the result of this function. This CL breaks it out into 3 new functions: GetVisualProperties() - Generates the VisualProperties. This should be const but too much of the call chain underneath it did not annotate their getters with const that annotating would be too annoying. DidVisualPropertiesSizeChange() - Helper function that extracts a common query used by DoesVisualPropertiesNeedAck() and StoredVisualPropertiesNeedsUpdate(). DoesVisualPropertiesNeedAck() - Returns true if sending the given VisualProperties update to the renderer will generate an ack. StoredVisualPropertiesNeedsUpdate() - Returns true if the stored copy of the VisualProperties is different enough from the incoming one that it needs an update. Bug: 998273 Change-Id: Ifabce4e3232ee313bde937e6098dc83c2e616333 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783669Reviewed-by:
Albert J. Wong <ajwong@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Auto-Submit: Albert J. Wong <ajwong@chromium.org> Commit-Queue: Albert J. Wong <ajwong@chromium.org> Cr-Commit-Position: refs/heads/master@{#693407}
-
James Cook authored
Some users directly navigate to chrome://help to check for OS updates. Add a banner with a link to About Chrome OS. Screenshot: http://screen/KARbXaGN2no Bug: 1000307 Change-Id: Id85031eec50d65e2f1e862ec664b60e9e74e9e02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784011 Auto-Submit: James Cook <jamescook@chromium.org> Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#693406}
-
John Lee authored
Bug: 989131 Change-Id: I152d509958df396b667bd54da5a75eb056f10589 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1778597 Commit-Queue: John Lee <johntlee@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#693405}
-
Gordon Guan authored
Performing layout inflation synchronously on devices with low core count leads to startup time improvement (~170 ms empirically, on one specific device) Bug: 985545 Change-Id: I4ee8a54f34ae040d357a2817f4d40038dcbe903a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783528 Commit-Queue: Gordon Guan <gordonguan@google.com> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#693404}
-
Guido Urdaneta authored
The image may be null in some situations, so check if it is null before sending it as a frame. Bug: 997556 Change-Id: I567f12e6a9890152a86b551c82cc64d962ead302 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782697 Auto-Submit: Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Armando Miraglia <armax@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#693403}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/53a464d7b4f6..c382c68c4f88 git log 53a464d7b4f6..c382c68c4f88 --date=short --no-merges --format='%ad %ae %s' 2019-09-04 dbeckett@google.com Adding in a promise option to EvaluateJavascript 2019-09-04 bsheedy@chromium.org Reland "Reland "Reland "Support minidump symbolization on ChromeOS""" Created with: gclient setdep -r src/third_party/catapult@c382c68c4f88 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC simonhatch@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=simonhatch@google.com Bug: chromium:992452,chromium:978952 Change-Id: Iae2d10124a8502f92e65141b60085dbd2389e58f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783875Reviewed-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@{#693402}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/65b7843ab9b6..69265b03982f git log 65b7843ab9b6..69265b03982f --date=short --no-merges --format='%ad %ae %s' 2019-09-04 lalitm@google.com Merge "trace_processor: migrate GPU tables to new macros" Created with: gclient setdep -r src/third_party/perfetto@69265b03982f If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@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=perfetto-bugs@google.com Bug: None Change-Id: I0c9a2f6ea72cff8cee72e18da4aedf0bca1c9c6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784353Reviewed-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@{#693401}
-
Bailey Berro authored
Updates the icon for the OS Settings Personalization page. Bug: 996425 Change-Id: Ia5976f8d5b886e047234f7651cb6712147e4e3ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785005 Commit-Queue: Bailey Berro <baileyberro@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#693400}
-
Toby Huang authored
SupervisionTransitionScreenTest uses a lot of login functionality that's centralized within LoggedInUserMixin. Avoid code duplication by refactoring SupervisionTransitionScreenTest to use LoggedInUserMixin for logging in. Bug: 990909 Change-Id: Iaead0d13e9b170a5e8eb933828c562dbfac45c5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1776903Reviewed-by:
Aga Wronska <agawronska@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Toby Huang <tobyhuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#693399}
-
Dominic Battre authored
Extending the lifetime as we want to track the metric as we experiment with re-engaging users in Q4/Q1. Bug: 984187 Change-Id: I141a2173f4655796f332e00b9f797df1ab714ae2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768328 Auto-Submit: Dominic Battré <battre@chromium.org> Reviewed-by:
Nik Bhagat <nikunjb@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#693398}
-
Jan Krcal authored
This CL extends the latency metric for initial sync to all data types (previously, we recorded that only for types with ephemeral storage). Bug: 998501 Change-Id: If11f0969b74c699de8c6d9ae665932083379a806 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1773147 Commit-Queue: Jesse Doherty <jwd@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Auto-Submit: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#693397}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Iebd8212bac32c3bc19df732845b300b07a8b987a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783916Reviewed-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@{#693396}
-
dalyk authored
Now includes OpenDNS FamilyShield mapping. Bug: 985589 Change-Id: Ia526ddfb19eafe236c01c5f3b78b00b00c3c36f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1784971Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Katharine Daly <dalyk@google.com> Cr-Commit-Position: refs/heads/master@{#693395}
-
John Lee authored
Bug: 999094 Change-Id: I830363d723b495669eb22c0ed30c32ffb41182e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783664Reviewed-by:
calamity <calamity@chromium.org> Commit-Queue: John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#693394}
-
Bettina authored
The current code does not decipher between multiple signed-in content area accounts. However, the SecurityEventRecorder only supports one signed-in account, whether it's consented or unconsented. The modal warning still shows for all signed-in content area accounts. Pingining is now only for unconsented signed-in account. All other content area signed-in accounts will not get pings. Bug: 999369,914410 Change-Id: If197c4085794025a4355c3d2a89c173f4c310178 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1777068 Commit-Queue: Bettina Dea <bdea@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#693393}
-
Nick Harper authored
Bug: 994899 Change-Id: I458f7fdd5b925ab58b3bb522301d10be7612fee5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1772493 Commit-Queue: Nick Harper <nharper@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#693392}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/aea4bca2621b..a6b07058f952 git log aea4bca2621b..a6b07058f952 --date=short --no-merges --format='%ad %ae %s' 2019-09-04 thestig@chromium.org Add a test for glyph path rendering. 2019-09-04 thestig@chromium.org Add a pixel test for a fixed JBIG2 bug. 2019-09-04 thestig@chromium.org Remove CRLF line endings from link_annots.in. 2019-09-03 thestig@chromium.org Roll third_party/freetype/src/ 9adc3b35f..543a3b939 (31 commits) 2019-08-28 gourabk@microsoft.com Add embedder tests for progressive render public APIs Created with: gclient setdep -r src/third_party/pdfium@a6b07058f952 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=pdfium-deps-rolls@chromium.org Bug: chromium:601362,chromium:963885 Change-Id: Ib95fe39d0b40e4f159dd0dd4493b6bc4070d53d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783561Reviewed-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@{#693391}
-