- 17 Oct, 2019 40 commits
-
-
Hirokazu Honda authored
This is a follow up CL of crrev.com/c/1855142. The CL causes failures in image_processor_test, because a layout of planes is not specified in ImageProcessor initialization, and the adjusted planes are not exposed in LibyuvImageProcessor. This CL fixes those mistakes. Bug: 1005636 Test: image_processor_test on atlas Change-Id: I481d0ca8d276721103030a9ba89d2b590050885d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863065 Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Reviewed-by:
Chih-Yu Huang <akahuang@chromium.org> Reviewed-by:
Alexandre Courbot <acourbot@chromium.org> Cr-Commit-Position: refs/heads/master@{#706794}
-
rhalavati@chromium.org authored
Tab.Count.Incognito UMA was previously added in crrev.com/c/1647854, but the Android implementation was missing. It is added in this CL. Bug: 966747, 1014018 Change-Id: I1f51550d7ad6844a0f53039a00625d33b53fcf69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863799 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Auto-Submit: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#706793}
-
Maksym Onufriienko authored
Example of error: https://chrome-swarming.appspot.com/task?id=47e61333eed2f710 Bug: 1011851 Change-Id: I598615ac07cac20294e7171f81c6fb1ec07ed2fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862245Reviewed-by:
Justin Cohen <justincohen@chromium.org> Commit-Queue: Maksym Onufriienko <monufriienko@chromium.org> Cr-Commit-Position: refs/heads/master@{#706792}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/7f426898efe0..31bde9585709 git log 7f426898efe0..31bde9585709 --date=short --no-merges --format='%ad %ae %s' 2019-10-17 enga@chromium.org perf_tests: Replace WaitForGPU with maxStepsInFlight argument Created with: gclient setdep -r src/third_party/dawn@31bde9585709 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel TBR=cwallez@google.com Bug: None Change-Id: I1741c81ea8ecbdff7ed22796e9490754e690c137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865046Reviewed-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@{#706791}
-
Hiroshige Hayashizaki authored
Before this CL, only `imports` parts of import maps were tested. Chromium side: - This CL makes ImportMap::ToString() to output the whole import map, rather than only the `imports` value. - This CL removes white spaces for pretty printing, to simplify the logic. WPT side: - This CL checks the whole import maps in `jest-test-helper.js`. - Reflect the upstream changes in https://github.com/WICG/import-maps/pull/190 to `builtin-support.tentative/imported/resources/parsing-scope-keys.js`. Test expectation changes: - This CL exposes new test failures in `parsing-scope-keys.tentative.html` on Chromium due to the spec-inconformant behavior of Chromium's URL parser. - Other test expectation changes are just converting `x` to `{imports: x, scopes: {}}`. Bug: 990561, 927181 Change-Id: Ic6a0171298636170d2fd96db2ac1a8d60e3ff345 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863854Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#706790}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/91024cf94428..6ee22f8f2e9b Created with: gclient setdep -r src-internal@6ee22f8f2e9b 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: I61b1e58bf0c20eaec2bfaa4b36913dfa52913f0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865706Reviewed-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@{#706789}
-
Kuo Jen Wei authored
For photo mode, filter out preview size exceeding screen size. For video mode, follow order of preferred resolution, 1080p, 720p, rest of resolution sorted by size. Bug: b/142523663 Test: Verify preview resolution used in photo and video mode are correct. Change-Id: Iadb5c70ff00a65ee6cdbc4d71b790d7567d8b1d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864508Reviewed-by:
Shik Chen <shik@chromium.org> Commit-Queue: Kuo Jen Wei <inker@chromium.org> Cr-Commit-Position: refs/heads/master@{#706788}
-
Alan Cutter authored
This CL implements the final part of the ManifestUpdateTask process where the web app is reinstalled with new manifest data. Bug: 926083 Change-Id: I291b64d3e7c05b24a50761acc40ee4d007821a8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1811402 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#706787}
-
Simon Que authored
Previously this was reverted due to infrastructure issues that have since been resolved. This CL is the same as the previously landede CL: https://chromium-review.googlesource.com/c/chromium/src/+/1780983 ============================================= CI/try builders migrated: - mac-code-coverage-generation - mac-hermetic-upgrade-rel - mac-mojo-rel - mac-osxbeta-rel - Mac Builder / mac-rel, mac_chromium_10.12_rel_ng, mac_chromium_10.10, mac_chromium_compile_rel_ng - Mac Builder (dbg) / mac_chromium_dbg_ng, mac_chromium_compile_dbg_ng - GPU Mac Builder / mac-rel See migration schedule of when this is expected to land: https://docs.google.com/spreadsheets/d/1TZhpasm6iceYm7zqkyEtZ1wn9ZcpREfH4LV4cusICJA/edit#gid=0 Bug: 950413 Change-Id: I6d19e6043b3d1776321e512a348395c325ed3484 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860856Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Simon Que <sque@chromium.org> Cr-Commit-Position: refs/heads/master@{#706786}
-
Kazuki Takise authored
We don't want to apply ComputeFlungPosition() for PIP resize. send a wrong bounds at the end of resize anymore. Bug: b/142105182 Test: Resized a PIP window very quickly and confirmed Chrome didn't Change-Id: Ie1d6b1288f4ff16175ee013edbc5dd2e3660f863 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849750Reviewed-by:
Eliot Courtney <edcourtney@chromium.org> Reviewed-by:
Stefan Kuhne <skuhne@chromium.org> Commit-Queue: Kazuki Takise <takise@chromium.org> Auto-Submit: Kazuki Takise <takise@chromium.org> Cr-Commit-Position: refs/heads/master@{#706785}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/9e4f6d03f2f7..a959deb00750 git log 9e4f6d03f2f7..a959deb00750 --date=short --no-merges --format='%ad %ae %s' 2019-10-17 johnkslang@users.noreply.github.com Merge pull request #1933 from dj2/runtest Created with: gclient setdep -r src/third_party/glslang/src@a959deb00750 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,jmadill@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=radial-bots+chrome-roll@google.com,jmadill@google.com Bug: None Change-Id: I97b1b86b20b98748613685503c3d498687cee636 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866025Reviewed-by:
-
Jinsuk Kim authored
The public method |initialize| is deliberately separated from the constructor as an initialization step that gets TabObserver-inherited objects notified to do their own initialization. This CL makes the API package-private and moves it into TabBuilder to reduce its visibility. There is no functional change in the behavior. Bug: 995903 Change-Id: Ibdde4bb257c532e5a29a1e6650329ef219374df2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1843994 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#706783}
-
Joey Arhar authored
Previous to this CL, and after [1], if a form Submit button had an onclick handler that also called form.submit() and did not call event.preventDefault(), the form would get submitted twice. The second request was eventually cancelled, but not before it hit the network. This behavior is specified in [2], through the "plan to navigate" mechanism. In the case of this bug, the "click" event occurs first, and changes the "planned navigation". Then, because the click handler does not preventDefault(), the default submit action is executed, which changes the "planned navigation", replacing the navigation queued by the onclick handler. Therefore, only the default submit navigation is performed. Note that there are other potential interactions which are less clearly specified, and which are not addressed in this CL. For example: <iframe id="test" name="test"></iframe> <form id=form1 target="test" action="click.html"></form> <a target="test" onclick="form1.submit()" href="href.html">Test</a> In this case, clicking the <a> link first submits the form (to click.html), and then queues a navigation to href.html. Because the navigation to href.html is specified (in [3]) to "queue a navigation", independently of the planned navigation specified in [2], it is unclear when/whether the form submission should take place. The spec ([4]) does have provisions for canceling existing navigations, but that leaves room for the form to still get to the network in this case, before getting canceled. [1] https://chromium.googlesource.com/chromium/src/+/6931ab86f19aa79abbdd0c1062084e16b5c4f0f6 [2] https://www.w3.org/TR/html52/sec-forms.html#form-submission-algorithm [3] https://html.spec.whatwg.org/#following-hyperlinks [4] https://html.spec.whatwg.org/#navigating-across-documents Bug: 977882 Change-Id: I693f3bdccb17c5e64df75c2e569fab589c02e88c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850358 Commit-Queue: Joey Arhar <jarhar@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#706782}
-
Justin Cohen authored
Bug: 987646 Change-Id: Iaa13ee085aec001158ac46151a50d5ab3cbfa46c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862994 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#706781}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/3800252a84f8..edf765329fe2 git log 3800252a84f8..edf765329fe2 --date=short --no-merges --format='%ad %ae %s' 2019-10-17 mmortensen@google.com Handle android branch/target/version for boards without android. 2019-10-17 ahassani@chromium.org auto_updater: Retry GetUpdateStatus on failure Created with: gclient setdep -r src/third_party/chromite@edf765329fe2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: Ie2d1a68f6d1c13d8f248403817c0b03ec7c0c79a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866066Reviewed-by:
-
Kai Ninomiya authored
Note: Some of the tests in the WebGPU CTS right now require runtime compilation of GLSL to SPIR-V. Those tests are currently excluded from the variants list in cts.html to avoid importing glslang yet. Bug: 984818 # Tracking issue Bug: 1014785 # Expectations bug # Actual WebGPU bugs Bug: 1014734, 1014735, 1014738, 1014740 Bug: 1014744, 1014750, dawn:243 Change-Id: Ibb42565565afd29e428f72cc5f26d149b784cdfc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860509 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#706779}
-
Alex Keng authored
The current implementation (which uses border-radius: 20px 0px 0px 20px for the value part) has two issues: 1) when the value is large (ex 99%), the flat end overlaps the rounded edge. 2) when the value is small (ex 1%), border-radius doesn't render correctly. (see the associated bug for details) The new implementation achieves the rounded corner effect using clip-path which is applied to a new container div (-internal-meter-clip) added between -webkit-meter-bar and -webkit-meter-*-value. test: fast/forms/controls-new-ui/meter/meter-extreme-values.html Bug: 1013977 Change-Id: I1d50a42bfa9903952664f5f9cac265021e57b642 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1858295Reviewed-by:
-
Darren Shen authored
We used to have a JSON-based rulebased API, where we needed to escape certain characters in the protocol. We then added an API based purely on Mojo types. However, the code for the JSON one was copied for the Mojo one, so we also escaped certain characters. This means that we actually insert escaped characters rather than the characters themselves. For example, typing "\" gives "\\". We delete the escaping code and add tests to prevent this in the future. Bug: 1014384 Change-Id: I8865869aa020b94c961c71826fa72d6cf2c96b67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859809Reviewed-by:
Keith Lee <keithlee@chromium.org> Reviewed-by:
Leo Zhang <googleo@chromium.org> Commit-Queue: Leo Zhang <googleo@chromium.org> Auto-Submit: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#706777}
-
Nicholas Verne authored
Reverted in https://chromium-review.googlesource.com/c/chromium/src/+/1862337 This fixes an uninitialized member variable in a test fixture found by msan. Adds UpgradeContainer logic to CrostiniManager. A call to UpgradeContainer can start off a long-running upgrade process via the Cicerone daemon. A dbus signal UpgradeContainerProgressSignal is used to communicate progress to Chrome, including the final success or failure of the upgrade itself. Bug: 930901 Change-Id: I18ae12c5706f9a989c5c8247ca8ba223d25cf41a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862883Reviewed-by:
Nic Hollingum <hollingum@google.com> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org> Auto-Submit: Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#706776}
-
Jeevan Shikaram authored
This CL renames the labels of App Management's localized strings to prevent overlap with other settings' localized string labels. It also removes any unused strings. Bug: 1014815 Change-Id: I52b20363b140d1abc7839f763013eeeff6d31513 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862888Reviewed-by:
Trent Apted <tapted@chromium.org> Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org> Cr-Commit-Position: refs/heads/master@{#706775}
-
Justin Cohen authored
Record the time taken to read a stored session window, or write one to a file. Bug: 1007337, 1010609 Change-Id: I8f98348c51b8b407b60d9514008431c2fa564d87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860303Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#706774}
-
Ahmed Fakhry authored
- Make SetEnabledForTest/Dev() simulate a device physical tablet state, which is closer to reality. - This CL also fixes an issue with the overview button, where it should show after transitioning to UI tablet mode finishes. More follow-up CLs are planned for this feature. BUG=925087 TEST=No change in behavior, all tests must pass. Change-Id: I451b40a4f0da5814893d5e2e4cb618d7d4cf2aab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865543 Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#706773}
-
tby authored
Add a CrSOActionRecorder call for each usage of the launcher, with type and query hash as conditions. Bug: 1012936 Change-Id: Ie1e42487c67dc922407bb39f538b67384297f48a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865911Reviewed-by:
Jia Meng <jiameng@chromium.org> Reviewed-by:
Charles . <charleszhao@chromium.org> Commit-Queue: Tony Yeoman <tby@chromium.org> Cr-Commit-Position: refs/heads/master@{#706772}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f29cb70281d5..97afd2e21cbf git log f29cb70281d5..97afd2e21cbf --date=short --no-merges --format='%ad %ae %s' 2019-10-17 mtklein@google.com add bsl.16b, cmeq.4s, cmgt.4s Created with: gclient setdep -r src/third_party/skia@97afd2e21cbf If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC csmartdalton@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-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=csmartdalton@google.com Bug: None Change-Id: Ib69eaaae775697029ea5e98db580db0023b2a7eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866065Reviewed-by:
-
Tommy Steimel authored
This CL uses borders to separate notifications in the media dialog. Bug: 1004707 Change-Id: I3c129e46ac1c855a906ac0577fcd092f9087c576 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864096 Commit-Queue: Tommy Steimel <steimel@chromium.org> Reviewed-by:
Jazz Xu <jazzhsu@chromium.org> Cr-Commit-Position: refs/heads/master@{#706770}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5cf279fb5b69..91024cf94428 Created with: gclient setdep -r src-internal@91024cf94428 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: I0aed3ccbd031637e027f245ac761b66fc5f6703b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866064Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=kariah@chromium.org Change-Id: I6ca1356dd6dde9fa416ca28f69f2b00f708584be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864368Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#706768}
-
Dan Beam authored
Also hide focus outline; just rely on background-color. Fixed: 1015137 Change-Id: Ib9b7e28815317a0954a624923aae0c2712b633df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864822 Commit-Queue: Dan Beam <dbeam@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#706767}
-
Charles Zhao authored
If for some reason, lots of actions are generated at very short period of time, we need to make sure: (1) We don't use too much memory. (2) We don't use too much disk. Bug: 1012936 Change-Id: I00e9d79c3a45dc3bdbe682bc2e9aae532bc00862 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866091Reviewed-by:
Tony Yeoman <tby@chromium.org> Reviewed-by:
-
Peter Kotwicz authored
This CL matches the status bar behaviour of WebAPKs to that of TWAs by: - Changing the status bar colour used by WebAPKs when the Web Manifest does not provide a "theme_color" to white. This requires increasing MINIMUM_REQUIRED_CHROMIUM_VERSION_NEW_SPLASH - Making the status bar use dark icons if the Web Manifest provides a light colour. BUG=997793 Change-Id: Ia628810345af90cd45bb9762e0ce24f500ed4bba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1857205 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#706765}
-
Tao Bai authored
This essentially adds CorePageLoadMetricsObserver to WebView, the integration test will be in following patch to keep patch simple. Bug: 995880, 992028 Change-Id: Icb25cad2690323d9a0dbd495c57f8f3b461d7c91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862251 Commit-Queue: Tao Bai <michaelbai@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Cr-Commit-Position: refs/heads/master@{#706764}
-
Noel Gordon authored
.computers-root and .external-media-root are file-list only - remove their unneeded [selected] state (directory) tree rules since these icons are never shown that tree, ever. - and file-list does not add [selected] state to icons, ever. fix drive file-type-icon='folder' rules - remove redundant .tree prefix since .tree-item implies you are in a directory .tree, by-design. - moreover, tree-item[selected] also means tree-row[selected] so we can simplify these rules even more ... - rule .tree .tree-item[selected] === .tree-row[selected] as one .tree-row only can be [selected] in the .tree at any time. 'downloads' and root_type_icon='drive' rules - define the normal and tree [selected] rules in the same order. Fix a comment, remove redundant whitespace. Bug: 992819 Change-Id: I210b775b02bfff011c407c8c33f9f966afcd33b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865052Reviewed-by:Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#706763}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/55e5853e5ce4..2a0049f96a77 git log 55e5853e5ce4..2a0049f96a77 --date=short --no-merges --format='%ad %ae %s' 2019-10-17 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/depot_tools@2a0049f96a77 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@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=agable@chromium.org Bug: None Change-Id: I4f592844c09091d065e50d2c2fdac0ee76ea430f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866062Reviewed-by:
-
Sanket Joshi authored
Bug: 1015095 Change-Id: I9df222bf1b310cdbc9e31c689b148e392be9b364 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865614Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/16944ed21bc2..ae1b7786b89a git log 16944ed21bc2..ae1b7786b89a --date=short --no-merges --format='%ad %ae %s' 2019-10-16 jonahr@google.com Fix ANGLE_FEATURE_CONDITION style issue Created with: gclient setdep -r src/third_party/angle@ae1b7786b89a If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@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=jmadill@google.com Bug: None Change-Id: I3f24dba6093d05912c3c3cc7992be2b9bdac5afa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865136Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/c9f13b8d903d..8df31ad1d9b8 git log c9f13b8d903d..8df31ad1d9b8 --date=short --no-merges --format='%ad %ae %s' 2019-10-17 crouleau@chromium.org Reland "[Telemetry] Refactor expectations code into story_filter.py." Created with: gclient setdep -r src/third_party/catapult@8df31ad1d9b8 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 oysteine@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=oysteine@google.com Bug: chromium:985103 Change-Id: I71b1b2f2d63f06b5680de86e9d0af1341bc24ad7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865138Reviewed-by:
-
Sanket Joshi authored
This change fixes a bug where the HSL and Hex values for the selected color could be NaN if the color well's selection ring was the bottom of the color well and the page zoom was set to 150%. At certain zoom levels like 150%, the height of the color well is not a round number. However, the getImageData API, which is used to retrieve the underlying pixel color data for the color well, only works with integer values and will truncate decimal values. As such, if the color well's selection ring is placed at the bottom of the color well, a valid pixel data point for the ring's position cannot be found in the image data array for the color well. When such a situation occurs, the fix is to use the last color in the color well's image data array. This color will be the same as the color seen at the bottom of the color well (black), so the user will see what they expect. Bug: 1015238 Change-Id: I1b74a4870fa455d197c525dca39dc88e7c6f75f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866060Reviewed-by:
-
Fritz Koenig authored
GLES 3.0 does not have glFramebufferParameteri. The spec for MESA_framebuffer_flip_y was updated to add glFramebufferParameteriMESA which will allow the MESA_framebuffer_flip_y functionality on GLES 3.0. BUG=955198 TEST=betty-vm Change-Id: I7e7d762e85b862a1264e130bbb22000adb17ba58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850797Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
-
Joel Hockey authored
Currently we disallow dropping tabs onto a browser that does not support FEATURE_TABSTRIP. This adds an extra check to also disallow if the source and target browser are not the same type (APP vs NORMAL). This CL includes some refactoring of the logic to check whether a tab can attach to a new target. * New function CanAttachTo replaces GetContextForWindow and ShouldDisallowDrag. * Removed TabDragContext.IsCompatibleWith and inlined the profile checking into CanAttachTo. * OnWidgetBoundsChanged no longer calls GetContextForWindow which was previously doing a number of pointless checks to see if the current attached context could drag to itself. Rather this codesite uses attached_context_ directly. From what I can tell, the widget change observer happens on move_loop_widget_ which is attached_context_. * GetTargetTabStripForPoint was previously doubling up on the checks in GetContextForWindow as this function was being called by ShouldDisallowDrag, then again immediately after to get destination_tab_strip_. Now these checks happen only once in CanAttachTo. * BringWindowUnderPointToFront now calls CanAttachTo which has the additional modal dialog check from ShouldDisallowDrag. Bug: 1012169 Change-Id: Iab0a09a1b37024b8611798822c94edd9c6820daf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862884 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#706756}
-
Brandon Wylie authored
The Google G (or other dse icon) should appear when scrolling the NTP. This icon wasn't displaying because the hasFocus boolean isn't set when scrolling. Adding plumbing to store the current focus percent in StatusMediator and factoring that into the dse icon showing logic. Bug: 1012508 Change-Id: Ia1f5a935ba5ceb8814000a520f482c661da716f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854505 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Ender <ender@google.com> Cr-Commit-Position: refs/heads/master@{#706755}
-
