- 31 Jan, 2020 40 commits
-
-
Kent Tamura authored
This CL introduces blink::MenuListInnerElement, which will replace the anonymous block in LayoutMenuList. For now, we just add the element to UA shadow tree with display:none. So this CL doesn't have any changes on SELECT rendering. * UpdateUserAgentShadowTree() Add MenuListInnerElement as the first child of ShadowRoot if UsesMenuList(). Otherwise, remove it from the UA shadow tree. * Update some test expectations for the new shadow element. Bug: 1040828 Change-Id: I6c59c45dcc41baa41ff0e0ab060c14c2eefb6cff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032645Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#737248}
-
Philipp Hancke authored
show in the webrtc-internals page that you are using SDP munging BUG=823036 Change-Id: I874bc4575f7718355336507d84c7616971c30e6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1953635 Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Reviewed-by:
Harald Alvestrand <hta@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#737247}
-
Kenichi Ishibashi authored
This CL moves ScheduleDeleteAndStartOver() call from ServiceWorkerStorage::DidFindRegistration() to ServiceWorkerRegistry so that we can reduce ServiceWorkerContextCore dependency from ServiceWorkerStorage. DidFindRegistration() is removed as a consequence of this change because it just called ScheduleDeleteAndStartOver() and converted status. Bug: 1039200 Change-Id: I0af1314ab774617cacb7847a026c117835f77754 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032447Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#737246}
-
Patrick Monette authored
This will allow the WorkerTaskProvider to do accurate bookkeeping on running dedicated workers, even though it dynamically subscribe and unsubscribe to the DedicatedWorkerService while some workers are already running. Bug: 1041093 Change-Id: I96e75274d938324fe178a0999ff7968b030b8827 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2018143 Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#737245}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d65a6015c6a6..8fa7c321f46b Created with: gclient setdep -r src-internal@8fa7c321f46b 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 Bug: None Tbr: jbudorick@google.com Change-Id: I7df7a5d42ee2f59781cda26502f96217d1aa6d2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032849Reviewed-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@{#737244}
-
Kazuki Takise authored
The hotseat affects the position of the PIP window, so this CL includes the following changes to take it into consideration in collision detection. - Add the hotseat to collision rects. We adjust the bounds of the hotseat a bit so that we can slide the PIP window along the hotseat smoothly. - Make hotseat state change trigger a system ui area change event in workspace layout manager. Note we still have the PIP initial bounds issue as Android still doesn't know the correct initial position. BUG=b:147790853 TEST=Manually confirmed the PIP window was placed at the correct TEST=position (once dragged) and was moved smoothly. TEST=Manually confirmed toggling in-app state properly adjusted the TEST=PIP window. Change-Id: Idefc2877aa4aaf8996a016b64721bae4a74b3cea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014357Reviewed-by:
Mitsuru Oshima (slow in TOK) <oshima@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: Kazuki Takise <takise@chromium.org> Auto-Submit: Kazuki Takise <takise@chromium.org> Cr-Commit-Position: refs/heads/master@{#737243}
-
Hirokazu Honda authored
This reverts commit 139567ba. Reason for revert: Regression, HW encoder is not utilized on sarien b/148625570 Original change's description: > content/renderer/media: Query GPU process HW encoder capabilities > > Originally GpuVideoAcceleratorFactoriesImpl get HW encoder > capabilities by referencing values stored GpuInfo instance. > However, the values are not updated after GPU process boots up. > Even if a new hw encoder is available after GPU process is > initialized, the hw encoder is not detected. > > This fixes the problem by querying GPU process the hw encoder > capabilities when a render process is created. e.g. open the > page. > > Bug: b:147404923 > Test: HW encoder is used at appr.tc > Test: tast run webrtc.* on krane > Change-Id: Ibca82b6e54e9b5d585037c8e63f4c663d085db0e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994849 > Reviewed-by: Dominick Ng <dominickn@chromium.org> > Reviewed-by: Dan Sanders <sandersd@chromium.org> > Commit-Queue: Hirokazu Honda <hiroh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#735339} TBR=sandersd@chromium.org,dominickn@chromium.org,hiroh@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: b:147404923 Bug: b:148625570 Change-Id: I75bfe87b97505f400d1fb5c27facff507495cfb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032454Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#737242}
-
Eriko Kurimoto authored
This CL allows developers to use header files ending with 'mojom-forward.h' in public directories. Traditionally, we use 'mojom-shared.h' files, but we now have 'mojom-forward.h' filed and it is better to use forward header files. This is discussed here: https://chromium.slack.com/archives/CGGGVPSQ4/p1580370782044400 Bug: n/a Change-Id: I2bd1bd3d304d8a46e8df5bfd3ebc0d49f5497d22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032686Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Eriko Kurimoto <elkurin@google.com> Cr-Commit-Position: refs/heads/master@{#737241}
-
anina koehler authored
When policy templates are changed, syntax_check_policy_template_json.py is run as part of the presubmit checks. It should also be run when changes to the file itself were made. Bug: 1045930 Change-Id: Ic8870bd748d80d87b99b93889640cf2ebbbf0b27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022794Reviewed-by:
Alexander Hendrich <hendrich@chromium.org> Commit-Queue: Anina Koehler <aninak@google.com> Cr-Commit-Position: refs/heads/master@{#737240}
-
Renato Silva authored
Improves the overlay dialogs shown on OOBE ARC terms of service screen to match MD specs. Fixed: 1030466, 1032914 Change-Id: If10fcdec926d724f43c08034519dac5b14eb55c4 Bug: 1030466 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1953740Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Renato Silva <rrsilva@google.com> Auto-Submit: Renato Silva <rrsilva@google.com> Cr-Commit-Position: refs/heads/master@{#737239}
-
Andres Calderon Jaramillo authored
This reverts commit 0ea41733. Reason for revert: In this CL, GetOverlayMailbox() calls BufferQueue::GetCurrentBuffer(). Unfortunately, it turns out there are cases where this causes the GPU to draw to a buffer that's being scanned out (see https://crbug.com/1047030 for an example). It may also cause problems with damage tracking. Reverting this CL to try to fix the issue before the M81 branch point :( Original change's description: > Viz/Ozone/DRM: Provide NativePixmap for the primary plane > > Plumb mailbox for the primary plane to OverlayProcessorOzone and use > SharedImageInterface to obtain the corresponding NativePixmap. > > Bug: 756454 > Change-Id: Ic537d05253bc68c27a8fed961de8547ace359e82 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016327 > Reviewed-by: Robert Kroeger <rjkroege@chromium.org> > Commit-Queue: Saman Sami <samans@chromium.org> > Cr-Commit-Position: refs/heads/master@{#736065} TBR=rjkroege@chromium.org,samans@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 756454 Change-Id: I6f42b94d1939597f7c34f0d0433d45a02716aa58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031723Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#737238}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-compile-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-compile-chrome BUG=762641 TBR=chrome-os-gardeners@google.com Change-Id: Ife76dd9a8bfd16e43b5936a1829ccf1945b58760 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032193Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#737237}
-
Morten Stenshorne authored
We'll now put *all* fragments generated from a node into a vector in LayoutBox, instead of pointing to (at most) one fragment (was only stored if the fragment was cacheable). When a fragment is regenerated (after a relayout), we'll overwrite entries in the vector. Each fragment now has a "sequence number", which is stored in the break tokens. We need this to tell the fragments apart. Block fragmentation may cause a node to generate multiple fragments, and multicol balancing [1] and rebalancing [2] may go back and relayout and overwrite fragments for the current column row (until everything fits nicely). Then we need to know at which fragment indices to store the new fragments (and nuke the old ones following, if any). The sequence number will also be used for other purposes in an upcoming CL, for example to cache the drawing of each fragment; see ScopedDisplayItemFragment. At least we'll need this as long as we don't create a unique DisplayItemClient for each fragment. This is in preparation for NG fragment traversal (for painting and hit-testing), which is needed by block fragmentation. This CL, however, should not affect behavior in any way (but is filed as a separate CL nevertheless, due to its size) - hence the unit tests. We already have a bunch of block fragmentation tests in ng_column_layout_algorithm_test, but I put the new tests in a new file, since they aren't really about testing the column layout algorithm, but rather block fragmentation in general (and the same can be said for many of the tests in ng_column_layout_algorithm_test, BTW). In an upcoming CL, PaintLayer will walk through these fragments and paint them separately. The list of fragments will also be used to map to FragmentData entries. In the future, we might also consider making FragmentData an (optional) member of NGPhysicalFragment, since there is a 1:1 relationship between NGPhysicalFragment and FragmentData. [1] See NGColumnLayoutAlgorithm::CalculateBalancedColumnBlockSize() [2] See the exit condition for the outer loop in LayoutRow(). Bug: 829028 Change-Id: I2e0b678c378327ea21d60a5c306845ce7b6e9e21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030949Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
-
Simon Zünd authored
This CL re-writes a breakpoint web test using a new SourcesTestRunner helper introduced in https://crrev.com/c/2027427. This should not only prepare the test for the upcoming source map asyncification but also reduce the overall flakiness of breakpoint web tests. R=sigurds@chromium.org Bug: chromium:1032016 Change-Id: I1002384ffa6bbc330cd3132c183e356e5b1f59ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029368 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#737235}
-
Adam Rice authored
For "cheap" checks of state in the streams implementation, use CHECKs instead of DCHECKs. This will improve robustness against logic errors. BUG=1045931 Change-Id: I01af9c21feca586c74e354faa8f919fbb7565c64 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032471Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#737234}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a161f0c9091d..d65a6015c6a6 Created with: gclient setdep -r src-internal@d65a6015c6a6 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 Bug: None Tbr: jbudorick@google.com Change-Id: I02c5f142fb69151a1ea789f9e3df7183b46b10c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032846Reviewed-by:
-
Koji Ishii authored
Bug: 982194 Change-Id: I1b55db65d9fae0903d91d0fb682da5c15ac0891c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028876Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#737232}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e196bc85ac2d..088b1baa948a git log e196bc85ac2d..088b1baa948a --date=short --first-parent --format='%ad %ae %s' 2020-01-31 ynovikov@chromium.org Change uuid attributes to declspec in winrt. Created with: gclient setdep -r src/third_party/angle@088b1baa948a 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 tobine@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-asan;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: tobine@google.com Change-Id: Ied6ebb542bb12063bb6de5c21815417af2d929b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032844Reviewed-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@{#737231}
-
Kuznetsov Alexey authored
In chromium code audio_utility.cc we just need to use PI constant from //base instead from local file. This is some polishing. Change-Id: I71d7042a9ed40c563c67bab2237b267c822a6961 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027367Reviewed-by:
Peter Kasting <pkasting@chromium.org> Reviewed-by:
Yuri Wiitala <miu@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#737230}
-
Tao Bai authored
Add call site for AwContents state of AwContentsLifecycleNotifier. Bug: 1042048 Change-Id: I6d59b2b956fe8b1dbf2f208a3f2881fdc6f4d778 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023400 Commit-Queue: Tao Bai <michaelbai@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#737229}
-
Alan Screen authored
Given that there are so few printing-specific features, have them all in one file instead of multiple very small files for each OS. ChromeOS did not use the printing::features namespace for the flags before, so update that throughout for consistency. Change-Id: I30d062236d404d7f53c212333ddfcc8c27968503 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031867 Commit-Queue: Alan Screen <awscreen@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Daniel Hosseinian <dhoss@chromium.org> Cr-Commit-Position: refs/heads/master@{#737228}
-
Alan Screen authored
With the removal of Harfbuzz subsetter the only printing/common features left are related to XPS printing on Windows. As discussed in [1] move these out of common so that they can be included as part of the regular printing component. [1] https://crrev.com/c/1988767/5 Bug: 1008222 Change-Id: I5b5c096eaa50cf53cfe62c1f12319cb506c6fc7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026369 Commit-Queue: Alan Screen <awscreen@chromium.org> Reviewed-by:
-
Takashi Toyoshima authored
Bug: 941354 Change-Id: Iaf0b1ca9e8a4898333dead2ba4b4a38cbee00b48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028880Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#737226}
-
nancy authored
When adding a new user, although IsMultiProfileAvailable return true, MultiUserWindowManagerHelper::GetWindowManager is still null. So add a check for MultiUserWindowManagerHelper::GetWindowManager. When MultiUserWindowManagerHelper::GetWindowManager is still null, we don't need set owner for windows, because multiple user window manager is not ready yet. BUG=1047376 Change-Id: Idb527b24e0f7d66714b6f408b08f20e50b6f8c32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032486Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#737225}
-
Noel Gordon authored
The iconSet property of most volume types is empty, but we expect that third party volumes (ANDROID_FILES, DOCUMENT_PROVIDERS and File System Providers) should provide icons in the respective iconSets. Add a shouldProvideIcons() helper to volume manager common, that lists the volumes types that should provide icons. Bug: 992819 Change-Id: I00b9d1910ff9069fb82d1a51519f0dc72d2c81a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032469 Commit-Queue: Alex Danilo <adanilo@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Alex Danilo <adanilo@chromium.org> Cr-Commit-Position: refs/heads/master@{#737224}
-
Chromium WPT Sync authored
Using wpt-import in Chromium d998cfeb. Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: I42cff1fb06e632c0598a10a64abb422b80a518c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031907Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#737223}
-
Md. Hasanur Rashid authored
The Chromium C++ style guide recommends that DVLOG is used as it "avoids bloating the release executable and in debug can be selectively enabled at runtime". Fixed: 519010 Change-Id: I0a66e81332847b250bfc1038727ddfa020ed634d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029472 Commit-Queue: Md. Hasanur Rashid <hasanur.r@samsung.com> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#737222}
-
Kent Tamura authored
inner_block_ will be removed soon. The function will help the removal. This CL has no behavior changes. Bug: 1040828 Change-Id: I5acc8dc885a5c218fe215c37c017d0463cfb3ce6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032448Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/689bf533edd9..a161f0c9091d Created with: gclient setdep -r src-internal@a161f0c9091d 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 Bug: chromium:1041701 Tbr: jbudorick@google.com Change-Id: Ie81acfebc79a4d6d4a11f0e76c1f62b6098402a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032580Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/f28d0ae61457..f44a809f9a3b git log f28d0ae61457..f44a809f9a3b --date=short --first-parent --format='%ad %ae %s' 2020-01-31 kainino@chromium.org Remove VK_DEFINE_NON_DISPATCHABLE_HANDLE magic, use explicit VkHandle wrapper 2020-01-31 enga@chromium.org [docs] Add documentation for Dawn's testing infrastructure Created with: gclient setdep -r src/third_party/dawn@f44a809f9a3b 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 Bug: chromium:1046362 Tbr: cwallez@google.com Change-Id: Ia6733a40384a8bea2380f8132a0ac1d246690cb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032579Reviewed-by:
-
Anand K. Mistry authored
Bug: None Change-Id: Idb695ce4366dbcbbf48e2958b2f74276d5491ad9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030927 Auto-Submit: Anand Mistry <amistry@chromium.org> Reviewed-by:
François Degros <fdegros@chromium.org> Commit-Queue: Anand Mistry <amistry@chromium.org> Cr-Commit-Position: refs/heads/master@{#737218}
-
John Delaney authored
This change adds a feature which modifies the AdTagging heuristic for frames that are the results of non-srcdoc navigations. This change is only implemented in AdsPLMO for metrics and the heavy ad intervention, and is not intended to be implemented there permanently. Frames with a url that match an allowed filter list rule and are not considered ad frames even if they are created by ad script. Frames with a url that are same-domain to the top-level page and do not match a disallow filter rule are not considered ads, even if created by ad script. Bug: 1030325 Change-Id: I45831aa84e339f0d8fd8c642e8fb2520d3d76d9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1954181 Commit-Queue: John Delaney <johnidel@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#737217}
-
Toni Barzic authored
Fixes an edge case where opaque shelf background doesn't get reshown after it's hidden for transition from home screen. The opaque background is hidden when transition from kShown hotseat state starts, and reshown once it ends. In both cases ShelfView checks the original hotseat state to determine whether the opaque background state should be updated. This does not work if the original hotseat transition is interrupted by another hotseat state change (to kShown state, as only transitions from/to shown state are animated) - in this case hosteat transition animator stops observing implicit animations before it updates the animating backgrounf transform, so it doesn't send the end notification for initial transition. Once the second animation finishes, the shelf widget delegate will only see the end notification for the second transition, and given the hotseat state is not kShown, it will not update the opaque background visibility. (If the user exits tablet mode before going to home screen again, they will see completely transparent shelf). BUG=1044751 Change-Id: I07e15126215c908831ad24b4aeb525eb2ef66513 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032008Reviewed-by:
Manu Cornet <manucornet@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#737216}
-
Sergey Ulanov authored
Now FuchsiaAudioRenderer can handle mid-stream configuration changes. Bug: 1047537 Change-Id: I93b61f56fd1a9e84b2a5a1c82dc3fc0c5f660e3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029455 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#737215}
-
Manu Cornet authored
Also fix a memory management issue that was latent beforehand, use the |DeleteDelegate| pattern that the shelf widget is already using, for the navigation widget, since a widget delegate must outlive its widget. This makes it more clear that all the shelf components (nav widget, hotseat, status area, shelf widget) are now meant to play a similar role in the class hierarchy. This change isn't expected to have any impact on user-visible behavior. Change-Id: I78688ec4f4fda7185dfcdf9e260c94f083d94923 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032188 Commit-Queue: Manu Cornet <manucornet@chromium.org> Reviewed-by:
Andrew Xu <andrewxu@chromium.org> Cr-Commit-Position: refs/heads/master@{#737214}
-
Kurt Horimoto authored
The default cancellation handler is deleted after calling Cancel(), so the observer needs to be removed before cancellation. Bug: 1038514 Change-Id: I9a638b9ae7c6c44e4655fb5d80674285620c308d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032062Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Auto-Submit: Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#737213}
-
Virender Singh authored
This change modifies the PDF document's name string to follow formatting rules defined in: http://userguide.icu-project.org/formatparse/messages Bug: 1043505 Change-Id: I1cad4ecea83b41a1ccf7adb68ad3e2a104f65749 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030350Reviewed-by:
Kevin Babbitt <kbabbitt@microsoft.com> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Reviewed-by:
-
Kent Tamura authored
If a json5 file for make_names.py contains duplicated names, make_name.py produced invalid C++ code and we had to remove duplicates. * make_names.py should report an error for duplicated entries instead of producing invalid code. * html/keywords.json5 should allow duplicated entries because it contains keyword sets for multiple attributes and some keywords are valid for multiple attributes. Change-Id: I81c2a4a978ece5a03471fd8b37d85b61cda2a8e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032465 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#737211}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/08f1abcc5bb0..659962bc1b4c git log 08f1abcc5bb0..659962bc1b4c --date=short --first-parent --format='%ad %ae %s' 2020-01-31 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. Created with: gclient setdep -r src/third_party/devtools-frontend/src@659962bc1b4c If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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 Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I564612f9fcff1253adb663ddd162db42b6e629a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032569Reviewed-by:
-
Kent Tamura authored
* select-box.html Convert a pixel test to an assert_selection.js test * select-element-paragraph-boundary.html Merge this into select-box.html * document-write-option.html Convert a pixel test to a reference test. Bug: 1040828 Change-Id: I15e156016b183a44709f7a6bc7b520f83a7a73f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032644Reviewed-by:
-
