- 20 Aug, 2020 10 commits
-
-
Andre Le authored
Add the logic to update visibility for "Clear all" button depends on the count of total and unpinned notification. BUG=1111167 Change-Id: Ie609ae1225c0041e3c45815b1f4c2550136ace77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339942 Commit-Queue: Andre Le <leandre@chromium.org> Reviewed-by:
Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#799890}
-
Avi Drissman authored
Bug: 1119479 Change-Id: I889ae0f4f01e5e4a79d48fca1172b920a1393a7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363363Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#799889}
-
Wan-Teh Chang authored
These test images were added in commit ea65e680: https://crrev.com/c/2321307 Bug: 1108626 Change-Id: I35f7b58ab9b38d308744513c77b617e271fcd47b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365220Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Wan-Teh Chang <wtc@google.com> Cr-Commit-Position: refs/heads/master@{#799888}
-
Ian Kilpatrick authored
Removes a combination of unused methods, or methods which only returned one possible value. There should be no behaviour change. Change-Id: Iabc747262dcf46dc514b361890a85adc171754fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363659Reviewed-by:
Mason Freed <masonfreed@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#799887}
-
Roman Arora authored
Mojo bindings and API to show the feedback page. Bug: 1099917 Change-Id: Ie1fd176f67d069b1eb7b9bed1db79751ea4c6df5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2356971Reviewed-by:
Peter Kasting <pkasting@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Thomas Lukaszewicz <tluk@chromium.org> Commit-Queue: Roman Arora <romanarora@chromium.org> Cr-Commit-Position: refs/heads/master@{#799886}
-
rajendrant authored
static_cast<TabWebContentsDelegateAndroid> maybe a problem if different delegate got used. So using a different method to check for isCustomTab Bug: 1117533 Change-Id: Ibf5fde78e77bfaa407538880c181c713e176cb0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363215Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#799885}
-
Adam Langley authored
This code matches up with the Android accessory device code recently added on the desktop side. It is not yet wired into anything on the phone side. BUG=1002262 Change-Id: I802eb6a0275a71744b374589003f5a0675bbb58d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341033 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#799884}
-
minch authored
The root window and root_location of the event are still based on the original display while dragging a window across displays. This makes the magnifier will not be activated in the display that the window has been dragged to until the drag be released. This cl updates the root window and root location during drag to make sure the magnifier can be activated at corresponding display immediately while drag a window across displays. Bug: 1082392 Change-Id: Ie3feb7679c29e1e9c0b4f8811ae98bd0f170ade0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354997Reviewed-by:
-
Timothy Loh authored
The path for vm disks recently changed so we need to correspondingly update the code here. This is a follow-up to http://crrev.com/c/2362163 which fixed detection of crosvm processes for Crostini. A tast test will be added in http://crrev.com/i/3186385 once this has uprevved. Bug: chromium:1114826 Change-Id: I97a7fb93fa18f54121ab9ca384281181b7ea0f52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364148Reviewed-by:
David Munro <davidmunro@google.com> Reviewed-by:
-
Mustafa Emre Acer authored
When Delayed Warnings feature detects and delays an interstitial, Client Side Detection could send another phishy verdict for the same URL. This causes the interstitial to be undelayed immediately. This CL changes the CSD behavior so that it never checks if a Delayed Warning observer is attached to a tab which only happens if a warning is being delayed. This is manually tested to work both on official and non-official builds. A follow up CL will add browser tests. Bug: 1118192 Test: Manual Change-Id: I418910c35ec692ef23e4295a6b59092cb55d5968 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364213Reviewed-by:
Daniel Rubery <drubery@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#799881}
-
- 19 Aug, 2020 30 commits
-
-
Dirk Pranke authored
This reverts commit cd69e8f5. Reason for revert: re-landing with a fix. Original change's description: > Revert "Rework generated_script handling in MB." > > This reverts commit b05d8793. > > Reason for revert: Broke ios full_configs bot. See: > https://ci.chromium.org/p/chromium/builders/ci/ios-simulator-full-configs/25885 > > Doesn't look like this change triggered the full_config bots on try. > > Original change's description: > > Rework generated_script handling in MB. > > > > It turns out the work I did on the "wrapped_*" targets in > > gn_isolate_map was somewhat overlapping with the already-existing > > iOS work to declare things as "generated_scripts". However, the > > generated_scripts did not include test_env.py. > > > > So, this CL rearranges things so that the generated script will call > > test_env.py, and then we can share logic between the generated_script > > targets (and every target on iOS and LaCrOS) and use that as the > > basis for the rest of the work going forward. > > > > Bug: 816629 > > Change-Id: I9d55c3f1587defcb599ddf1df838dd9ed5b6a12c > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357917 > > Reviewed-by: Erik Staab <estaab@chromium.org> > > Commit-Queue: Dirk Pranke <dpranke@google.com> > > Cr-Commit-Position: refs/heads/master@{#799171} > > TBR=dpranke@google.com,estaab@chromium.org,jeffyoon@chromium.org > > Change-Id: I94597d58417f7aa76320579ca282293e6b643811 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 816629 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364014 > Reviewed-by: Justin Cohen <justincohen@chromium.org> > Commit-Queue: Justin Cohen <justincohen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#799629} TBR=dpranke@google.com,justincohen@chromium.org,estaab@chromium.org,jeffyoon@chromium.org # Not skipping CQ checks because this is a reland. Bug: 816629 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs Change-Id: I1f481f23ff1f1de991b13f3e5aadf967818c2763 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364696 Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by:
Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/master@{#799880}
-
zhaoyangli authored
This is required from Xcode 12 which is rolled to main builders today. No-try: true Bug: 1119510 Change-Id: I7db1dcfdb3dde77d692bfc978ba6502db7592813 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365432 Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Commit-Queue: Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#799879}
-
Tommy Steimel authored
Bug: b:154517281 Change-Id: I4dbdbfb787db3d6436def3f77a2d19b0052a26ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2361044 Commit-Queue: Tommy Steimel <steimel@chromium.org> Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#799878}
-
Yuke Liao authored
This reverts commit 66870c32. Reason for revert: 1. The root cause is not lacros, symptom is generally seen across all builders. 2. #pending tasks is ~0 now: https://chromium-swarm.appspot.com/task?id=4e21b13cf27db110&o=true&w=true. 3. 400 VMs were temporarily added to the pool to mitigate the outage. Original change's description: > Revert "[lacros] Enable linux-lacros-rel by default" > > This reverts commit ac7726b8. > > Reason for revert: reverting to shed load on CQ, crbug.com/1119483 > > Original change's description: > > [lacros] Enable linux-lacros-rel by default > > > > This CL enables linux-lacros-rel on CQ by default. > > > > Bug: 1116180 > > Change-Id: I67bf89a5eefd7382bbd2886f416bc38c411213bf > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360496 > > Reviewed-by: Erik Staab <estaab@chromium.org> > > Commit-Queue: Yuke Liao <liaoyuke@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#799123} > > TBR=estaab@chromium.org,liaoyuke@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 1116180, 1119483 > Change-Id: I2be0017d3af1e863ec15efaa3c3cdf1ff1764911 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364140 > Reviewed-by: Ben Pastene <bpastene@chromium.org> > Cr-Commit-Position: refs/heads/master@{#799798} TBR=estaab@chromium.org,liaoyuke@chromium.org,bpastene@chromium.org # Not skipping CQ checks because this is a reland. Bug: 1116180 Bug: 1119483 Change-Id: Ib9211794c4eb92e3e5c721c77f4821dda49d8a0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365223Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#799877}
-
Kevin McNee authored
These tests crash under android asan. Tbr: asvitkine@chromium.org Bug: 1102747 Change-Id: If26aff18beacc1108e0617b4ba04d66ac3197709 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365152Reviewed-by:
Kevin McNee <mcnee@chromium.org> Commit-Queue: Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#799876}
-
Arthur Eubanks authored
Bug: 1114873 Change-Id: Idc828b72f08583ab336c706c1bd8843e076bf573 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357457Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#799875}
-
Jeff Yoon authored
ios14-beta-sim upstream is failing b/c of bad xcode value. Change-Id: I1572a773f4ce33d76bb536cbe0c39f88e3340693 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365294 Auto-Submit: Jeff Yoon <jeffyoon@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
-
Nick Burris authored
Add the header icon and progress bar to the secure payment confirmation dialog. Before this patch, the header icon was a property of the model. Since the model lives in //components, but the icon comes from //chrome, it's awkward for the controller to get the icon from the view just to pass a pointer to the model for the view to dereference later. See patch set 3 for what this looks like. Since the icon is specific to the SecurePaymentConfirmationDialogView implementation anyway, this patch removes the icon from the model and keeps the logic local to the view. Bug: 1110322 Change-Id: I8681bc00c4d48d1b98f3c939f920b5ea44f0ff02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358821 Commit-Queue: Nick Burris <nburris@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#799873}
-
Michael Tang authored
Change-Id: Id3868d6e9fd854a0c7fd34868101227dd6adb540 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363362 Commit-Queue: Michael Tang <tangm@microsoft.com> Commit-Queue: Mike Reed <reed@google.com> Reviewed-by:
Mike Reed <reed@google.com> Reviewed-by:
Calder Kitagawa <ckitagawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#799872}
-
Monica Basta authored
Screenshot: https://drive.google.com/file/d/1hJB_rmXQ13zfwdMI-we-LoVPlOy9Fspt/view?usp=sharing Bug: 1115056 Change-Id: I324dfca8105e439aeb1d29c2a7a6130b9cf5af1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362753 Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#799871}
-
Domenic Denicola authored
As part of this, we fix a bug in send-header-page-script.mjs which was not correctly reading the "send-loaded-message" query parameter. In the less-comprehensive tests that were there previously, the buggy code still worked, but these new tests brought out the problem. Bug: 1042415 Change-Id: Id34c627d1d7fdd41727f3db362ada25a6651498f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364172 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#799870}
-
Adam Langley authored
This change plumbs a NetworkContext for WebSocket creation into the |FidoDiscoveryFactory| when caBLEv2 is enabled. BUG=1002262 Change-Id: I0fabe9642c785669c75516207bf4d8f2f8c147e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340389 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a64aed23..afdbedf7 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I9f7803630d49074644892a4dc5ecd12add7e42a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362635Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#799868}
-
Karandeep Bhatia authored
in hacker_case. When the type name is in hacker_case, generate HackerCase as the class name instead of Hacker_case. BUG=1113513 Change-Id: Ie94419b088a8c5de9434a2f6bcb962ca0a1a20cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360508 Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#799867}
-
Claude van der Merwe authored
Bug: 1117619 Change-Id: Ied3c92682a776d83b27e848b7496151fd2618e19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364079 Commit-Queue: Claude van der Merwe <cvandermerwe@google.com> Reviewed-by:
Jon Mann <jonmann@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#799866}
-
Henrique Nakashima authored
Failures are not very informative without the stderr output. For example: https://logs.chromium.org/logs/chrome/buildbucket/cr-buildbucket.appspot.com/8871613511001211808/+/steps/Generate_dependency_graph_data/0/stdout Bug: 1111056 Change-Id: I50142bd4d2c8fa9ee43dea572359c2c331f91186 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363699 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#799865}
-
Mark Yacoub authored
When getting displays, if an update for a Drm Display has an invalid connector, do not create a Display Snapshot for it. This prevents attempts to use displays with invalid connectors. Bug: 1105427 Change-Id: Id3422686b019942e924d3e98172394f6caa23eed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362442 Commit-Queue: Mark Yacoub <markyacoub@google.com> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#799864}
-
Camille Lamy authored
This CL allows reporting browsing context group switches triggered by redirects and updates the reports sent in this case to the latest version of the spec PR (https://github.com/whatwg/html/pull/5518). Since the status of COOP was becoming hard to track, I moved it to its own class for better encapsulation. Bug: 1059303 Change-Id: Ifafb23073301bd05cd9ce83fdb0b748c28e8a51f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352880 Commit-Queue: Camille Lamy <clamy@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#799863}
-
Zhenyao Mo authored
On Windows, if we call swap chain's Present1 with damage rect info, even the damage rect info indicates full damage, the chance of Chrome's back buffer being promoted into an overlays are much lower. If we want to consistently Chrome's BGRA back buffer to an overlay, we have to always call Present which doesn't take damage rect info, indicating full damage. I measured some common use case, and their percentage of frames being promoted to overlays are as below: - Google Meet (5 person, 2x2): 97.8% - wikipedia: 80.5% - a story sharing site: 77.2% - gmail (reading a few emails and then compose one): 61.3% - Google speadsheet: 78.2% - Google photos: 95.5% If we promote a frame to overlay, then we save an extra copy (DWM doesn't need to copy chrome's back buffer into OS's back buffer). If we fail to promote a frame to overlay and it's partial damage, now we use full damage, so at worst we do an extra copy. So as far as we promote more than 50% frames to overlays, there is performance gains. For use cases where performance is critical, like Google Meet, or when we scroll, we get almost 100% promotion, so we get maximum performance gain. Besides, always use full damage simplifies logic quite a bit. The UMA "GPU.DirectComposition.CompositionMode.MainBuffer" will show us if this is a good decision by collecting overlay promotion percentage from the wild. BUG=1117185 TEST=manual R=sunnyps@chromium.org Change-Id: I12d927f472652f17e146debc83e40d9f40a1b950 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363771 Commit-Queue: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#799862}
-
Daniel Libby authored
With cc-based directly composited images, we previously made a decision to not directly composite images if raster scale and aspect ratio resulted in filling in tiles that end up truncated when scaled back up in the display compositor, based on the shared quad state transform. However, because we don't apply directly composited images in cases where we used to, we can end up using more tile memory. The example page from bug 1111621 has over a hundred 1572 x 861 size image layers, but the image is only 16x16. If we don't directly composite, we run into the upper limits of allowed tile memory, and tiles start disappearing (are dropped) on re-draw. Unfortunately, as raster scale can only be expressed as a single scaler value, there no way to have tile size match the intrinsic image size when the aspect ratio of the layer and image are different (the previous approach was able to do this by encoding x and y scales in the layer transform - however, our detection of directly composited images happens later in the pipeline at a time where we cannot alter the structure of the transform property tree). This change removes the restriction (and the associated DCHECK validating it) when the raster scale is less than 0.1, in favor of applying directly composited images to save memory, over the minor changes in rendering that may result. The difference in rendering is that the last row/column of scaled pixels will only be partially filled, and those pixels will be stretched and clipped at the layer bounds. Bug: 1111621 Change-Id: I15b83a9f33df72f40ece087ade3e82a513aa596e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355831Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Daniel Libby <dlibby@microsoft.com> Cr-Commit-Position: refs/heads/master@{#799861}
-
Yu Han authored
Prior to this CL, dark mode tests were coded one by one manually. However, there are already a number of tests that test the appearance of form controls. So we should leverage the existing tests to verify form controls dark mode. This CL adds fast/forms/color-scheme to the dark mode virtual TestSuite. The directory has a good coverage for all form controls. To do so requires modifying existing tests to include the <meta name="color-scheme" content="light dark"> so that they support both light and dark mode. In addition, I went through all the rebaselined expected images and mark the ones that doesn't match dark mode spec in the TestExpectation file, along with a bug number. The failed rebaseline images are not include in this CL. The CL also removes the duplicated tests in the dark-color-scheme directory that have been already tested in the fast/form/color-scheme directory. In the follow on CL, I'll work through these failed cases. Bug: 929098 Change-Id: Ic4e6c30c51051a7e5e009c733da9bbe3c6c98c32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353091Reviewed-by:
-
Karandeep Bhatia authored
Platform app resources should never load in a tab. However currently, it's possible for browser initiated navigations to bypass that restriction on redirects. Fix that by adding an explicit check in ExtensionNavigationThrottle to ensure that navigations to platform app resources only succeed in certain cases. Also, add a regression test. BUG=1110551 Change-Id: If11f7f1f9649c8a3f7960cd51d18ef902ac272d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347086 Auto-Submit: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
-
Jianhui Dai authored
Set default bitrate according to video resolution Change-Id: I0f00af6b8900af71c27701c7f91c393f63d36b82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347399Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#799858}
-
Marijn Kruisselbrink authored
Renames self.getOriginPrivateDirector() to navigator.storage.getDirectory(), following the changes in https://github.com/WICG/native-file-system/pull/217. Change-Id: Ie993c24b56ffdf369bb87ed03eb786f458e50ad5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363567 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Auto-Submit: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#799857}
-
Anastasia Helfinstein authored
Switch Access has been experiencing performance issues on moderate to large webpages. A large portion of this is due to the inefficiencies of its traversal of the automation tree, recalculating the same values sometimes hundreds of times for nodes deep in the tree. This change utilizes techniques from dynamic programming to persist intermediate values for continued use, reducing the asymptotic worst- case run time from exponential in the depth of the node to linear in the number of nodes in the subtree. AX-Relnotes: n/a. Bug: 1109970 Change-Id: I61368292f2e731245e4f733c2883b86293d8a74c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360340Reviewed-by:
Abigail Klein <abigailbklein@google.com> Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Cr-Commit-Position: refs/heads/master@{#799856}
-
Harkiran Bolaria authored
Add callback to handle specialized behavior when tasks are posted. To be filled with IPC tracking for cached frames in a subsequent Cl. Bug: 1110344 Change-Id: I7a053747082782a0c2f6c44a7b77aeb6f9694d96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316781 Commit-Queue: Harkiran Bolaria <hbolaria@google.com> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#799855}
-
Eric Lawrence authored
Previously, the loader would unconditionally clear the request's Content-Type header upon any redirect. This would cause the value to be lost upon reloading a page that loaded through a HTTP/307 or HTTP/308 redirect that preserved the POST body. Bug: 860546 Change-Id: Id5af5b03a997b8fa185af7ad3245cec5952b3b92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363661Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Eric Lawrence [MSFT] <ericlaw@microsoft.com> Cr-Commit-Position: refs/heads/master@{#799854}
-
Justin DeWitt authored
Bug: 1119485 Change-Id: Ic85c4ae86c8bdc287e724f3bf403a7942aa1c337 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364023Reviewed-by:
Cathy Li <chili@chromium.org> Commit-Queue: Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#799853}
-
Nela Kaczmarek authored
This change covers the implementation of AffiliationService, the AffiliationFetcherDelegate interface implementation and unit tests. It prefetches data with a help of AffiliationFetcher and provides an API to get change password urls for requested origin. This change includes only preparing data for prefetch without processing the response. Bug: 1108279 Change-Id: I3f47a3b1f7c0b99726b4107d484387a77b1345b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332604 Commit-Queue: Nela Kaczmarek <nelakaczmarek@google.com> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#799852}
-
Renato Silva authored
PIN auto submit is only available on Chrome OS and the feature should be in the chromeos namespace. Bug: 1075994 Change-Id: Idd199abb2baf6ac88d10762e22735fe42d46e656 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362965 Commit-Queue: Renato Silva <rrsilva@google.com> Reviewed-by:
-
