- 19 Jun, 2020 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e7ae237eb9e9..84fb97ba9452 2020-06-19 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from 99651228b238 to 545d158a2ff9 (2 revisions) 2020-06-19 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 7a1d99d0be42 to eb6824408d08 (3 revisions) 2020-06-19 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Loader from 24a17f5fe4ef to 7942c0830780 (1 revision) 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 courtneygo@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/+doc/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;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: courtneygo@google.com Change-Id: I3fd23e39ecb467344088f6845141d47d4e524c41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253571Reviewed-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@{#780257}
-
Victor Hugo Vianna Silva authored
This is a reland of 39818338 Reason for reland: The original CL missed .js extensions in two of its imports. When the new dialog started being used in crrev.com/c/2246157 this caused several tests to fail. TBR=aee@chromium.org Original change's description: > [b4p/Settings] Add dialog for removing duplicated passwords > > For a b4p user, in case some password has copies attached both to the > device and the Google Account, attempting to delete it should show a > dialog that allows selecting which copies to remove. This CL implements > this dialog but does not yet wire it in. Some details in the UI are left > for future CLs, such as the user avatar and displaying the website > associated with the password to be deleted. Note RemovePasswordBehavior > is not used here, for reasons that are better explained in > crrev.com/c/2246157. > > Screenshot of implementation: > https://screenshot.googleplex.com/hZnTiuy80tL > > Screenshot of mock: > https://screenshot.googleplex.com/pGV0iMTQBxw > > Bug: 1049141 > Change-Id: I50ca0e5bfc99dbc76c12c345c00f82788bbc377c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2248180 > Commit-Queue: Victor Vianna <victorvianna@google.com> > Reviewed-by: Friedrich [CET] <fhorschig@chromium.org> > Reviewed-by: Esmael Elmoslimany <aee@chromium.org> > Cr-Commit-Position: refs/heads/master@{#779743} Bug: 1049141 Change-Id: I39cc548744d7d290b98de3376b96eb7c5472efae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252246 Commit-Queue: Victor Vianna <victorvianna@google.com> Reviewed-by:
Friedrich [CET] <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#780256}
-
Caitlin Fischer authored
As described in more detail here (crbug.com/1096582), this test seems to cause testSingleSyncSignout and testSingleDisableSync to be flaky. Added a bug to re-enable testRegularPlusIncognito. Bug: 1094932 Change-Id: I87ce718f3d533f5684d97ff5aadb6f8cf8c9ba2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252638Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#780255}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1592545853-4aad13dd3d5b31e6b22212a49c45cb09e0a49e05.profdata to chrome-win64-master-1592557014-0fc653e79e8d54496b6e208718c321ae21bb710d.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC jeffyoon@google.com,liaoyuke@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/+doc/master/autoroll/README.md Cq-Include-Trybots: chrome/try:win64-chrome Tbr: jeffyoon@google.com,liaoyuke@google.com Change-Id: I6958144b98aa99629e5b26628b97c9328e361b3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253572Reviewed-by:
-
Maksim Sisov authored
It doesn't seem to be used at all. Thus, remove that. Change-Id: I5aba62543107efe4cc719d9e8168ac1f7f7c38db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250112 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#780253}
-
Caitlin Fischer authored
Original description: Replace GzipUncompress calls with DecodeLogDataToProto. Also, remove "ukm::", where applicable, from ukm_service_unittest.cc Bug: 1086910 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222521Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Original-Commit-Position: refs/heads/master@{#777137} Change-Id: Ia59944a291b095755f5b9cb889f6c16b5388a704 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2248750 Cr-Commit-Position: refs/heads/master@{#780252}
-
Hans Wennborg authored
Add direct includes for things provided transitively by logging.h (or by other headers including logging.h). This is in preparation for cleaning up unnecessary includes of logging.h in header files (so if something depends on logging.h, it needs include it explicitly), and for when logging.h no longer includes check.h, check_op.h, and notreached.h. TBR=kinuko Bug: 1031540 Change-Id: I302009b875c8cdad1465cb72331fdd22dd33adeb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249674 Commit-Queue: Hans Wennborg <hans@chromium.org> Auto-Submit: Hans Wennborg <hans@chromium.org> Reviewed-by:
Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#780251}
-
Yuki Shiino authored
Bug: 839389 Change-Id: I521397e8ea474bdf7a66d2b28d38508e06fe389c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251525Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#780250}
-
Alexander Hendrich authored
This reverts commit 88854e15. Reason for revert: replaced with new enterprise.networkingAttributes API Change-Id: I3e1553f3aad053a2c7780d8e1c1f4498c759ecc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250062Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#780249}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0ec56611a754..f2f2cf0206e5 2020-06-19 patrick.brosset@microsoft.com Split computed-pane-properties_tests.ts to avoid timeouts 2020-06-19 wolfi@chromium.org Add FrameManager to aggregate info about ResourceTreeFrames 2020-06-19 mathias@chromium.org Force-replace Windows-style path separators for stylelint 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/+doc/master/autoroll/README.md Bug: chromium:1083142,chromium:1093247,chromium:1096439 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I9e96dbd4bd62bba7e0657df41ed35368888a0f68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253782Reviewed-by:
-
arthursonzogni authored
It has been decided to monitor only the attributes marked as CrossOrigin instead of every attributes. Updating the tests accordingly. Along the way some improvements. Bug: chromium:1090273 Change-Id: Iecd0bd478ab348f75f3835105db5bdca9edcc39b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252339 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Pâris Meuleman <pmeuleman@chromium.org> Cr-Commit-Position: refs/heads/master@{#780247}
-
Nektarios Paisios authored
This is a reland of 41e56b19 Dealt with crashes https://chromium.googlesource.com/chromium/src.git/+/a6705f429d0215f809bc98715c4a69aa0f3b6ca3 An occasional infinite loop was identified and fixed in AXPosition, between CreateParentPosition and AtStartOfLine methods. Original change's description: > Consolidated some text helper methods in AXNode > > This patch is a second precursor to a more substantial change that > would move hypertext computation to AXNode from AXPlatformNodeBase which will > in turn open the way for AXNodePosition to be merged with AXPosition and > for Views to be exposed as a tree of AXNodes. > See https://chromium-review.googlesource.com/2150294 > > Currently, we have multiple methods that compute inner text, IsLeaf and IsChildOfLeaf > one set in BrowserAccessibility and another in AXPlatformNodeBase. > We want to centralize all platform independent utility methods in AXNode and AXNodeData. > > There was some confusion in the existing codebase regarding what should be included in inner text. > Some code assumed that the name attribute of a leaf node could not be included, unless it was derived from its contents, > or its placeholder in the case of a text field. > Other parts of the codebase were more relaxed about this requirement. > > This patch adopts this requirement for the whole codebase, because the definition of inner text should only include visible > text that is present inside the node itself, but not text derived from an attribute, e.g. an ARIA label. > This is apparent from the name "inner text" itself, but it also stems out of the need > to support computing bounding boxes for character ranges in inner text. > If the name of an element is derived from an attribute such as an ARIA label, that attribute won't expose any bounding box information. > If the name of an element is derived from a related element, e.g. a figcaption or an HTML label, > the bounding box of that element is unrelated to the original element's inner text. > > APIs to compute bounding boxes are exposed in IAccessibleText, ATKText and ITextRangeProvider. > > See also the definition of IAccessibleText in the IAccessible2 Specification, > the definition of ATKText in the ATK Specification, or > the definition of ITextProvider in the UIA Specification. > 1. https://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/interface_i_accessible_text.html > "The IAccessibleText interface should be implemented by all components that present textual information on the display like > buttons, text entry fields, or text portions of the document window." > 2. https://developer.gnome.org/pygtk/stable/class-atktext.html > "... if the text is editable, multi-line, typically longer than three or four words, attributed, selectable, > or if the object already uses the 'name' ATK property for other information, the atk.Text interface should be used" > 3. https://docs.microsoft.com/en-us/windows/win32/api/uiautomationcore/nn-uiautomationcore-itextprovider > "Provides access to controls that contain text." > 4. https://docs.microsoft.com/en-us/windows/win32/winauto/uiauto-implementingtextandtextrange > "If an embedded object spans a range of text, the plain text should include the inner text of the object, but not the alternative text (the name property of the embedded object) > because it might be inconsistent with the descriptive inner text." > > RELNOTES: N/A > > R=dmazzoni@chromium.org, aleventhal@chromium.org > TBR=rsesek@chromium.org > > Bug: 1049261 > Change-Id: Ic39687eb98c3ef7575214de2c659eb28d6633466 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2171436 > Commit-Queue: Nektarios Paisios <nektar@chromium.org> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#771809} TBR=dmazzoni@chromium.org, rsesek@chromium.org Bug: 1049261 Change-Id: Iebe5f00e5119ce4020dedcee176ecf9fc8a40310 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224224Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Auto-Submit: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#780246}
-
Mihai Sardarescu authored
Histogram Welcome.SignInPromptResult expired by mistake in M81. This CL resurects it as it is needed to understand how user interact with the welcome page. Bug: 814779 Change-Id: If6976a0ebdb84f979a3b6b91137a446a7310db3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252194 Auto-Submit: Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#780245}
-
Jérôme Lebel authored
-[<ApplicationCommands> showAdvancedSigninSettingsFromViewController:] is needed by WelcomeToChromeViewController. Bug: 971989 Change-Id: Ie7800f0fcc5cb26fda3bfa3b1713cc05fb9aad21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252101 Auto-Submit: Jérôme Lebel <jlebel@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#780244}
-
Mario Sanchez Prada authored
Currently, AXContentTreeData and AXContentTreeUpdate are defined in the same source files than AXContentNodeData (ax_content_node_data.h), which makes it a bit unconvenient now that we are in the process of removing all these classes, in favour of those from //ui/accessibility. While technically this is not a requirement for the process, it would be convenient to have each definition on separate places so that we can work in a more iterative way towards removing those three classes, so this CL puts AXContentTreeData in ax_content_tree_data.{h|cc} and AXContentTreeupdate in ax_content_tree_update.h, in preparation for the removal of ax_content_node_data.h, which will be the first step. Bug: 1094150 Change-Id: Ied779d527fdff7dddeac896084872f4c15b31683 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250603Reviewed-by:Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#780243}
-
Hajime Hoshi authored
Bug: 1014174 Change-Id: I27fc6bcfb0a0bfa2937f9ad26a1bdc2e984dd803 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251858 Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> Reviewed-by:
Nicolás Peña Moreno <npm@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
-
Clemens Backes authored
It was only enabled on Intel platforms so far (which meant mostly desktop), after finching we now want to also enable it on mobile systems for M-85. R=haraken@chromium.org Bug: 1040030 Change-Id: I2a2c12b977b2c519f5a7eb61f380d75d11bb943f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252100 Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Clemens Backes <clemensb@chromium.org> Reviewed-by:
-
Alex Rudenko authored
Sending CSS.styleSheetChanged allows DevTools to pick up the latest styles from the mutated stylesheet. Fixed: 1096371 Change-Id: I9acdee212309e2f6f98cdf8bdbbecf9046fd01f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253739Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Cr-Commit-Position: refs/heads/master@{#780240}
-
Yutaka Hirano authored
This is a speculative fix for a test flakiness. Bug: 1096444 Change-Id: Id9ae9124a542541c67e46bad9b891b3a3ce10ca1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253602Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#780239}
-
Yoichi Osato authored
This CL implements a part of https://fetch.spec.whatwg.org/#dom-request: " 37: If body is non-null and body’s source is null, then: 1. If r’s request’s mode is neither "same-origin" nor "cors", then throw a TypeError. 2. Set r’s request’s use-CORS-preflight flag. " Bug: 688906 Change-Id: Ie8bb1ba8ae9a3e4dca69d73b9de4078791d5f39d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235132Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#780238}
-
Christian Dullweber authored
This string is an example for a valid content settings pattern. Most translations leave it untouched but some change the url to something that is not a valid example domain or breaks the syntax. Bug: 1095878 Change-Id: I95fa441d9c356fe55e893b6a3ea4f191e03fd9de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249762 Commit-Queue: Christian Dullweber <dullweber@chromium.org> Auto-Submit: Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#780237}
-
Andy Paicu authored
TBR=mfoltz@chromium.org Bug: 1096988 Change-Id: I04e9202842d4e4e8c9929f77087e58d2b2c0684d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253760Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#780236}
-
Colin Blundell authored
This CL adds a basic test that the infobar container responds to scrolling as expected in WebLayer. To enable this test we also made the following changes: - Factored out some support for setting up scrolling in tests from BrowserControlsTest.java for reuse - Extended EventUtils.java's simulation of dragging to post the finger down/move/up events sequentially. This change is necessary to get the scroll events to be fully processed within //content and ripple out to the infobar container. Bug: 1093846 Change-Id: Ifb94f33c498a13d711336165029370e259e330c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2247894 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I0436547843d6b2b0d311ef29fb454b45524fb413 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253779Reviewed-by:
-
Dominic Battre authored
TBR=drubery@chromium.org Bug: 1068623 Change-Id: I7dafe5af78aa2d898d748df74842ede742b0e504 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253759Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#780233}
-
Oleh Lamzin authored
Expose empty Mojo probe service to Telemetry Extension. The Telemetry Extension is a prototype System Web App only installed on non-official builds and only if the chromeos::features::kTelemetryExtension feature is enabled. The exposed Mojo APIs are being used to prototype the app. In the final version, it's quite likely the APIs will be exposed a different way e.g. Extensions or Web APIs, which will go through security review. Bug: b:158658869 Test: existing browser test verifies that we don't crash when bind to service Change-Id: I4e0ebf5b74559cb2b11955dce2ba975c0fff94ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235716Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Reviewed-by:
Mahmoud Gawad <mgawad@google.com> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Oleh Lamzin <lamzin@google.com> Cr-Commit-Position: refs/heads/master@{#780232}
-
Koji Ishii authored
FragmentItem keeps all inline items in a flat list. When inline box fragments are nested, |CreateBoxFragment| handles the same item twice; once for its parent and another for its grand parent. This patch fixes this by skipping non-direct children. Bug: 1096957 Change-Id: If5acba0c5bd687d156cc4530fbe6123bca9840ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251643Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#780231}
-
Omid Tourzan authored
It clamps the banner text in case of passing the limit and adds ellipsis at the end, so the banner text doesn't overflow over/under the sibling elements. There is line-clamp property made for this purpose to do it simply by css, and it's built on -webkit-box display. As webkit-box deprecated, the css presubmit fails. https://www.chromestatus.com/feature/5680142707851264 https://gist.github.com/bfgeek/b1dc3cb741681523ae043045411eb526 So the other solution is setting the property through the js code while presubmit process updated. Comparing patchset 2 and 5 shows the difference. Tested RTL manually and it's fine. There was a change in behavior on line clamp recently supposed to be released in M85, as tested it works as expected. Bug: 1082539 Change-Id: Ie677b367eb9fa28704d89eda7ea54af9ba5a81bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251859 Commit-Queue: Omid Tourzan <oto@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#780230}
-
Mario Sanchez Prada authored
Instead of using a routingID for the |hit_frame_routing_id| field, let's use a frame token instead, which uniquely identifies a frame as well in a similar fashion to the routing ID, paving the way for future Onion Souping of content/renderer/accessibility. This also comes with a shorter term benefit, since we are in the process of removing AXContentNodeData and, along with it, the |child_routing_id| attribute that it's currently used to refer to a child frame being hit on RenderAccessibilityImpl::HitTest(). By using a frame token instead we can remove that dependency on |child_routing_id|, and therefore helpìng with the process of removing AXContentNodeData along with other AXContent* classes. Bug: 1094150 Change-Id: I2091abf6a5195ffd0128eeebc24c214eb5d5d254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251827Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#780229}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/b76d781b4f8f..0ec56611a754 2020-06-19 mathias@chromium.org Fix stylelint path resolution on Windows 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/+doc/master/autoroll/README.md Bug: chromium:1083142 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I46bbef7ff62aa9670ad8d2885d8253910643b39d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253778Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/99651228b238..545d158a2ff9 2020-06-18 stevenperron@google.com Use structured order to unroll loops. (#3443) 2020-06-18 jaebaek@google.com Debug info preservation in dead branch elimination (#3425) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,courtneygo@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64 Tbr: radial-bots+chrome-roll@google.com,courtneygo@google.com Change-Id: I6368917b890212225d048482f5fd484a6522c0f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253237Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c81f0b7b921f..e7ae237eb9e9 2020-06-19 syoussefi@chromium.org Vulkan: ANGLE_copy_texture_3d support 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 courtneygo@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/+doc/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;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: courtneygo@google.com Test: Test: CopyTexImage*Vulkan:Texture3DCopy*Vulkan:Texture2DArrayCopy*VulkanTest: Test: dEQP.KHR_GLES3/copy_tex_image_conversions_required_cubemap*cubemap* Change-Id: Id9612e2620abd4b706a8fa005ce66aac1828720b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253232Reviewed-by:
-
Andy Paicu authored
TBR=drubery@chromium.org Bug: 1096975 Change-Id: I89b93e62d1dbb3d8d84c98cc7b75e047db4c2fbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252006Reviewed-by:
-
Hans Wennborg authored
Add direct includes for things provided transitively by logging.h (or by other headers including logging.h). This is in preparation for cleaning up unnecessary includes of logging.h in header files (so if something depends on logging.h, it needs include it explicitly), and for when logging.h no longer includes check.h, check_op.h, and notreached.h. Bug: 1031540 Change-Id: Ia7798c8bba2eaf5c5bb27b27a9fd8a89ed19ff5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2248574 Auto-Submit: Hans Wennborg <hans@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#780224}
-
Rune Lillesveen authored
This is a revert of [1] which causes at least one of potentially several missing image resources updates on Chrome internal pages. I have not been able to reduce these pages and understand how MatchedPropertiesCache is involved here. I have confirmed that this fixes the issue on chrome://downloads. This flag was necessary to reproduce issue 1094185: --disable-blink-features=CSSMatchedPropertiesCacheDependencies [1] https://crrev.com/bd57436c85636c1ff62fc83f0deca55282437c0a Bug: 1094185 Change-Id: I90c4660b5cd4aa095c072033d23bdf3304e3a48d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252799Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#780223}
-
Hans Wennborg authored
Add direct includes for things provided transitively by logging.h (or by other headers including logging.h). This is in preparation for cleaning up unnecessary includes of logging.h in header files (so if something depends on logging.h, it needs include it explicitly), and for when logging.h no longer includes check.h, check_op.h, and notreached.h. TBR=sergeyu Bug: 1031540 Change-Id: Iefe53b4fbb4575b8b7bbf9d7ced13e742a4b910f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249802Reviewed-by:
Hans Wennborg <hans@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Auto-Submit: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#780222}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/581c407cd20b..693e88ae8516 2020-06-19 enga@chromium.org Vulkan: consider VK_ERROR_OUT_OF_HOST_MEMORY an OOM error 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/+doc/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: None Tbr: cwallez@google.com Change-Id: I4f47a63257028b9de431b849d6909a1f6b6f6c2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253235Reviewed-by:
-
Richard Stotz authored
Bug: 914488 Change-Id: I81a96bc4f395d82d7a0c1d804eef25a861eb1fe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2228152 Commit-Queue: Richard Stotz <rstz@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#780220}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/8ee14407329b..d257440b81e5 2020-06-19 thestig@chromium.org Rearrange CFX_CSSSelector::FromString(). 2020-06-19 thestig@chromium.org Use more WideStringViews in CFX_CSSSelector. 2020-06-18 thestig@chromium.org Remove a TODO related to C++14. 2020-06-18 thestig@chromium.org Remove CFX_CSSSelector::set_next(). 2020-06-18 thestig@chromium.org Remove CFX_CSSSelectorType. 2020-06-18 thestig@chromium.org Make CFX_CSSSelector better match Chromium style. 2020-06-18 thestig@chromium.org Clean up CFX_CSSSelector: 2020-06-18 thestig@chromium.org Reset context after running CXFA_TextLayout::LayoutInternal(). 2020-06-18 virens@microsoft.com Add function to get FPDF_ANNOTATION from FPDF_LINK 2020-06-18 thestig@chromium.org Clang format the code base. 2020-06-18 thestig@chromium.org Mark more parameters in image loading code const. 2020-06-18 thestig@chromium.org Change several enums to follow the style guide. 2020-06-18 thestig@chromium.org Check input param consistently in FPDFPageObjMark_*. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:997412 Tbr: pdfium-deps-rolls@chromium.org Change-Id: Ifb941c78e966a22f8b9f521634e135dc60c9a403 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253721Reviewed-by:
-
Andy Paicu authored
TBR=drubery@chromium.org Bug: 1096972 Change-Id: Ie7f263090e0b1810c22d3a0c4402a3edd23ca473 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253741Reviewed-by:
-
