- 16 Aug, 2018 40 commits
-
-
Oskar Sundbom authored
By putting these parameters in a struct, future changes to parameters accepted by audio sinks can be made easier, without changing so many dependencies. This CL also adds an optional 'processing_id' parameter to audio sinks. It will be used to associate input and output streams for audio processing, when it's running in the audio service. At this point, the id doesn't get transferred along IPC. That's part of the next CL. For an outline of the project this CL is part of, see: https://docs.google.com/document/d/1u4POff_ts_1LE3WDLA_wDDFnUswdlsuHL5DsiTE0a3U/edit?usp=sharing It's accessible to everyone @chromium.org. Bug: 851959 Tbr: kinuko@chromium.org 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 Change-Id: I59a467d83d1516965bbbf06cd4fc49a3198c6cfb Reviewed-on: https://chromium-review.googlesource.com/1163884 Commit-Queue: Oskar Sundbom <ossu@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#583659}
-
Annie Sullivan authored
Bug: 874810 Change-Id: I11ff44a55b4f2b14b8ba0a4ab5bb4e0f54cd8ef8 TBR: nednguyen@google.com NOTRY: true Reviewed-on: https://chromium-review.googlesource.com/1177882Reviewed-by:
Annie Sullivan <sullivan@chromium.org> Commit-Queue: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#583658}
-
Fredrik Söderquist authored
Too deep recursions can cause stack overflows. Bug: 874759 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ie532e28bceee4e7f1c3ab501b80c0e2f14be083a Reviewed-on: https://chromium-review.googlesource.com/1106378Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#583657}
-
W. James MacLean authored
Instead of using GetOuterWebContents, which only return the immediate parent of this WebContents, use GetOutermostWebContents to check against the root of the web-contents tree, which in this case should be the app-view's web-contents. Bug: 873672, 823021 Change-Id: I421a64be495c575d22501328ec732794abc045f4 Reviewed-on: https://chromium-review.googlesource.com/1176342 Commit-Queue: James MacLean <wjmaclean@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Lucas Gadani <lfg@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#583656}
-
Xida Chen authored
This is a follow up for https://chromium-review.googlesource.com/c/chromium/src/+/1174696 TBR=dtapuska@chromium.org Bug: 851644 Change-Id: I702bd9afc80a82d0b7db02cb8f06a1765c69aaaf Reviewed-on: https://chromium-review.googlesource.com/1177631 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by:
Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#583655}
-
Balazs Engedy authored
Ensure that FidoRequestHandlerBase only instantiates FidoDiscoveries for transports that are in the intersection of those supported by the client, and those allowed by the relying party; where the allowed transports are: (1) For MakeCredential calls: -- {BLE, caBLE, USB, NFC} if `authenticatorAtttachment` == `cross-platform`, -- {Internal} if `authenticatorAtttachment` == `platform`, -- (all) if `authenticatorAtttachment` == `any`. (2) For GetAssertion calls: -- (all) if `allowedCredentials` is undefined or empty, or if it contains an entry with `transports` undefined or empty, -- the union of `transports` lists in all elements of `allowedCredentials`. FidoRequestHandlerBase::Observer::OnTransportAvailabilityEnumerated is also changed to be consistent with this, i.e., the |available_transports| list in TransportAvailabilityInfo will also be this intersection set. Finally, the CL ensure that this method is always called on the observer, even if enumerating transports is finished before the observer is set. Bug: 866601 Change-Id: I00fbd6684fd52851149bdb0dd39800aafda54630 Reviewed-on: https://chromium-review.googlesource.com/1175118 Commit-Queue: Balazs Engedy <engedy@chromium.org> Reviewed-by:Jun Choi <hongjunchoi@chromium.org> Reviewed-by:
Kim Paulhamus <kpaulhamus@chromium.org> Cr-Commit-Position: refs/heads/master@{#583654}
-
Oskar Sundbom authored
It will be used both by content::MediaStreamAudioProcessor and the upcoming media::AudioProcessor. For an outline of the project this CL is part of, see: https://docs.google.com/document/d/1u4POff_ts_1LE3WDLA_wDDFnUswdlsuHL5DsiTE0a3U/edit?usp=sharing It's accessible to everyone @chromium.org. Bug: 851959 Change-Id: I794558e46ab01fd2f367e1df2fababdefb712c4f Reviewed-on: https://chromium-review.googlesource.com/1170841 Commit-Queue: Oskar Sundbom <ossu@chromium.org> Reviewed-by:
-
Andrew Grieve authored
Bug: 872904 Change-Id: Ia4ea4ff2de48680abc94bb0ff7c678a430c0cae4 Reviewed-on: https://chromium-review.googlesource.com/1176969 Commit-Queue: agrieve <agrieve@chromium.org> Reviewed-by:
Sam Maier <smaier@chromium.org> Cr-Commit-Position: refs/heads/master@{#583652}
-
Juan Antonio Navarro Perez authored
Tag a selection of system health stories chosen to have a wide coverage for catching regressions, but run in a limited amount of time. The stories chosen caught more than 80% of system health memory mobile regressions in Q2 2018, and a single repeat of the entire set runs in under 20 minutes. Bug: 865959 Change-Id: I397cda35bb71dadf94bb2343c389d00cb8e80ec3 Reviewed-on: https://chromium-review.googlesource.com/1177396Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#583651}
-
Stephen McGruer authored
This reverts commit 2b5dfbb0. Reason for revert: Strong suspect for performance regression (https://pinpoint-dot-chromeperf.appspot.com/job/14a343e2640000), and disagreements on original CL implementation. Reverting until they can be resolved. Bug: 872123, 869387 Original change's description: > Add full saturate-to-infinity behavior to base::TimeDelta > > Before this CL TimeDelta had saturation behavior for translating > from/to other values, but had clamping behavior for its computation. > That is, invariants like the following did not hold: > > TimeDelta::Max() - TimeDelta::FromSeconds(1) == TimeDelta::Max() > > This CL fully implements saturation behavior, such that TimeDelta::Max() > and TimeDelta::Min() are treated as positive and negative infinity > regardless, with all the expected mathematical consequences. > > The one exception is that adding/subtracting a saturated TimeDelta to a > TimeClass is still undefined. This was left undefined because we are not > yet making a statement on whether TimeClass should be considered to have > clamping or saturating behavior for values outsied of range. > > See the linked bug, or also the discussion at > https://groups.google.com/a/chromium.org/forum/#!topic/platform-architecture-dev/S4umX2sOvrk > > Bug: 869387 > Change-Id: I2b3f98c69e7fc5030a6e210d75409d667b73c5ac > Reviewed-on: https://chromium-review.googlesource.com/1155264 > Commit-Queue: Stephen McGruer <smcgruer@chromium.org> > Reviewed-by: Gabriel Charette <gab@chromium.org> > Cr-Commit-Position: refs/heads/master@{#579969} TBR=gab@chromium.org,smcgruer@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 869387 Change-Id: I7251e77bd66dc95c9b1aae16fbfc89acd239f19b Reviewed-on: https://chromium-review.googlesource.com/1175470 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#583650}
-
Leszek Swirski authored
Posted blocking ScriptStreamer tasks can end up in a queue, and have their Resource complete loading before the task even starts. When this happens, these tasks will no longer block on network input, but they will still be posted to the blocking task runner, which does not spin up new threads if the running task is not blocked. When there are a lot of small functions posted for streaming, this results in a slightly paradoxical starvation, where the blocking task runner is processing lots of no-longer-blocking tasks all in one thread, as it has no reason to spin up new threads. To avoid this, if a streaming task isn't started before the resource finishes loading, we can cancel this posted task, and instead post a new non-blocking task to the non-blocking thread pool. This frees up the blocking task runner to process only blocking tasks (and thus allows it to spin up new threads for them). Bug: chromium:865098 Bug: chromium:866868 Change-Id: Iceb282582781109ade233366d1009c3be50db3a5 Reviewed-on: https://chromium-review.googlesource.com/1174380 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#583649}
-
Danyao Wang authored
Current expectations assume a buggy behavior of LegacyNavigationManager, which doesn't create a pending item on reload (crbug.com/676129). The test initiates a navigation to the same page to abort the payment request. This navigation is incorrectly classified as renderer-initiated by LegacyNavigationManager, which causes the abort reason for payment request to be incorrectly logged as EVENT_OTHER_ABORTED. WKBasedNavigationManager fixes this bug, so the test should now check EVENT_USER_ABORTED. Bug: 874628 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I74997df64464f196cfcfb34f21b0252d2f2f6e3e Reviewed-on: https://chromium-review.googlesource.com/1176470 Commit-Queue: Danyao Wang <danyao@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#583648}
-
Anders Carlsson authored
When building a framework for macOS that has public headers, this flag is needed for the compiler to find the headers located inside the framework bundle. This same cflag is set when linking with frameworks in the build/config/ios/rules.gni template. E.g. the header may be at `xyz.framework/Headers/x.h` and it is imported with `#import <xyz/x.h>` in the source. We need this for using the WebRTC macOS framework from a demo app. Bug: webrtc:9627 Change-Id: Ib431bacfd85eb4597cb19e60ed575336b76b0598 Reviewed-on: https://chromium-review.googlesource.com/1177400Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Anders Carlsson <andersc@chromium.org> Cr-Commit-Position: refs/heads/master@{#583647}
-
David Bokan authored
A common pattern on the web is to resize a container to the window's innerWidth and innerHeight so that it matches the viewport size and accounts for the URL bar's presence. Unfortunately, these values are do not report fractional CSS pixels, they're floored. So on high DPI devices, innerHeight * devicePixelRatio != initial containing block's size. This patch allows applying the root scroller on pages following this pattern by ceil'ing the bounds values before comparing them to the ICB. Two additional unrelated changes: - Remove unused parameter in FillsViewport This is always true since some changes were made recently. - Early out for non-main frames in ProcessImplicitCandidates We avoid adding implicit candidates for non-main frames already so this is a no-op but this early out is convenient for debugging and logging. Bug: 838683 Change-Id: I740816184a26aa067e135041543170356e90fed5 Reviewed-on: https://chromium-review.googlesource.com/1176550Reviewed-by:
Ella Ge <eirage@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#583646}
-
Armando Miraglia authored
FYI: I am using this opportunity to test the submission flow on Chrome/Gerrit & co :) R=ossu@chromium.org Bug: None Change-Id: I6d5897a3e64160843d80b423f02c91d68430cb82 Reviewed-on: https://chromium-review.googlesource.com/1177718Reviewed-by:
Oskar Sundbom <ossu@chromium.org> Commit-Queue: Armando Miraglia <armax@chromium.org> Cr-Commit-Position: refs/heads/master@{#583645}
-
Xida Chen authored
This reverts commit 902e5475. Reason for revert: <INSERT REASONING HERE> Suspect causing layout test failure: https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20ASAN/15204 Original change's description: > [LayoutNG] Store NGPaintFragment in LayoutObject > > This patch stores a one-way linked list of NGPaintFragment to > their source LayoutObject. Looking up the HashMap consumes > non-ignorable time during paint. > > This patch adds IsInLayoutNGInlineFormattingContext flag to > LayoutObject. This flag represents whether the object is in > LayoutNG inline formatting context, even if the object itself > is laid out by legacy. > > With the flag, the storage used for storing InlineBox in > LayoutText, LayoutInline, and LayoutBox are changed to union > to store the first NGPaintFramgent. > > Bug: 714962 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel > Change-Id: I7dfd11fafa9b1527b8d77e1fa3a24abf0e7f551e > Reviewed-on: https://chromium-review.googlesource.com/1170726 > Commit-Queue: Koji Ishii <kojii@chromium.org> > Reviewed-by: Morten Stenshorne <mstensho@chromium.org> > Reviewed-by: Emil A Eklund <eae@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583633} TBR=eae@chromium.org,kojii@chromium.org,mstensho@chromium.org Change-Id: I9a870a209f86cfd061df8c82858b58093dff310b No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 714962 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Reviewed-on: https://chromium-review.googlesource.com/1177761Reviewed-by:
-
Adithya Srinivasan authored
Makes callsites use mojom::blink::FileSystemType instead. Bug: 787281 Change-Id: If0a3a687fa99b77b3a05ec8c4790f1ee0cbe6dd5 Reviewed-on: https://chromium-review.googlesource.com/1155157Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#583643}
-
Xida Chen authored
Mark virtual/new-remote-playback-pipeline/media/controls/modern/doubletap-to-jump-backwards-at-start.html flaky on Mac TBR=wjmaclean@chromium.org NOTRY=true Bug: 874866 Change-Id: Ie04f74b689e1bea6e7c51e5e30ba4a7ce70863fc Reviewed-on: https://chromium-review.googlesource.com/1177633Reviewed-by:
-
Vadym Doroshenko authored
Along the way 2 tests are fixed. Bug: 831123, 852742 Change-Id: If8466bf72cb81be1edbf5f0b95f7da5d309e6f54 Reviewed-on: https://chromium-review.googlesource.com/1169170 Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
Robert Kaplow (slow) <rkaplow@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#583641}
-
manuk authored
Omnibox: Prevent ctrl-enter behavior when we believe the ctrl key was pressed in order to perform another action. For example, if the user presses ctrl-a to select all the text in the omnibox, then presses enter without releasing ctrl, we do not perform ctrl-enter behavior. On the other hand, if the user releases and represses ctrl after performing a ctrl action, we do perform ctrl-enter behavior. This cl does two changes for the above goal. 1. Previously, ctrl-enter was disabled when the omnibox is focused via ctrl-l but not when the omnibox was already focused and the user presses ctrl-l. Now, we disable ctrl-enter in both cases. 2. Previously, ctrl-enter was disabled if a ctrl action caused either the omnibox selection or text to change; e.g. ctrl-v when the clipboard is non-empty causes a text change, and ctrl-a when the omnibox is non-empty causes a selection change. However, ctrl-enter was not disabled if the ctrl-action did not cause a selction or text change; e.g. ctrl-c, ctrl-v when the clipboard is empty, ctrl-a when the entire omnibox text is already selected, ctrl-left when no omnibox text is selected, etc. Now we disable ctrl-enter if an action was executed, regardless of whether that action caused the omnibox text or selection to change. For example, if text selection is not empty, ctrl-c will disable ctrl-enter, but if selection is empty, ctrl-c will not disable ctrl-enter. Ctrl-left/right/home/end are the 1 notable exception, where they will disable ctrl-enter regardless of whether the cursor was already at either edge. Bug: 75715 Change-Id: I8b2b4829697bf66855879366e4429494c3e95ab9 Reviewed-on: https://chromium-review.googlesource.com/1173424 Commit-Queue: manuk hovanesian <manukh@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#583640}
-
Tibor Goldschwendt authored
Monochrome is crashing on startup. Fix this by using the default proguard instead of proguard 6.0.3 for monochrome. In order to stay under the DEX method limit use multidex for monochrome release builds. Bug: 874464, 868770 Change-Id: I9f002c26fb6e2b9b1b5d7471dab890090c446a75 Reviewed-on: https://chromium-review.googlesource.com/1176474 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#583639}
-
A Olsen authored
go/cros-untangle shows that one reason why Chrome OS code depends on all kinds of Chrome internals, is because it uses g_browser_process to get hold of various Chroms OS globals, and g_browser_process keeps a reference to all globals, Chrome and Chrome OS. This CL removes a few easy-to-remove references to g_browser_process from chrome/browser/chromeos. Bug: 446937 Change-Id: I7ed4d1ccede3d0963ab86c80bba6f9327dd0cf61 Reviewed-on: https://chromium-review.googlesource.com/1174448 Commit-Queue: A Olsen <olsen@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#583638}
-
Vadym Doroshenko authored
These forms should not be filled. This CL implements that nor PasswordFormManager nor NewPasswordFormManager is created for such forms so as result they are not filled. Bug:871191 Change-Id: I509bb6d1ca500ac2bbbea265712001f61bec3c53 Reviewed-on: https://chromium-review.googlesource.com/1174714 Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
-
Leonard Ge authored
Change-Id: Id3e7dfd5a3e60f93ac6653eb7eb32af4a14b4b45 Reviewed-on: https://chromium-review.googlesource.com/1177608 Commit-Queue: Leonard Ge <wangge@google.com> Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#583636}
-
Juan Antonio Navarro Perez authored
The story should be independently disabled (on separate lines) for each of Android_Go and Android_One. TBR=nednguyen@google.com NOTRY=true Bug: 871708 Change-Id: Ifa5273b546738bf6e3162785590658671e8fe66f Reviewed-on: https://chromium-review.googlesource.com/1177713Reviewed-by:
-
Xida Chen authored
TBR=wjmaclean@chromium.org NOTRY=true Bug: 874853 Change-Id: I0e28c54f5dfbfa0ae940b48ea5319914e6b49768 Reviewed-on: https://chromium-review.googlesource.com/1177684Reviewed-by:
-
Koji Ishii authored
This patch stores a one-way linked list of NGPaintFragment to their source LayoutObject. Looking up the HashMap consumes non-ignorable time during paint. This patch adds IsInLayoutNGInlineFormattingContext flag to LayoutObject. This flag represents whether the object is in LayoutNG inline formatting context, even if the object itself is laid out by legacy. With the flag, the storage used for storing InlineBox in LayoutText, LayoutInline, and LayoutBox are changed to union to store the first NGPaintFramgent. Bug: 714962 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I7dfd11fafa9b1527b8d77e1fa3a24abf0e7f551e Reviewed-on: https://chromium-review.googlesource.com/1170726 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#583633}
-
Peter E Conn authored
Add a test case to cover comment 13 in the linked bug. Bug: 873178 Change-Id: I02fcb38b6737c79b41c32824bcfcc848e4cd79b3 Reviewed-on: https://chromium-review.googlesource.com/1177610Reviewed-by:
Paul Jensen <pauljensen@chromium.org> Commit-Queue: Paul Jensen <pauljensen@chromium.org> Cr-Commit-Position: refs/heads/master@{#583632}
-
Xida Chen authored
TBR=wjmaclean@chromium.org NOTRY=true Bug: 874853 Change-Id: I4d141e987d48df3ee4b4332c8341e5e5c7883301 Reviewed-on: https://chromium-review.googlesource.com/1177683 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by:
-
Andrew Grieve authored
R8 doesn't parse the "" version, but is fine with ''. Bug: 872904 Change-Id: I827798ac9b29031138397dcadde38567e3df63bb Reviewed-on: https://chromium-review.googlesource.com/1176631Reviewed-by:
-
Xida Chen authored
TBR=wjmaclean@chromium.org NOTRY=true Bug: 874851 Change-Id: I83cc51e272b418a942f324f3e0a408f7b05961d3 Reviewed-on: https://chromium-review.googlesource.com/1177629Reviewed-by:
-
Xida Chen authored
Flakiness dashboard shows that it is flaky on all platform TBR=wjmaclean@chromium.org NOTRY=true Bug: 859169 Change-Id: I5c9193cb1e36962c02b6c8d33739bc1687728ac1 Reviewed-on: https://chromium-review.googlesource.com/1177628Reviewed-by:
-
Gauthier Ambard authored
This CL removes the TabGrid implementation of BrowserCommands. This is done such as the -openNewTab: method of BrowserCommands can be removed in UI Refresh, merged away in the -openURL: method in ApplicationCommands. Bug: 861729 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I001e387a3f4668ff2291c49ef83354888ea81a03 Reviewed-on: https://chromium-review.googlesource.com/1127898Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#583627}
-
Rune Lillesveen authored
We mark nodes as needing a layout tree rebuild pass to reconsider the need for whitespace LayoutText objects if we remove any of its children. However, we don't need that if all children were removed, if the node no longer has a LayoutObject, or if the node was already marked for re-attachment. Change-Id: I74310936372320599b24f2d5146df855455bce1e Reviewed-on: https://chromium-review.googlesource.com/1177381 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#583626}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/4eb4b05556ff..e9721f2f0830 git log 4eb4b05556ff..e9721f2f0830 --date=short --no-merges --format='%ad %ae %s' 2018-08-16 titovartem@webrtc.org Move SimulatedNetworkConfig on top level. 2018-08-16 danilchap@webrtc.org Remove deprecated fields from RtcpStatistic struct 2018-08-16 nisse@webrtc.org Refactor voe::Channel to not use RtpReceiver. Created with: gclient setdep -r src/third_party/webrtc@e9721f2f0830 The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ic6e1d945bb71aeb629d95e66a294bf7974b29ed8 Reviewed-on: https://chromium-review.googlesource.com/1177582Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#583625}
-
Sam Maier authored
Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This exector is good for preventing concurrency errors since it guarantees serial execution, but bad for performance since the entire app shares this single queue. We are hoping to get rid of execute() entirely, since it is often assumed to be a parallel operation. It looks like this callsite can use the THREAD_POOL_EXECUTOR instead, since this use doesn't appear to rely on the concurrency guarantees that SERIAL_EXECUTOR provides. Bug: 869907 Change-Id: I51f22e371ec1e0d0e5114f4b211c934e214f5784 Reviewed-on: https://chromium-review.googlesource.com/1174900Reviewed-by:
Simeon Anfinrud <sanfin@chromium.org> Commit-Queue: Sam Maier <smaier@chromium.org> Cr-Commit-Position: refs/heads/master@{#583624}
-
Miguel Casas authored
This CL adds support for I420A VideoFrames in GMBVideoFramePool. These VFrames are turned into BGRA or RGBA depending on the preferred platform swizzling (spolier: BGRA is Mac). Canvas Capture test is changed to premultiplied to follow up the Skia convention. Bug: 873345 Change-Id: I20d1f9f59e47a55b67763b2cb7884387f99118a5 Reviewed-on: https://chromium-review.googlesource.com/1174949 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Reviewed-by:
-
Rune Lillesveen authored
FirstChild did not include pseudo elements and some PseudoAware* methods were already duplicated in the traversal methods. Change-Id: I002384693edb188eda9ee6388aa191c4727fbc84 Reviewed-on: https://chromium-review.googlesource.com/1177393Reviewed-by:
-
Eric Willigers authored
This mitigation shipped to stable in M61. https://chromium-review.googlesource.com/518156 https://www.chromestatus.com/feature/5735596811091968 BUG=680970 Change-Id: I827ca161ecc7e3d7b75fc2774cee8e6d0ea04ed3 Reviewed-on: https://chromium-review.googlesource.com/1164967Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#583621}
-
Xida Chen authored
TBR=wjmaclean@chromium.org NOTRY=true Bug: 874837 Change-Id: I1025816a10ffcc261a9fb21c434bf86b1f9a4dde Reviewed-on: https://chromium-review.googlesource.com/1177625Reviewed-by:
-
