- 13 Nov, 2018 40 commits
-
-
Fredrik Hubinette authored
Turns out that when a video is tagged as RGB, they really mean that the Y channel contains green, Cr contains red, and Cb contains blue. (According to ISO 23001-8:2016) Bug: 901664 Change-Id: I468327252389dc2468020f23a912129fdc55574a Reviewed-on: https://chromium-review.googlesource.com/c/1321582Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Fredrik Hubinette <hubbe@chromium.org> Cr-Commit-Position: refs/heads/master@{#607442}
-
Sahel Sharify authored
JS_SCROLL_TEXT_ONLY and JS_SCROLL_200_LAYER_GRID both add event listeners to the document that preventDefault wheel/touch events and call JS scrolling. The tests regressed after landing the following cl: https://chromium-review.googlesource.com/1183538 This is because with passive document level event listeners interventions the wheel/mousewheel and touchstart/touchmove event listeners on a document level target are treated as passive if not requested otherwise. This cl changes the event listeners in both tests to passive:false to make sure that they actually prevent scrolling. Bug: 877586 Change-Id: I25fb5c0563534b1d67f124bd43272d02d849fa23 Reviewed-on: https://chromium-review.googlesource.com/c/1329447 Commit-Queue: Sahel Sharify <sahel@chromium.org> Reviewed-by:
Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#607441}
-
Yiming Zhou authored
The Captured Sites Autofill tests start with a default saved credit card. Individual test recipes may overwrite this default with a specified credit card. Today, there is a bug that prevents a recipe from overwriting the default card owner by first name and last name. When doing an override, the framework triggers a DCHECK in the saved credit card code that asserts the credit card name is empty. This fix address the DCHECK by setting the default credit card owner name to an empty string before overwriting it. Fixing an autofill profile setup bug in test. The Captured Sites Autofill Tests starts with a default saved credit card. A test recipe may override the default card with its own credit card info. Today, a bug exists in the framework that prevents the recipe from overriding the credit card owner by first name and last name. The bug breaks a DCHECK assertion in the saved credit card code. This fix addresses the assertion by setting the credit card owner name to empty before overriding the recipe specified credit card name. Bug: 902492 Change-Id: Iec86496bf408400b60c2a7183b15ef0bd7dfc14f Reviewed-on: https://chromium-review.googlesource.com/c/1332694 Commit-Queue: Yiming Zhou <uwyiming@google.com> Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#607440}
-
Ben Pastene authored
TBR=jbudorick Bug: 880623 Change-Id: Ibcda8cadf0e6b00f1f50ade12c06922a2f5f3bda Reviewed-on: https://chromium-review.googlesource.com/c/1332610Reviewed-by:
Ben Pastene <bpastene@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#607439}
-
Andres Calderon Jaramillo authored
This CL adds a method to ClientTransferCache that allows the client to get a ClientDiscardableHandle without ClientTransferCache::Client::IssueCreateTransferCacheEntry getting called so that the client can essentially start a locked entry but trigger the creation of the service-side entry using some other mechanism, e.g., an IPC message. This is needed for hardware-accelerated image decodes because the decode will be started by sending an IPC message, and the service-side cache entry shouldn't be created until the decode is done, so the usual flow of triggering the cache entry creation using the command buffer won't do. Additionally, some documentation is updated. Bug: 868400 Change-Id: I24cf9b921b8a0ea2e7038c1801f2b7c36fda1927 Reviewed-on: https://chromium-review.googlesource.com/c/1328184Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#607438}
-
Liquan(Max) Gu authored
UserTiming L3 will change the L2 API in certain cases. These cases are described in http://bit.ly/2SZqAKz. We want to investigate which and how much various use cases will be impacted by the introduction of L3 API. So we write this CL to do the investigation. In particular, we will have two UMA histograms to count the input types of the performance.measure method in the wild. The input types are to be divided into the following groups: 1. number 2. sub-groups defined by navigation timing names 3. object 4. unprovided 5. undefined or null 6. others We used to have a similar histogram before (CL/769932), which we used to collected 2,3,6. Though we had removed it, it defined some of the enums that we reuse. Change-Id: Idfb1d7fc761189563f55e5f5ba7c493e94e5e83a Reviewed-on: https://chromium-review.googlesource.com/c/1320012 Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org> Reviewed-by:
Nicolás Peña Moreno <npm@chromium.org> Reviewed-by:
-
James Hawkins authored
Bug: 899324 Test: none Original change description: > CryptAuth: Remove unused ConnectionFinder. > > Bug: 899324 > Test: none > Change-Id: I30f07136ac7c3ed3ac49b678e5f45d250fcbe65f > Reviewed-on: https://chromium-review.googlesource.com/c/1331573 > Reviewed-by: Jeremy Klein <jlklein@chromium.org> > Commit-Queue: James Hawkins <jhawkins@chromium.org> > Cr-Commit-Position: refs/heads/master@{#607302} R=hansberry@chromium.org Change-Id: Ia14bbe45b5b76a94c79aea5c4b687695df843163 Reviewed-on: https://chromium-review.googlesource.com/c/1333109 Commit-Queue: James Hawkins <jhawkins@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#607436}
-
Eric Roman authored
The rule should just match simple hostnames, and previously was confused (both in implementation and consumers) into acting like a bypass for localhost. The compatibility risk of changing its meaning (given this may be serialized in preferences or used by extensions) is low, since a previous change added implicit bypass on localhost. Hence the overall impact of fixing <local> now is just that IPv6 IP addresses are no longer bypassed. That IPv6 literals were being bypassed by the check was unexpected and a bug. Bug: 902579, 902418 Change-Id: I5937048e3f927c66668e39e4ceb589ef8516e874 Reviewed-on: https://chromium-review.googlesource.com/c/1320849 Commit-Queue: Eric Roman <eroman@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#607435}
-
Hector Carmona authored
Bug: 901480 Change-Id: I8b85878f855ee470bf3ae62ce98ba9317f20dcef Reviewed-on: https://chromium-review.googlesource.com/c/1332702Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#607434}
-
Yiming Zhou authored
The Captured Sites Automation Framework interacts with real-life pages. By default, the framework expects that a page element to be visible, enabled and on top of the page. In the Chrome Autofill tests, some sites break this expection. Some address or credit card fields are hidden inputs, and some customized combo boxes have a selection element hide behind sibling span elements. Today, the test framework fails when encountering these exceptions. The Action Recorder Extension already logs the visibility state of each element it records. This change takes account of the element visibility state information inside the recipe files. Bug: 847905 Change-Id: Ibed7beef309d1bfbfb285cae02d026e172da8fb4 Reviewed-on: https://chromium-review.googlesource.com/c/1332701Reviewed-by:
-
Xida Chen authored
This CL implements the idea of Phase 1 described in this doc: https://docs.google.com/document/d/1bSv_qNsLLnpXImuH7sHa6D3R_0GdDYkTiNjxso8Rgxo/edit# The idea to to let the browser use compositor-computed touch action, to decide whether a gesture event should be allowed or dropped, if the effective touch action from the main thread is not known yet. This CL makes it work with gestures other than PinchBegin / Update / End, as those are more complex. Bug: 772130 Change-Id: I92af471f22c76080755d34925069fdf3a4f448c7 Reviewed-on: https://chromium-review.googlesource.com/c/1318060 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#607432}
-
Mitsuru Oshima authored
if a) the mouse event is not captured, or b) even if captured, it's considered a plain click. see bug for repro step. Bug: 900614 Test: updated tests to match this expectation. Also tested manually. Change-Id: I2668fa5692a0e4381e72d2d22bf5543914a8ca34 Reviewed-on: https://chromium-review.googlesource.com/c/1328709 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Vladislav Kaznacheev <kaznacheev@chromium.org> Cr-Commit-Position: refs/heads/master@{#607431}
-
Eric Roman authored
Bug: 904598 Change-Id: If760623af28051df78e1209df29e412190eb70b6 Reviewed-on: https://chromium-review.googlesource.com/c/1332290Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/ff9427fb8a90..22d2394b3274 git log ff9427fb8a90..22d2394b3274 --date=short --no-merges --format='%ad %ae %s' 2018-11-12 primiano@google.com Merge "Fix gcc build" Created with: gclient setdep -r src/third_party/perfetto@22d2394b3274 The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll 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. TBR=perfetto-bugs@google.com Change-Id: I25047678629ce14f2af9e4fa88d97a4308f2a4ee Reviewed-on: https://chromium-review.googlesource.com/c/1332167Reviewed-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@{#607429}
-
Corentin Wallez authored
https://dawn.googlesource.com/dawn.git/+log/2960ec33667a..597e1587b4bf $ git log 2960ec336..597e1587b --date=short --no-merges --format='%ad %ae %s' 2018-11-12 cwallez Build fuzzer tests in standalone builds too. 2018-11-12 cwallez Add a fuzzer for the wire server and Dawn frontend 2018-11-12 cwallez Fix compilation of SPIRV-Cross fuzzers in Chromium 2018-11-12 rharrison Add fuzzers for SPIRV-Cross 2018-11-12 cwallez Suppress tests failing on D3D12 2018-11-12 cwallez WireCmd: error out if "self" is null. 2018-11-09 jiawei.shao Skip BindGroupTests.ReusedUBO and UBOSamplerAndTexture on Metal 2018-11-07 cwallez Validate that mapped buffers aren't used in submits. 2018-11-07 cwallez Add tests for pass resource usage validation 2018-11-07 jiawei.shao Add entry points for creating a cube map/cube map array texture view 2018-11-04 senorblanco MSC build fix. Created with: roll-dep src/third_party/dawn TBR=kainino@chromium.org Change-Id: I7e27100d2396478bdbaf24dbca9cd1ab64c70781 Reviewed-on: https://chromium-review.googlesource.com/c/1331403Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> Cr-Commit-Position: refs/heads/master@{#607428}
-
Robert Ogden authored
Adds Lite Page Server Previews to DetermineAllowedPreviews and DetermineCommitted. For now, the preview is always allowed if the feature is enabled and is committed if the URL matches. This intentionally leaves an open question about whether more logic in the NavigationThrottle can/should be moved into the DeciderImpl. The biggest part of this change is moving the URL checking logic to the previews component and adding additional helper functions there. Bug: 898557 Change-Id: Iccc0b672eeedbe23942f4d17f6afd214426372a9 Reviewed-on: https://chromium-review.googlesource.com/c/1323800 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Cr-Commit-Position: refs/heads/master@{#607427}
-
rbpotter authored
Only applies to the new print preview. Bug: 904003 Change-Id: I3992ee0f196b86617c27b7cdb15cc5242b2e9690 Reviewed-on: https://chromium-review.googlesource.com/c/1330989Reviewed-by:
-
Chih-Yu Huang authored
The corruption issue is fixed. We enable the VP8 for Vaapi VEA again. BUG=b:111781384 TEST=Run apprtc with VP8 format and check Vaapi VEA is used and no corruption is found. 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: Ie9b5a90d4b8b8a1747a8a4cd6458521d7d3b7729 Reviewed-on: https://chromium-review.googlesource.com/c/1256388Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Pawel Osciak <posciak@chromium.org> Commit-Queue: Chih-Yu Huang <akahuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#607425}
-
Shawn Gallea authored
EXO: Moved zcr_notification_shell_v1_interface into another file, to be followed by refactoring of more protocols. Bug: 896710 Test: Compiled on ChromeOS. Change-Id: I0884132357f8acadb8d5659b9330abae8acc7cd1 Reviewed-on: https://chromium-review.googlesource.com/c/1302861 Commit-Queue: Shawn Gallea <sagallea@google.com> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#607424}
-
Jerome Jiang authored
https://chromium.googlesource.com/webm/libvpx.git/+log/c66fe1a8930c..4a8c24874450 $ git log c66fe1a89..4a8c24874 --date=short --no-merges --format='%ad %ae %s' 2018-11-09 jianj vp8: Init buffers and pred arrays for mt after allocation. 2018-11-09 yaowu Refactor common code in RDMULT computation Created with: roll-dep src/third_party/libvpx/source/libvpx R=johannkoenig@google.com BUG=902691 Change-Id: Ic3b3eebd592d8ed0bb764fb358633d15e3ebbff6 Reviewed-on: https://chromium-review.googlesource.com/c/1330937Reviewed-by:
Johann Koenig <johannkoenig@google.com> Commit-Queue: Jerome Jiang <jianj@google.com> Cr-Commit-Position: refs/heads/master@{#607423}
-
Jinsuk Kim authored
This is to break the TabObserver present in Tab class down to feature level and eventually remove it. Theme color used for Tab is managed via Tab UserData. Relevant Tab methods also got migrated. Bug: 877878 Change-Id: If120beaaa370d07f6855ab666e380cc2318e945a Reviewed-on: https://chromium-review.googlesource.com/c/1304038 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#607422}
-
Hao Zhang authored
These lines should be imported which caused a bug. https://chromium-review.googlesource.com/c/chromium/src/+/1300314/39/components/autofill/core/browser/form_data_importer.cc The line 445 to 449 should be removed and the line 451 to 455 is the right place. They shouldn't be kept both from this patch. https://chromium-review.googlesource.com/c/chromium/src/+/1300314/18 It will auto-reject offering upload of expiration date fix flow cards as long as you have 1+ server cards on the device. Bug: 899057 Change-Id: I55504fce3fe67ef57ad772c73e5026e793d3f033 Reviewed-on: https://chromium-review.googlesource.com/c/1329847 Commit-Queue: Hao Zhang <hozhng@google.com> Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
-
Erik Chen authored
The hermetic mac toolchain currently uses Xcode 8. Xcode 8 does not run on macOS 10.14+. Bug: 904400 Change-Id: I79afe5563631aac5c608c6ef57b594ae5de81e73 Reviewed-on: https://chromium-review.googlesource.com/c/1331907 Commit-Queue: Erik Chen <erikchen@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#607420}
-
Erik Luo authored
The main ElementsTreeOutline in ElementsPanel is wired to DOMModel updates, but ETOutlines in Console / elsewhere are not. In the unwired case, nodes in the tree may have null `children()`. This can result in internal errors. Bug: 896445 Change-Id: Ie903fdddb76b31a5460ce2dd4b753be7ba7eeb56 Reviewed-on: https://chromium-review.googlesource.com/c/1286860Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Erik Luo <luoe@chromium.org> Cr-Commit-Position: refs/heads/master@{#607419}
-
Avi Drissman authored
This reverts commit 74d2ba14. Reason for revert: This breaks the dialog. The beforeunload dialog *must* block all of Chrome. MacViews does not have the modality code do to so yet. If you implement that modality you may reland this. Original change's description: > MacViews: Remove JavaScriptAppModalDialogCocoa > > Move from using Cocoa to using Views. The Cocoa version was was causing > problems with app exit dialogs showing up in the wrong process in > RemoteMacViews. This issue was solved by the views version. > > Bug: 898604 > Change-Id: I30bd1e543fa98a1503d80b4ad3947f676eb5e0c6 > Reviewed-on: https://chromium-review.googlesource.com/c/1298300 > Commit-Queue: ccameron <ccameron@chromium.org> > Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> > Cr-Commit-Position: refs/heads/master@{#605898} TBR=ellyjones@chromium.org,ccameron@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 898604 Change-Id: I5ec60bc8490083175092da9b4f2d0a2167aac18a Reviewed-on: https://chromium-review.googlesource.com/c/1331831Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#607418}
-
Josh Horwich authored
Update the ARC opt-in strings with minor tweaks, and use specific strings for child-account scenarios. Also remove the ability for a device owner to toggle the usage & diagnostics collection setting from within ARC opt-in flow. Bug: 805304 Test: Run ARC opt-in during new-user setup (OOBE) Test: Run ARC opt-in for existing user ('in-product') Change-Id: Ic8dcbbaddd5b690baea469b4688d38f3c2378a98 Reviewed-on: https://chromium-review.googlesource.com/c/1313764Reviewed-by:Achuith Bhandarkar <achuith@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Commit-Queue: Josh Horwich <jhorwich@chromium.org> Cr-Commit-Position: refs/heads/master@{#607417}
-
Tarun Bansal authored
Change-Id: Ib7a70bf6d4921aafdd3786f7402f79547cee70de Bug: 903978 TBR: ryansturm@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/1330338Reviewed-by:
-
Eric Aleshire authored
The type action allows for text to be typed into a field, enabling more autofill scenarios, and additionally enabling for password manager automation, which I am working on extending autofill automation to support. There are a great deal many more flows needed for password automation compared to autofill (i.e. save password on login, don't save password on login, update password on change, etc), and "save password" is just the first of them - but this change lays important groundwork by adding AX IDs to the confirm infobar so that automation can tap them. Change-Id: I5368fabfbc1a450341969b63936960dce2de6246 Reviewed-on: https://chromium-review.googlesource.com/c/1332008 Commit-Queue: ericale <ericale@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#607415}
-
Jared Saul authored
When a card has max strikes on desktop, instead of showing the offer-to-save bubble, only the omnibox icon is shown. This metric tracks these occurrences. Bug: 884817 Change-Id: I43f5cf0b1c9d6a3431790e8a2788bbf489fcdbe6 Reviewed-on: https://chromium-review.googlesource.com/c/1330898Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Commit-Queue: Jared Saul <jsaul@google.com> Cr-Commit-Position: refs/heads/master@{#607414}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/85604c46..d5f26302 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I3514d813ee12fb0cbcec3ec005db1b73950e59da Reviewed-on: https://chromium-review.googlesource.com/c/1331575Reviewed-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@{#607413}
-
Koji Ishii authored
This patch impements inline fragmentation for BiDi. When BiDi reorder fragments an inline box; e.g., <span>T1 T2</span>T3 becomes after BiDi reorder: <span>T1</span> T3 <span>T2</span> this change creates two box fragments, one for T1 and another for T2. Unfortunately, one test starts failing: fast/css/css-properties-position-relative-as-parent-fixed.html In this test, when absolute/fixed positioned container is fragmented, the position becomes incorrect. As far as I checked, the fragment tree looks correct, so I suppose computing positioned objects get confused by multiple fragments for a LayoutObject within a line. Bug: 636993 Change-Id: Id1055e411e7cb59a8c8e731e5ad7c74b0c7fd246 Reviewed-on: https://chromium-review.googlesource.com/c/1323989 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#607412}
-
Sadrul Habib Chowdhury authored
BUG=894440 Change-Id: I0757af5f6a2058d0c98b68ff1e71c3083a1a76f2 Reviewed-on: https://chromium-review.googlesource.com/c/1332249 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#607411}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/49e1239f94fe..fd1fd279a353 git log 49e1239f94fe..fd1fd279a353 --date=short --no-merges --format='%ad %ae %s' 2018-11-12 scroggo@google.com Remove unused exposedInAndroidJavaAPI 2018-11-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 635c9b33fe7c..1147fc2a5dac (1 commits) 2018-11-12 rmistry@google.com Remove usage of EnsureCQIncludeTrybotsAreAdded 2018-11-12 herb@google.com Move adding a glyph to a subRun from Run to SubRun 2018-11-12 reed@google.com New plan -- aa and lcd DO belong on SkFont 2018-11-12 herb@google.com Make SubRunInfo a subclass of GrTextBlob and rename to SubRun 2018-11-12 halcanary@google.com SkPDF: fix BUG:chromium:900562 2018-11-12 mtklein@google.com Revert "remove old name for SkCodec::kNoFrame" 2018-11-12 mtklein@google.com Revert "put kNone back too" 2018-11-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 50bf0429394d..48f63f90f6f3 (1 commits) Created with: gclient setdep -r src/third_party/skia@fd1fd279a353 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll 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:android_optional_gpu_tests_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;master.tryserver.blink:linux_trusty_blink_rel TBR=rmistry@chromium.org Change-Id: I1826586602f3f80aed3014f4c315e6c70548bde7 Reviewed-on: https://chromium-review.googlesource.com/c/1332609Reviewed-by:
-
Malay Keshav authored
This patch is a temporary fix to reduce the delay before occlusion tracker is unpaused after overview mode is dismissed. It is a temporary fix to load web contents immediately instead of waiting on the occlusion tracker for 5 seconds. Bug: 904617 Change-Id: Ib1d4957638965fd34ffa719c057d234a058d7e08 Component: Window selector controller Reviewed-on: https://chromium-review.googlesource.com/c/1332778Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Cr-Commit-Position: refs/heads/master@{#607409}
-
Mike Wasserman authored
Use the ash::Shell aura::Env in single-process mash ui_devtools. Keep a TODO for initializing ui_devtools in Ash for multi-process Mash. Encapsulate server init, and the switch and port definitions. Bug: 896977 Test: ui_devtools works well on Chrome OS single-process Mash. Change-Id: I3cc285d5f8ee465d45795a3521e7e4eafa354414 Reviewed-on: https://chromium-review.googlesource.com/c/1324373 Commit-Queue: Michael Wasserman <msw@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#607408}
-
Shakti Sahu authored
Change-Id: I3acdd151cb7330eb62b9f8ba484aa47483fb6dee Reviewed-on: https://chromium-review.googlesource.com/c/1330750 Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#607407}
-
Ehsan Karamad authored
This API should not be public, because: 1- BrowserPluginGuest is internal to content. 2- The use cases are all within content/ - so it does not need to be in the WebContents interface. Bug: None Change-Id: Ia0206bb305e851742a7d71e64882c8fdf51a53b2 Reviewed-on: https://chromium-review.googlesource.com/c/1329302Reviewed-by:
Ehsan Karamad <ekaramad@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#607406}
-
Jacob Dufault authored
Bug: 898696 Change-Id: I0d9dd064a69cc54f8e983f0447a2388024bb5745 Reviewed-on: https://chromium-review.googlesource.com/c/1311127Reviewed-by:
Stefan Kuhne <skuhne@chromium.org> Commit-Queue: Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#607405}
-
Robert Ogden authored
time_before_main_frame_request_sent is the best estimate for the amount of time spent following redirects and any computational overhead in the browser. Bug: 902063 Change-Id: Ie958cf6b749d00cb2bb47d0d1a7d0434b04c3788 Reviewed-on: https://chromium-review.googlesource.com/c/1330687 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Reviewed-by:
-
Ted Choc authored
BUG=898522 Change-Id: Ifd8c5748dd46e0a8417f9cd1bd80cf7f5a115965 Reviewed-on: https://chromium-review.googlesource.com/c/1330704 Commit-Queue: Ted Choc <tedchoc@chromium.org> Reviewed-by:
Pedro Amaral <amaralp@chromium.org> Cr-Commit-Position: refs/heads/master@{#607403}
-
