- 08 Nov, 2019 40 commits
-
-
Nektarios Paisios authored
Every accessibility object has an ID that is used to identify the object in accessibility events, calls to methods that navigate the accessibility tree, such as IAccessible::get_accChild and get_accParent, etc. Before this patch, we were erroniously exposing an ID of -1 in the accessibility data of every View instead of its correct ID. R=aleventhal@chromium.org Change-Id: I77f31c2a3c0138ff505ff386999c60bf7465fac1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907428Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#714008}
-
Victor Vasiliev authored
quic_transport_simple_server is a simple QuicTransport server that can discard or echo back all of the traffic it receives, depending on how it's configured. Note that I've not tested the functionality of this server fully (as I don't have a corresponding client binary), but it does correctly parse ALPN and reject HTTP/3 when offered. R=rch@chromium.org Change-Id: I6396e95d180a41a9afdb185f0891c787d0c67c36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903958 Commit-Queue: Victor Vasiliev <vasilvv@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#714007}
-
Toni Barzic authored
Removes HomeScreenDelegate::UpdateAfterHomeLauncherShown, which was only updating expand arrow visibility, and move the logic to HomeScreenDelegate::OnHomeLauncherTargetPositionChanged. The method was used to update expand arrow visibility when home launcher is shown. Given that OnHomeLauncherTargetPositionChanged is expected to get called during the same sequence, expand arrow visilibity can be moved there without losing much, and reduces the number of methods that need to be called while using gestures to show/hide home launcher. Also, updates how app list progress is calculated when app list is scaled in tablet mode to ignore app list translation that was added during scaling (without this, if arrow is painted while app list view is scaled down, it might be slightly bent). BUG=1022530 Change-Id: Ie284b413bdc576121757c1c4bb1b4280c97e06b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1904235Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Manu Cornet <manucornet@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#714006}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e9709db85ca9..c1e84c789f8d git log e9709db85ca9..c1e84c789f8d --date=short --no-merges --format='%ad %ae %s' 2019-11-08 oysteine@google.com Merge "Re-land "Stack profiles: Reuse existing frame/module rows rather than adding one per sequence"" Created with: gclient setdep -r src/third_party/perfetto@c1e84c789f8d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=perfetto-bugs@google.com Bug: None Change-Id: I3cc3f4de7db752e95d241ba91ac7fa25ede12bc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907277Reviewed-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@{#714005}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-compile-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-compile-chrome BUG=762641 TBR=chrome-os-gardeners@google.com Change-Id: Ic8d59cb796fe30a71d4ed21abe9eda9202411ec3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906526Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#714004}
-
Wei-Yin Chen (陳威尹) authored
Bug: None Change-Id: I394f1a6db39649ceab7eda3f0950425c5b0c0d44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906122Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#714003}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/50919254cbc7..c2f1f6188127 git log 50919254cbc7..c2f1f6188127 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 lehoangq@gmail.com Always use MTLPixelFormatBGRA8Unorm for SurfaceMtl. 2019-11-08 jonahr@google.com Reset texture swizzle state to default after LUMA workaround Created with: gclient setdep -r src/third_party/angle@c2f1f6188127 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 jonahr@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=jonahr@google.com Bug: chromium:1022080 Change-Id: I8e90d828cd012b89d9946f042bf4d838952c7f0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907276Reviewed-by:
-
Etienne Bergeron authored
This test is broken due to the way the metrics are computed in RenderText Harfbuzz. Assume we have a text with 1) SUPERSCRIPT 2) NORMAL 3) SUBSCRIPT The NORMAL text is using a font 12px, and the SUBSCRIPT and SUPERSCRIPT are using a font 7 px. The metrics of both font will differs (not the same Ascent and Descent) and not same font-height. The baseline offset of 1) will be negative (e.g. -3) and the baseline offset of 2) will be positive (e.g. 3). The test is checking that the size of the text is within a bounding box. But the computation of that box is wrong. The TOP is the SUPERSCRIPT baseline + superscript_font.ascent. The BOTTOM is the SUBSCRIPT baseline - subscript_font.descent. The current computation is trying to find the max_ascent and max_descent and offset them on baseline. This computation is not giving the right bounding box. Bug: 459812 Change-Id: Id72f37888dfd2de4db2dc3b8704f06da01797cda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906631 Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#714001}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/a53e47fe9483..4135cf0b57c2 git log a53e47fe9483..4135cf0b57c2 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 mtklein@google.com use round() instead of trunc() to f32->unorm 2019-11-08 jlavrova@google.com Yet another build fix 2019-11-08 mtklein@google.com rename to_i32 -> trunc, and add round 2019-11-08 mtklein@google.com avoid redundant clamps 2019-11-08 mtklein@google.com don't clamp alpha, it's already [0,1] Created with: gclient setdep -r src/third_party/skia@4135cf0b57c2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC ethannicholas@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-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 TBR=ethannicholas@google.com Bug: None Change-Id: I8cd2dcd82d71352dc997d353334512e79c3a677c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906297Reviewed-by:
-
evliu authored
Bug: 997813 Change-Id: I08cab88280f727a67cd22ddc06b109e8663430c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1904613 Commit-Queue: Evan Liu <evliu@google.com> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#713999}
-
Min Qin authored
If a download is interrupted in a terminal state, the information will be written to both history DB and in-progress DB. And the in-progress DB info will later be erased when download history is loaded. However, if Chrome crashes during the write, history DB could contain more recent information. If the same download is resumed in reduced mode later, loading the history DB could delete that download, causing Chrome to delete the DownloadFile object on UI thread while it is reading data on download task runner. This CL fixes the issue by: 1. Force in-progress DB to write download information immediately if a download is in a terminal state. 2. If a download is in terminal state in history DB and an in-progress DB version is already in-progress, ignore the history DB version and request it to be deleted. This matches the existing behavior if only history DB is used. (If only history DB is used, a crash before download terminal state is written to disk will make the download to be able to resume, even if a failed notification is already shown). BUG=1009839 Change-Id: Ic8621754e4961f665f3d42452a4e3794cbbc82bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898647 Commit-Queue: Min Qin <qinmin@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#713998}
-
Manu Cornet authored
Bug: 1021691, 1017435, 1019531 Change-Id: I62368e4167a747227007543118d1a0ed2bf9ffbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1905746Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0db29887459d..f0ec2f973421 Created with: gclient setdep -r src-internal@f0ec2f973421 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: If7824298c5ed4c5d7b44272a3bdea6c97a2f69a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906720Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#713996}
-
Xiaohan Wang authored
- Move ExpectRendererInitialization() into StartPipeline* to avoid having to call this in most tests. - Simplify audio/video DemuxerStream creation. Bug: 1018372 Test: Add new tests Change-Id: I834b40fe8b475ce94661162edec9ed576d161d25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906256 Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#713995}
-
Philip Rogers authored
LayoutObject::HasDistortingVisualEffects will crash if there are no local border box properties. This patch updates HasDistortingVisualEffects to mirror HasNonZeroEffectiveOpacity which has a check for no local border box properties. Bug: 1012596 Change-Id: Ib1c5260c3335c70098d9462c9c626774e3ed0f63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906709Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#713994}
-
Yutaka Hirano authored
This is needed to start the experiment on beta. Bug: 1018081 Change-Id: I753809054a6f4d5119401ddc79439dcd3ca60713 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902173 Auto-Submit: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#713993}
-
Klaus Weidner authored
Copying a node's children happened asynchronously, resulting in them getting inconsistent worldMatrixDirty values and objects being rendered at the wrong place. Change-Id: If5bd6f166f24eabbcb628f70fba8f01b5a810490 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907274 Auto-Submit: Klaus Weidner <klausw@chromium.org> Reviewed-by:
Piotr Bialecki <bialpio@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#713992}
-
Fan Yang authored
Roll src/net/third_party/quiche/src/ 7a4d20901..ac35d459a91137d44e9418cc41e808a6d9bb466d (14 commits) https://quiche.googlesource.com/quiche.git/+log/7a4d20901fbb..ac35d459a91137d44e9418cc41e808a6d9bb466d $ git log 7a4d20901..ac35d459a91137d44e9418cc41e808a6d9bb466d --date=short --no-merges --format='%ad %ae %s' 2019-11-08 fayang Remove unused this from lamda function in QuicSentPacketManagerTest.RtoNotInFlightPacket 2019-11-08 fayang Loose the expectation of EndToEndTestWithTls.SendAndReceiveCoalescedPackets 2019-11-08 fkastenholz Handle case where crypto stream is not immediately available. 2019-11-07 nharper Add IsResumption method to QUIC client handshakers 2019-11-07 wub gfe-relnote: (n/a) Add pop_front_n and pop_back_n methods to QuicCircularDeque. Code not used yet. 2019-11-07 fayang gfe-relnote: In QUIC, do not inject bandwidth in BbrSender::AdjustNetworkParameters. Also use min rtt instead of srtt when calculating new cwnd. Protected by gfe2_reloadable_flag_quic_bbr_donot_inject_bandwidth. 2019-11-07 fayang gfe-relnote: In QUIC, call NeuterHandshakePackets() at most once per connection. Protected by gfe2_reloadable_flag_quic_neuter_handshake_packets_once2 which replaces gfe2_reloadable_flag_quic_neuter_handshake_packets_once. 2019-11-07 renjietang Remove QuicStream::read_side_closed(). 2019-11-07 renjietang Cleanup unused code in QuicStream. 2019-11-07 quiche-dev Fix invalid iterator bump in ValueSplittingHeaderListTest 2019-11-06 renjietang Remove member "perspective_" in QuicStream. 2019-11-06 dschinazi Add pretty-print logging for MessageResult 2019-11-06 renjietang Remove QuicStream::WritevData(). 2019-11-06 dschinazi Remove unimplemented method 2019-11-06 quiche-dev Internal QUICHE change Created with: roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src Change-Id: I233f0866873ce9f8e949a8de5fa768297b665427 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906634Reviewed-by:
-
Kenneth Russell authored
The following tests are enabled: ContextLost_MacWebGLMultisamplingHighPowerSwitchLosesContext ContextLost_MacWebGLPreserveDBHighPowerSwitchLosesContext GpuProcess_mac_webgl_backgrounded_high_performance GpuProcess_mac_webgl_high_performance GpuProcess_mac_webgl_low_power GpuProcess_mac_webgl_terminated_high_performance Pixel_WebGLHighToLowPower Pixel_WebGLLowToHighPower Bug: 681341 No-Try: True Tbr: ccameron@chromium.org Tbr: jdarpinian@chromium.org Change-Id: I996cc9e195eb4d398691ee816cbf6c404be3f4c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906881 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
James Darpinian <jdarpinian@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#713990}
-
Anastasia Helfinstein authored
In preparation for future changes, change the behavior of how Switch Access checks if a child node is a group from initializing a field on construction to implementing an abstract function. Bug: None Change-Id: I9a0657c19fcd7b3428ddfecb108d52a9cd0b2250 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907192Reviewed-by:
Aran Gilman <gilmanmh@google.com> Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Cr-Commit-Position: refs/heads/master@{#713989}
-
evliu authored
Bug: 997813 Change-Id: I1cc6104341d131e3688c6167c430a14cb57f3337 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903761 Commit-Queue: Evan Liu <evliu@google.com> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#713988}
-
Dirk Pranke authored
This reverts commit 3b26aa05. Reason for revert: Reverting due to failures on Mac as per the comment. Original change's description: > Attempt to fix the parser caching in the IDL compiler. > > PLY has a feature where it'll load a generated lexer > table by importing it as a python module. It turns out > that we were being inconsistent in how we were generating > these modules and that could lead to incomplete builds depending > on when the various IDL compilation targets ran. > > This CL attempts to be more consistent about the generation > of the cached files to eliminate that problem, by requiring > the scripts to consistently pass in the location of the cached > files. We can't really fix this without doing more serious > surgery on PLY (or working around it) to be more deterministic > in how the cached file is imported. > > R=dcheng@chromium.org, haraken@chromium.org > BUG=1022647 > > Change-Id: I141059341634633f0df33848638eecc432aa764c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903938 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Commit-Queue: Dirk Pranke <dpranke@chromium.org> > Cr-Commit-Position: refs/heads/master@{#713872} TBR=dcheng@chromium.org,dpranke@chromium.org,haraken@chromium.org Change-Id: Ia84a8baa53bef4556f2239e564ac19a92fffda9a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1022647 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906117Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#713987}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/039522eb577e..0e9afd2a56f2 git log 039522eb577e..0e9afd2a56f2 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 brucedawson@chromium.org Change "CPU time" to "elapsed time" Created with: gclient setdep -r src/third_party/depot_tools@0e9afd2a56f2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@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/+/master/autoroll/README.md TBR=agable@chromium.org Bug: None Change-Id: I62e53a374ea5c34d719bc578b85b9ad7a55e7372 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906721Reviewed-by:
-
David Schinazi authored
Fix issue where receiving HTTP response status 408 on an HTTP/2 connection would cause us to retry infinitely. We now only retry for HTTP/1.1 (and 0.9 and 1.0) but not HTTP/2 and later. Bug: 695225 Change-Id: I6a3c2c9447e4dde536fa7925306b41de9d4afb28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907188 Commit-Queue: David Schinazi <dschinazi@chromium.org> Reviewed-by:
-
Aran Gilman authored
Bug: 1016614 Change-Id: I9c16e9d8a31c1decb9269e6d5daf064132575d18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906633Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Aran Gilman <gilmanmh@google.com> Cr-Commit-Position: refs/heads/master@{#713984}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/636832d9a666..814821a14375 git log 636832d9a666..814821a14375 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 tsepez@chromium.org Remove unused CBC_QRCoder::GetNumECBytes(). 2019-11-08 tsepez@chromium.org Remove CBC_Writer::Set{Background,Barcode}Color(). 2019-11-08 tsepez@chromium.org Cover more branches in fx_crypt_sha.cpp. 2019-11-08 tsepez@chromium.org Simplify control flow in FPDF_RenderPage(). 2019-11-08 tsepez@chromium.org Remove duplicate FPDF_OBJECT_ definitions from fpdf_annot.h 2019-11-07 tsepez@chromium.org No need to check for null pages in RenderPageWithContext() Created with: gclient setdep -r src/third_party/pdfium@814821a14375 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/+/master/autoroll/README.md TBR=pdfium-deps-rolls@chromium.org Bug: None Change-Id: Ic3a103b1f3483effe684a5eaaf730fdc4d69f372 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907196Reviewed-by:
-
John Lee authored
Pressing a shortcut (ctrl+f1 on ChromeOS) will now allow the user to focus into an opened tab strip. Once the tab strip becomes focused, it will focus the first tab within it. If the tab strip is not opened, pressing the toggle to open it will automatically move the focus into the tab strip, but only if the user is already focusing the button, suggesting they were able to arrive at the button using other keyboard shortcuts. This CL also adds a title to the HTML doc to announce it when the user focuses into the tab strip, and adds the tab's title as context to the close button. The CL does not update focused styles. Demo screencast in bug. Bug: 1017472 Change-Id: I6af0114b24f1136c8a77faacadc89f4d3a6309b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1896045 Commit-Queue: John Lee <johntlee@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#713982}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/f7e05c734266..f0bfbce62d42 git log f7e05c734266..f0bfbce62d42 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 rharrison@google.com Another major API rework (#871) Created with: gclient setdep -r src/third_party/shaderc/src@f0bfbce62d42 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=radial-bots+chrome-roll@google.com Bug: None Change-Id: I800c7b7729f175550466898fec078543767a638d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906712Reviewed-by:
-
Robert Sesek authored
Bug: 1017830 Change-Id: I1c0c69b130bc048ec75a70a65e22e7d73fad0158 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906632 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#713980}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/2a7f3180..fdd7f421 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,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I41dc224608e14b61ed087198c6ce53e0c4de6d12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906510Reviewed-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@{#713979}
-
Ce Chen authored
The creation will happen on |task_runner_| when |model_update_listener| fires the new model available notification, instead of synchronously on receiving the user autocomplete input. This is to fix the omnibox.QueryTime2.1 regression (other QueryTime2.x is not affected by the existing design), e.g. http://screenshot/1U2Oq5vfnRm Tested on Pixel 2 XL for pre-existing model loading and new model download. Bug: 925072 Change-Id: Ieb26aa78c8bbd848ed1f0c9b722bab266b21aa59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902513 Commit-Queue: Ce Chen <cch@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#713978}
-
Quinten Yearsley authored
This would also rename BuildBot class to TestResultsFetcher, and rename the attribute buildbot to results_fetcher. These classes have nothing to do with Buildbot, which is no longer used. They do seem to be basically about fetching results of tests that were run on bots. Bug: 1002702 Change-Id: Ie877f4c16e8edde5023366a299dabb657a0ecd52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1894618Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Cr-Commit-Position: refs/heads/master@{#713977}
-
Nick Diego Yamane authored
As of crrev.com/c/1789603, GdkEventKey::state is not being set correctly when translating ui::KeyEvent into GdkEvents. Such field should be equivalent to XKeyEvent::state, which contains, besides modifiers state bits, keyboard group information. This causes regressions such as crbug.com/1021732, oddly specifically when GTK_IM_MODULE env variable is set to 'xim'. This CL fixes it by including 'group' value into GdkEventKey::state composed value, as was already done in GtkEventLoopX11. Bug: 1021732 Change-Id: I2d166ab9f88fc46fd5150f0f2d224aa85a22f9a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902438Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Nick Yamane <nickdiego@igalia.com> Cr-Commit-Position: refs/heads/master@{#713976}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/60c88fd3ec68..e9709db85ca9 git log 60c88fd3ec68..e9709db85ca9 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 eseckler@google.com processor: Build all of TP on chrome desktop platforms 2019-11-08 fmayer@google.com Merge "Do not block on control socket." 2019-11-08 treehugger-gerrit@google.com Merge "compact sched_waking: cfg/trace protos" Created with: gclient setdep -r src/third_party/perfetto@e9709db85ca9 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=perfetto-bugs@google.com Bug: chromium:1022386 Change-Id: Ibaa5a79c764fbdeb5474dc741a72c1509a135752 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906943Reviewed-by:
-
Doug Arnett authored
Bug: 1022820 Change-Id: Icada0c443861e2c5a9b66a879abb3c976db2c2e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906311Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Doug Arnett <dougarnett@chromium.org> Cr-Commit-Position: refs/heads/master@{#713974}
-
Reilly Grant authored
These metrics for usage of the device motion and orientation sensor APIs are unused because these features are no longer available in insecure contexts. Bug: 1016906 Change-Id: I86f4d7f5979b307753b0ee6c5a96fb4b1d1af6cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1904749 Commit-Queue: Reilly Grant <reillyg@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#713973}
-
Xiaohan Wang authored
Currently if there are encrypted streams in the demuxer and there's no CDM set, Renderer::Initialize() will wait for the CDM to be set to finish initialization. This logic has been implemented in RendererImpl and DecryptingRenderer. This CL moves this logic to PipelineImpl for two purposes: 1. We can create different Renderers based on the CDM type. 2. We can remove the waiting-for-CDM from Renderer implementations. Bug: 1018372 Test: Change-Id: I4d1b22bd0a3661a96934de1c78ccd5d9e179e2fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902647Reviewed-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/+/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: I4c0a72b515a8ea51b7312347783b40cee2b9f529 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907186Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f0ade8a687ee..a53e47fe9483 git log f0ade8a687ee..a53e47fe9483 --date=short --no-merges --format='%ad %ae %s' 2019-11-08 mtklein@google.com native f32 min/max 2019-11-08 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-11-08 mtklein@google.com convert SkVMBlitter over to floats 2019-11-08 csmartdalton@google.com Always attach stencil buffers with exact sample count matches 2019-11-08 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@a53e47fe9483 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC ethannicholas@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-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 TBR=ethannicholas@google.com Bug: None Change-Id: I6765528c0a685b89721ffc14aa4ae41abe754bcd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907187Reviewed-by:
-
Victor Vasiliev authored
This way, we can reuse the logic in non-HTTP QUIC servers. Change-Id: I9651e80c965ea0ea3890f776f380d402a563f8a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1904690 Commit-Queue: Victor Vasiliev <vasilvv@chromium.org> Reviewed-by:
-
