- 18 Oct, 2017 5 commits
-
-
Eugene But authored
Before this CL RecordPageLoadStart was called from deprecated CRWWebDelegate callbacks: - webWillAddPendingURL:transition: - webDidUpdateSessionForLoadWithURL: RecordPageLoadStart is called for the following navigations: - typed navigation - link clicks - bookmark - form submission - switching user agent type RecordPageLoadStart is NOT called for the following navigations: - back forward navigation - client redirect - reload - opening NTP - opening a child window and loading URL there - preload tabs Bug: 674991 Change-Id: I70d53f7e18faf8da151ae1dde35037bad124eb09 Reviewed-on: https://chromium-review.googlesource.com/707659 Commit-Queue: Eugene But <eugenebut@chromium.org> Reviewed-by:
Gregory Chatzinoff <gchatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#509614}
-
Vlad Tsyrklevich authored
Group failing casts and vcalls separately. This ensures the release build disables CFI checking as narrowly as possible--currently only CFI-vcall is enabled for release but checking is also disabled for bad- cast blacklist entries as well. Bug: 772906 Change-Id: Id8a91d1b01cbf858cf6be4f2b91fe548a521ef83 Reviewed-on: https://chromium-review.googlesource.com/706145Reviewed-by:
Peter Collingbourne <pcc@chromium.org> Commit-Queue: Peter Collingbourne <pcc@chromium.org> Cr-Commit-Position: refs/heads/master@{#509613}
-
Matt Reynolds authored
Chrome for Mac recognizes "Made for iOS" (MFi) gamepads enumerated by the GameController framework. When multiple such devices are connected at once, Chrome fails to properly distinguish them. GCController exposes a playerIndex field that defaults to the value GCControllerPlayerIndexUnset (-1). The application may set this field to a value between 0 and 3 to signal which LEDs should be lit on the gamepad. Chrome also uses this field to distinguish gamepads, but does not set the index to a unique value. This causes the first-connected gamepad to shadow any other connected gamepads. This CL ensures each connected MFi gamepad is assigned a unique player index up to the OS-defined limit of four. BUG=775270 Change-Id: Iaf038a910df8dc7eb2cee99d4d671a6c9ff6dba0 Reviewed-on: https://chromium-review.googlesource.com/724233 Commit-Queue: Matt Reynolds <mattreynolds@chromium.org> Reviewed-by:
Brandon Jones <bajones@chromium.org> Cr-Commit-Position: refs/heads/master@{#509612}
-
James Cook authored
crrev.com/c/723604 eliminated the only caller of this code from chrome. The remaining calls are from tests in ash_unittests. AshTestBase already installs a ui::ScopedAnimationDurationScaleMode::ZERO_DURATION so the animations were already being skipped in these tests. Bug: none Test: ash_unittests Change-Id: Ie95041cf03bee51b5d2786f03d3799241c75e513 Reviewed-on: https://chromium-review.googlesource.com/724221 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#509611}
-
Zhongyi Shi authored
to QuicChromiumClientSession::Migrate so that we can clean up further to move all migration logic to session. Bug: 775593 Change-Id: Id70c45fe7d0c05ce3fb34084c336e89d48c50500 Reviewed-on: https://chromium-review.googlesource.com/723782 Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#509610}
-
- 17 Oct, 2017 35 commits
-
-
Fady Samuel authored
Now that OOPIFs work in Mus+Ash, we can re-enable a surface synchronization DCHECK in RenderWidget. Bug: 672962 Change-Id: Ie9918085a103bf31c98f292667e312b78feedf96 Reviewed-on: https://chromium-review.googlesource.com/721631 Commit-Queue: Fady Samuel <fsamuel@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#509609}
-
Steven Holte authored
Splits decoder logic into a seperate generated file, and breaks logic into several templates with the same parameters. Bug: Change-Id: I8d6bf188ec73a475428cc49991bdace36458a468 Reviewed-on: https://chromium-review.googlesource.com/721849Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#509608}
-
Jon Napper authored
The option to "Never translate this site" is always shown on the translate dialog, even when the site cannot be blacklisted (for example a file:/// URL). This patch changes the translate options combon so "Never translate..." is only shown if it will have some effect. Note that the 2016Q2 experimental UI has not been patched as the currently plan is to not launch this UI. Bug: 663934 Change-Id: I64b80d830e124e9372906bd0c4711568c46ff636 Reviewed-on: https://chromium-review.googlesource.com/572475Reviewed-by:
Jia Meng <jiameng@chromium.org> Commit-Queue: Jon Napper <napper@chromium.org> Cr-Commit-Position: refs/heads/master@{#509607}
-
Michael Thiessen authored
This CL is kept intentionally as simple as possible for merging back to M-63. Tests to prevent this regression in the future will be added in a followup CL. Bug: 775571 Change-Id: I78ea1e46efdb2b48bc61e1ab704b6b1526d2c171 Reviewed-on: https://chromium-review.googlesource.com/723770Reviewed-by:
Brandon Jones <bajones@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#509606}
-
Kyle Horimoto authored
This will be used to aid testing in a follow-up CL. Bug: 761532, 672263 Change-Id: Ifb7b81ab745126aed13abe92e46fe2c77c0bada0 Reviewed-on: https://chromium-review.googlesource.com/724228Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#509605}
-
Nate Chapin authored
delegate_->GetExecutionContext() can get confused for Element-root IntersectionObservers if the Element moves between Documents. If the original Document was detached, attempting to schedule a task for that context will crash. Bug: 763040 Test: intersection-observer/observer-shared-from-iframe.html Change-Id: I6315791b71bf1e3d02e0e6f7369992f2c6fe2a6c Reviewed-on: https://chromium-review.googlesource.com/716671Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#509604}
-
Xi Han authored
In M57, we adopted the same signature to sign WebAPKs generated by all of the Chrome channels, as well as checked in a fix to open WebAPKs in a tab if it doesn't pass the signature check. These fix weren't available on pre-M57. As a result, a latest WebAPK can't pass the signature check and fails to be launched on pre-M57. In this CL, we add a check for Chrome's version in WebAPKs itself, and launch the WebAPK in tab mode if the Chrome's version is old. Bug: 772398 Change-Id: I3cd71d5b72512623795796c827aa6881ed08d4b7 Reviewed-on: https://chromium-review.googlesource.com/706056 Commit-Queue: Xi Han <hanxi@chromium.org> Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Cr-Commit-Position: refs/heads/master@{#509603}
-
webrtc-autoroll@chromium.org authored
https://webrtc.googlesource.com/src.git/+log/1b4059e84f5f..6bf70d20daa9 $ git log 1b4059e84..6bf70d20d --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I432dcae24606641f6d91f9287575673909b25027 Reviewed-on: https://chromium-review.googlesource.com/724170Reviewed-by:
WebRTC Roll Bot <webrtc-autoroll@chromium.org> Commit-Queue: WebRTC Roll Bot <webrtc-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#509602}
-
Dale Curtis authored
Should help with fuzzing timeouts and seem like they should be invalid... We definitely have files that have a zero sized sample as the last sample, but none that I can find with contiguous zero sized samples. BUG=770577 TEST=fuzzer fails before allocated massive amounts of memory. Change-Id: Ie137d6f9ec69a1afd5c496c9f6f93706d670c5d9 Reviewed-on: https://chromium-review.googlesource.com/720206Reviewed-by:
Dan Sanders <sandersd@chromium.org> Reviewed-by:
Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#509601}
-
Ken Rockot authored
For the sake of efficiency, we don't fully serialize handles in a message until we're ready to freeze the message contents for transmission. Unfortunately we were not properly closing these partially serialized handles in the event that the message was never fully serialized before destruction. This fixes that. R=jcivelli@chromium.org Bug: 775592 Change-Id: Idac3b11359dc2fcec0699cef779de809575ea163 Reviewed-on: https://chromium-review.googlesource.com/723771Reviewed-by:
Jay Civelli <jcivelli@chromium.org> Commit-Queue: Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#509600}
-
skia-deps-roller@chromium.org authored
https://skia.googlesource.com/skia.git/+log/a0020f987e73..e148bf714e39 $ git log a0020f987..e148bf714 --date=short --no-merges --format='%ad %ae %s' 2017-10-06 ethannicholas fix for SkSL lexer crash on non-ASCII input 2017-10-17 liyuqian Add concise option to Calmbench bot Created with: roll-dep src/third_party/skia Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=benjaminwagner@chromium.org Change-Id: I64882bc35167c1e38baf1c5088559c3e630e6c75 Reviewed-on: https://chromium-review.googlesource.com/724079Reviewed-by:
Skia Deps Roller <skia-deps-roller@chromium.org> Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#509599}
-
Rohit Rao authored
The _isActive flag and |clearInternalState| are called indirectly when the stack view is closed through viewDidDisappear, but it is better to reset state explicitly when the animations are complete. This matches the workflow that is used when an existing Tab is opened from the stack view. A future CL will switch to VC presentation instead of containment, and that will result in viewDidDisappear no longer being called in the same way. BUG=768563 Change-Id: I0c0dd453ca4c49a7f34ff072dc9e52e9fc551c2a Reviewed-on: https://chromium-review.googlesource.com/723166Reviewed-by:
Kurt Horimoto <kkhorimoto@chromium.org> Commit-Queue: Rohit Rao (ping after 24h) <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#509598}
-
Aaron Leventhal authored
Standalone executable tool that helps developers view IAccessible2 object trees from any application. This tool is an alternative to AccProbe, which is buggy, and AViewer, which is not feature rich. The first version of ax_dump_tree is barebones and simply displays events on console, but has a lot of room for future expansion (e.g., serve info to a GUI, dump the tree structure etc.). The tool is similar is use to ax_dump_events. As an example of how this makes easier, when there is a bug with NVDA/JAWS in Chrome that doesn't occur with Firefox, we can look at the object tree emitted by Firefox for the same content. The ax_dump_tree tool shares code and formatting with the DumpAccessibilityTree browsertests. Use as follows: ax_dump_tree --pid=[processid] ax_dump_tree --window=[hwnd] (start with 0x to use hex value) TBR=nektar,dpranke Bug: 771747 Change-Id: Idfc17ca1a1d44006ad32dcca07303ce1d93f7669 Reviewed-on: https://chromium-review.googlesource.com/724239Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#509597}
-
James Cook authored
The eliminates non-public ash dependencies from the tests. * Convert the tests to use the mojo system tray test API * Clean up the test api, always use the same SystemTray*, remove some unnecessary RunLoop spins * Put the tests on the mojo FYI bot. I'll move them to the main waterfall when I'm confident they are stable. Bug: 775121 Test: browser_tests --mash --gtest_filter="SystemTrayClient*" Change-Id: Id790ca77aa179db499c45825a1466e18cc9f78d7 Reviewed-on: https://chromium-review.googlesource.com/723604Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#509596}
-
ccameron chromium authored
This reverts commit fd493b4b. Reason for revert: Causing compile failures, unresolved externals SkCodec::getPixels SkCodec::startIncrementalDecode SkCodec::startScanlineDecode Original change's description: > Stop building SkCodec > > Bug: 768878 > > Building SkCodec seems to have caused a paint regression on a webpage > without any images. This leads us to suspect "some minor compiler > optimization tickling". Stop building it to confirm. Two CLs rely on > SkCodec: > > "Use SkCodec internally in GIFImageDecoder" > 4fed3346. This introduced building > SkCodec. > > "Enable Skia's SkImageGenerator implementation" > f5eb27c2. This used SkCodec to fix > crbug.com/758459, but that seems to have been fixed in another way. > > In addition, this corrects some formatting in the old code (as > commanded by presubmit), and makes some other minor changes (no more > PassRefPtr, FrameDurationAtIndex now returns a TimeDelta). > > Change-Id: Ic2bdd87740da0232c9c07e27eed6049efc26d76c > Reviewed-on: https://chromium-review.googlesource.com/718918 > Commit-Queue: Leon Scroggins <scroggo@chromium.org> > Reviewed-by: Chris Blume <cblume@chromium.org> > Reviewed-by: Fredrik Söderquist <fs@opera.com> > Reviewed-by: Leon Scroggins <scroggo@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#509570} TBR=scroggo@chromium.org,pdr@chromium.org,fs@opera.com,cblume@chromium.org Change-Id: I7871671628746680fd727708aed8736402d75ada No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 768878 Reviewed-on: https://chromium-review.googlesource.com/724381Reviewed-by:
ccameron chromium <ccameron@chromium.org> Commit-Queue: ccameron chromium <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#509595}
-
Ryan Sturm authored
There was a missing break statement in a switch statements, so this code was refactored to have a return in each case statment. Bug: 775595 Change-Id: Iec1671d5946804190d7d747bec9f17183586eff5 Reviewed-on: https://chromium-review.googlesource.com/723729 Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#509594}
-
Jérôme Lebel authored
Removing switch user mode ProfileChooserController, with all strings and resources related. Linux/Windows cleanup done previously in: crrev.com/c/704937 User switch feature was added: crrev.com/435423005 Bug: 775110 Change-Id: I6de5e8d8875402d4aaa347f32213440c35f779c5 Reviewed-on: https://chromium-review.googlesource.com/706776Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#509593}
-
Lei Tian authored
Move the Browser Actions tab merging function from ChromeTabbedActivity to the BrowserActionsTabModelSelector. And since the tab mergine removes tabs Synchronously, so there is no need to update TabPersistentStore for tabRemoved callback. Call saveState() after all tabs removed is enough. Bug: None Change-Id: I5b6dc8b9ed385212ae3f7bdc3fa33b9d030ff4aa Reviewed-on: https://chromium-review.googlesource.com/722175Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Lei Tian <ltian@google.com> Cr-Commit-Position: refs/heads/master@{#509592}
-
Robert Liao authored
This is a mostly automated refactor. BUG=638327 TBR=sky@chromium.org Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I9da8b34dc748d427bcdbe446878461b00bdbda93 Reviewed-on: https://chromium-review.googlesource.com/723867 Commit-Queue: Robert Liao <robliao@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Cr-Commit-Position: refs/heads/master@{#509591}
-
Sergey Ulanov authored
GetNativeGpuMemoryBufferType() returns EMPTY_BUFFER on all platforms other than MacOS and Linux, so when running cast_shell on Fuchsia a DCHECK in IsNativeGpuMemoryBufferConfigurationSupported() was failing. Replaced that DCHECK with an if statement that returns false in that case. Bug: 772488 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Icaeba966b46f1846540c3137e675ae223593fa7e Reviewed-on: https://chromium-review.googlesource.com/723592 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#509590}
-
Elliot Glaysher authored
Bug: 766759 Change-Id: Idbe2e37cdef51476c6af9b56952daa2851d4d2b2 Reviewed-on: https://chromium-review.googlesource.com/723200Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Elliot Glaysher <erg@chromium.org> Cr-Commit-Position: refs/heads/master@{#509589}
-
Rob Buis authored
Thead setter should throw if not handed a thead parameter [1]: "If the new value is neither null nor a thead element, then a "HierarchyRequestError" DOMException must be thrown instead." [1] https://html.spec.whatwg.org/#dom-table-thead Bug: 651572 Change-Id: Ia65a259b7bc6e9cca50d5491c497012149d1fa8e Reviewed-on: https://chromium-review.googlesource.com/721860Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#509588}
-
Dominick Ng authored
This CL introduces a feature flag which, when enabled, sources URLs for the NTP TopSites tiles from the site engagement service instead of using the history-based "frecency" approach. Using engagement allows sites that are infrequently navigated to but heavily used to be prioritised in TopSites. Currently, engagement sorting of TopSites is limited to sourcing origins only, as the site engagement service only records engagement per origin. Future work will overcome this limitation by integrating engagement as a component in the frecency scoring in VisitSegmentDatabase, rather than as a completely separate component. BUG=764218 Change-Id: I13d2072e3d1dd94684fafcbd5e5e991af9e43d00 Reviewed-on: https://chromium-review.googlesource.com/691497Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#509587}
-
Reilly Grant authored
These tests were blanket disabled when the number of failing LayoutTests with the Network Service enabled was very high. Now that the number of failures is more under control we should enable them. The mojo-loading virtual tests are explicitly skipped since enabling the Network Service also enables Mojo Loading and so the test coverage is redundant. TBR=jam@chromium.org NOTRY=true Bug: 729849 Change-Id: I33abad9d8a7cfe6cf498985d786dcc4294ae5229 Reviewed-on: https://chromium-review.googlesource.com/724081Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#509586}
-
Alex Moshchuk authored
This adds some more information for CHECKs that fire in origin lock mismatches, which we're seeing in the --site-per-process trial. It also adds a crash key for the origin lock in CanAccessDataForOrigin, since the existing crash key was not picked up for either GetCookies kills or local storage kills. Bug: 773809 Change-Id: I81e9a06e7c001d2520e3a49b18b6cbd63be32931 Reviewed-on: https://chromium-review.googlesource.com/723851Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#509585}
-
pdfium-deps-roller@chromium.org authored
https://pdfium.googlesource.com/pdfium.git/+log/6dc4fb899acf..7c2daec0a5f5 $ git log 6dc4fb899..7c2daec0a --date=short --no-merges --format='%ad %ae %s' 2017-10-17 hnakashima Fix loading mutually referencing colorspaces. Created with: roll-dep src/third_party/pdfium Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls TBR=dsinclair@chromium.org Change-Id: I38df7c4b75537760a5ca874fd13dad354328e964 Reviewed-on: https://chromium-review.googlesource.com/723611 Reviewed-by: <pdfium-deps-roller@chromium.org> Commit-Queue: <pdfium-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#509584}
-
Dirk Pranke authored
You can't run the browser on a ChromeOS device without the chrome_sandbox binary, so it makes sense for it to be a data_dep. This is unnecessary for the "desktop ChromeOS" build, but the binary isn't big so it's not much of an additional dependency. R=rsesek@chromium.org Change-Id: Ifd74b8ba2cc094d11686479d147d722661c21d10 Reviewed-on: https://chromium-review.googlesource.com/722239Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#509583}
-
Max Moroz authored
R=metzman@chromium.org, ochang@chromium.org Bug: 759794 Change-Id: I5dff2a11d985a6fb1bf9a9b821edd000b6227fe4 Reviewed-on: https://chromium-review.googlesource.com/721634 Commit-Queue: Max Moroz <mmoroz@chromium.org> Reviewed-by:
Jonathan Metzman <metzman@chromium.org> Reviewed-by:
Oliver Chang <ochang@chromium.org> Cr-Commit-Position: refs/heads/master@{#509582}
-
Jayson Adams authored
When you use Chrome's infobar or Settings page to make Chrome your default browser, macOS presents a confirmation dialog. Sometimes macOS orders the dialog onscreen but behind the browser window, where it is effectively invisible. Without confirmation via this dialog, macOS will not change your default browser. This cl forces the UI element responsible for the dialog to become active after setting the default browser, bringing the confirmation dialog to the foreground, in front of all windows. Bug: 775281 Change-Id: I5376d57c088ea6b564d84cb3d35442a4330f954b Reviewed-on: https://chromium-review.googlesource.com/722221Reviewed-by:
Mark Mentovai <mark@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Jayson Adams <shrike@chromium.org> Cr-Commit-Position: refs/heads/master@{#509581}
-
Hongchan Choi authored
Before audioWorklet.addModule() gets called, BaseAudioContext does not have a valid AudioWorkletThread so it cannot access to the worklet functionality, eventually causing the page to crash. This CL introduces the dynamic thread switching: if the context already started with the regular thread, then switch it with the worklet thread when audioWorklet.addModule() call is resolved. The dynamic thread switching on the real-time audio context makes the context rendering to stop and restart. This might cause audio glitches in the audio stream. With this fix, the attached layout test does not crash anymore. Bug: 774566 Test: worklet-context-interaction.html Change-Id: I2dc8e723a1b88d3a56fbd49aeb4e64c304d48dad Reviewed-on: https://chromium-review.googlesource.com/722126Reviewed-by:
Raymond Toy <rtoy@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#509580}
-
Reilly Grant authored
This flaky test is starting to fail due to timeouts. Accept this until the underlying issue (i.e. shader logic) is fixed. The original change (r507980) attempting to mark this test as Timeout accidentally changed the line for css3/filters/effect-reference-subregion.html instead. TBR=yhirano@chromium.org, fs@opera.com NOTRY=true Bug: 773648, 658305 Change-Id: Ie52945d5158037e600ac24a04533d6d0efaecec9 Reviewed-on: https://chromium-review.googlesource.com/724224Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#509579}
-
Tsuyoshi Horo authored
There is a bug that CORS requests can't work at all when "Bypass for network" in DevTools is enabled. Currently the CORS logic is implemented in DocumentThreadableLoader in the renderer process. If the page is not controlled by a service worker, DocumentThreadableLoader sets the Origin header for the CORS request and sends the request to the browser process. And the browser process sends the request to the network server. But if the page is controlled by a service worker, DocumentThreadableLoader just sends the original request to the browser process. And the browser process sends the request to the service worker. If the service worker doesn't call FetchEvent.respondWith(), the browser process returns a "FallbackRequired" response to the DocumentThreadableLoader. And DocumentThreadableLoader will start the CORS logic such as setting the Origin header. When "Bypass for network" is enabled, InspectorNetworkAgent::WillSendRequest() sets the request service worker mode to None. So the browser process doesn't pass the request to the service worker. But InspectorNetworkAgent::WillSendRequest() is called just before the renderer process sends the request to the browser process. So the request which should be sent to the service worker will directly go to the network server. This CL adds a check of the bypass flag in DocumentThreadableLoader, so that the CORS logic will be correctly executed. Bug: 771742 Change-Id: I923fc9f9e2e361aea3d25ace653c138707d9a682 Reviewed-on: https://chromium-review.googlesource.com/717960Reviewed-by:
Will Chen <chenwilliam@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Takeshi Yoshino <tyoshino@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#509578}
-
Reilly Grant authored
This reverts commit fd493b4b. Reason for revert: Broken build: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win%20x64%20Builder%20%28dbg%29/builds/114259 Original change's description: > Stop building SkCodec > > Bug: 768878 > > Building SkCodec seems to have caused a paint regression on a webpage > without any images. This leads us to suspect "some minor compiler > optimization tickling". Stop building it to confirm. Two CLs rely on > SkCodec: > > "Use SkCodec internally in GIFImageDecoder" > 4fed3346. This introduced building > SkCodec. > > "Enable Skia's SkImageGenerator implementation" > f5eb27c2. This used SkCodec to fix > crbug.com/758459, but that seems to have been fixed in another way. > > In addition, this corrects some formatting in the old code (as > commanded by presubmit), and makes some other minor changes (no more > PassRefPtr, FrameDurationAtIndex now returns a TimeDelta). > > Change-Id: Ic2bdd87740da0232c9c07e27eed6049efc26d76c > Reviewed-on: https://chromium-review.googlesource.com/718918 > Commit-Queue: Leon Scroggins <scroggo@chromium.org> > Reviewed-by: Chris Blume <cblume@chromium.org> > Reviewed-by: Fredrik Söderquist <fs@opera.com> > Reviewed-by: Leon Scroggins <scroggo@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#509570} TBR=scroggo@chromium.org,pdr@chromium.org,fs@opera.com,cblume@chromium.org Change-Id: Ib4c5be2e885f483d881ca65689cb5e9f3dc755df No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 768878 Reviewed-on: https://chromium-review.googlesource.com/724359Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#509577}
-
catapult-deps-roller@chromium.org authored
https://chromium.googlesource.com/catapult.git/+log/733ecb1825d0..75257303afa9 $ git log 733ecb182..75257303a --date=short --no-merges --format='%ad %ae %s' 2017-10-17 nednguyen Make the log of dependency_manager less spammy 2017-10-16 nednguyen Remove dead TBMv1 metrics code 2017-10-16 nednguyen Remove deadcode related to TimelineBasedMeasurement 2017-10-16 dnj [external_modules] Warn on optional import misses. 2017-10-16 nednguyen Revert "Increase the timeout for collecting Chrome trace" 2017-10-16 charliea Remove documentation for the "after_load" power metric 2017-10-07 benjhayden Make breakdown-span cross-reference RelatedNameMaps. 2017-10-16 rnephew [Telemetry] Remove benchmark.ShouldDisable from telemetry. 2017-10-16 benjhayden Allow results.html to use either location.search or location.hash. 2017-10-16 benjhayden Sort results.html by Name by default. 2017-10-11 benjhayden Automatically focus test-picker. 2017-10-16 johnchen Fix when seek times are calculated in media metrics 2017-10-12 benjhayden Simplify histogram-span API. 2017-10-13 benjhayden Add python implementation of RelatedNameMap. Created with: roll-dep src/third_party/catapult BUG=762005 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=sullivan@chromium.org Change-Id: Ibca32f9b7d7b6ba7513fd9bb99ba6b46fbc83dcd Reviewed-on: https://chromium-review.googlesource.com/724100 Reviewed-by: <catapult-deps-roller@chromium.org> Commit-Queue: <catapult-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#509576}
-
Bill Budge authored
- Adds a 'initial_seed' parameter to GetRandomPageBase, which defaults to 0. If non-zero, generates a predictable sequence, using the value as the initial seed. - Adds a unit test for the predictable sequence. Bug: chromium:756050 Change-Id: Iaf718baa2b7d49dc8eda7b0f97aa12b576ddca28 Reviewed-on: https://chromium-review.googlesource.com/703509 Commit-Queue: Bill Budge <bbudge@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#509575}
-