- 27 Oct, 2018 10 commits
-
-
Jazz Xu authored
Change-Id: Ic3f0448ae77c9226421132ce911181f53b5ceb7d Reviewed-on: https://chromium-review.googlesource.com/c/1303099Reviewed-by:
Tommy Steimel <steimel@chromium.org> Commit-Queue: Jazz Xu <jazzhsu@chromium.org> Cr-Commit-Position: refs/heads/master@{#603271}
-
Fredrik Hubinette authored
This should make VP9Decoder set color spaces on returned video frames correctly on windows and chromeos. Bug: 647725, 847573 Change-Id: I602e61e078795a511caef134256a0676199f031e Reviewed-on: https://chromium-review.googlesource.com/c/1298635 Commit-Queue: Fredrik Hubinette <hubbe@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#603270}
-
Tim Haloun authored
- Move QoSCreateHandle to a background task, letting critical socket operations continue unblocked while it executes. - Improve resetting handle when it returns REINITIALIZATION_NEEDED - Widen unit tests - Undo ifdef disabling QOS that was added because of hangs/stalls noted in bug 812137 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I383955c2a218f23974a3f5e7044ae0464e99a43f Bug: 812137, webrtc:5836 Reviewed-on: https://chromium-review.googlesource.com/c/1195936Reviewed-by:
Ryan Hamilton <rch@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Tim Haloun <thaloun@chromium.org> Cr-Commit-Position: refs/heads/master@{#603269}
-
Nektarios Paisios authored
This reverts commit eb17833e. Reason for revert: Broke linux-chromeos-dbg again. AXPlatformNodeDelegateBase::Create and GetData are not defined. Original change's description: > Reland "Adds code in ViewAccessibility to manage the focus of AXVirtualView descendants" > > This is a reland of cb9c3091 > > R=dmazzoni@chromium.org,aleventhal@chromium.org > TBR=afakhry@chromium.org,ellyjones@chromium.org,sky@chromium.org > Bug: 811277 > > Original change's description: > Adds code in ViewAccessibility to manage the focus of AXVirtualView descendants > > Also renamed some methods to make interface more consistent. > In preparation for more changes in AXVirtualView. > > Change-Id: I815d6d941f18ef84864636bc02423af20b0bbc97 > Reviewed-on: https://chromium-review.googlesource.com/c/1303093 > Reviewed-by: Nektarios Paisios <nektar@chromium.org> > Commit-Queue: Nektarios Paisios <nektar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#603255} TBR=ellyjones@chromium.org,dmazzoni@chromium.org,sky@chromium.org,afakhry@chromium.org,nektar@chromium.org,aleventhal@chromium.org Change-Id: I954e26880106e51fe78daa79717300f5ab833341 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 811277 Reviewed-on: https://chromium-review.googlesource.com/c/1303556Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#603268}
-
Xiaoqian Dai authored
Bug: 898403 Change-Id: If85fb9d0c90c583110f96a712ae50719c0a3925a Reviewed-on: https://chromium-review.googlesource.com/c/1300105 Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#603267}
-
jonross authored
VizDisplayCompositor has been on my default on the CQ for a while. However as we've been preparing for launching to stable, we've realized that we have no coverage of the non-Viz path. So we currently can't be sure that nothing has broken. We want to bring up three test suites on FYI bots, with Viz Disabled. So that we can get coverage back. These are for Linux, Windows, Android and Mac, as Viz is not yet enabled on Chrome OS. I plan to remove this once we are closer to launch: M-71 TEST=browser_tests, content_browsertests, content_unittests. Change-Id: Icd32248beeab3788070bbab10a194f9046c652d9 Reviewed-on: https://chromium-review.googlesource.com/c/1302693Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#603266}
-
danakj authored
The call in SetRootGraphicsLayer() comes from this CL: https://codereview.chromium.org/1078473002/diff/100001/Source/web/WebViewImpl.cpp#newcode4168 In that CL it mentions that visibility is not always propagated to the WebViewImpl, but in a racey way. At that time WebViewImpl would initialize its compositor on line 452 after SetVisibilityState on line 449. This means at startup the compositor's visibility would not be set. It would only be toggled if the browser send a shown IPC to the renderer, which it appears did not always end up arriving. Things have changed significantly since then. We now SetVisible on the compositor in order to start its scheduler. At the time we had a separate start signal via SetLayerTreeHostClientReady(). So now RenderWidget would set the compositor as visible if its marked as shown when it is created. The call in SetRootLayer was moved in 7e410b31 from WebViewImpl::attachPaintArtifactCompositor() which included - // TODO(jbroman): This is cargo-culted from setRootGraphicsLayer. Is it - // necessary? - m_layerTreeView->setVisible(page()->isPageVisible()); So I would say no it is not. R=enne@chromium.org Change-Id: Icaea3fb4b164b9b4de348dd2e216c4a6a3344b60 Bug: 896836, 894899 Reviewed-on: https://chromium-review.googlesource.com/c/1298341Reviewed-by:
enne <enne@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#603265}
-
Abhishek Bhardwaj authored
This is a reland of https://crrev.com/c/1297474. This change adds functionality to support lock screen notifications for Android. The wake lock module now listens to dark resume notifications from the power manager. It - 1. Starts a timer to check for partial wake locks acquired by Android. 2. After the timer in 1 expires, if no partial wake lock is acquired the power manager is requested to re-suspend the system. If a partial wake lock is acquired, then another hard timeout timer is set and also an observer to wake lock release is set. 3. If wake lock is released, the system is re-suspended immediately. 4. If a wake lock is still acquired but the hard timeout expires then the system is re-suspended immediately. 5. If the system transitions to a full resume all dark resume related state and timers are cleared. On top of this change - 1. Changes were added to fix linker errors by declaring static constants in the source file as well. 2. Refactored some functions in the test code. BUG=chromium:898297 TEST=Unit tests and end to end test with Android applications. Change-Id: I573f130fad2ed092d8acb83fb3319614b4ce8e02 Reviewed-on: https://chromium-review.googlesource.com/c/1302866Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Commit-Queue: Abhishek Bhardwaj <abhishekbh@chromium.org> Cr-Commit-Position: refs/heads/master@{#603264}
-
Stephen Martinis authored
The URL structure of the build info returned by `git cl try-results` is different on LUCI than it was on buildbot. This CL changes git_cl.py to instead look at the build_address of the build to determine the build number. Bug: 891729 Change-Id: I448638178942f2adbbb23c5dd947e305821a5417 Reviewed-on: https://chromium-review.googlesource.com/c/1302097 Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#603263}
-
Julie Jeongeun Kim authored
This is a reland of e14722dd Original change's description: > Move the APIs using XRANR to ui/base/x folder > > It creates x11_display_util.cc/h files and moves the APIs to > get display information using XRANR from DesktopScreenX11 to > share the implementation with Ozone/X11. > > 'GetXrandrVersion' is to get xrandr version, > 'GetFallbackDisplayList' is to get a fallback display and > 'BuildDisplaysFromXRandRInfo' is to get a list of displays from > the current screen. > > It also moves 'GetICCProfileForMonitor' from DesktopScreenX11 > to x11_util.cc. > > These APIs are required for Ozone/X11 as well. This change doesn't > bring any behavioral changes. > > Bug: 891175 > Change-Id: Idb42b1929b7bfab4501ced4403fc176342ebdada > Reviewed-on: https://chromium-review.googlesource.com/c/1295762 > Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com> > Reviewed-by: Dan Erat <derat@chromium.org> > Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#602634} Bug: 891175 Change-Id: I742eec8285b023adda84d28d68a21f7545a87f8c Reviewed-on: https://chromium-review.googlesource.com/c/1301036Reviewed-by:
Dan Erat <derat@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#603262}
-
- 26 Oct, 2018 30 commits
-
-
Chris Mumford authored
GetNetworkChangeManager was incorrectly added in r577168 but was never called. This change removes that vestigial code. Bug: 836188 Change-Id: I618712829d04e94c1bb4e2c1d3fe5c16475daa6f Reviewed-on: https://chromium-review.googlesource.com/c/1271556Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Chris Mumford <cmumford@chromium.org> Cr-Commit-Position: refs/heads/master@{#603261}
-
John Rummell authored
Adding the annotation makes it clear which fields are protected by base::Lock, and enables compile-time analysis to verify this. BUG=893739,887645 TEST=compiles Change-Id: Ideddb22c0687168d25ceab9ad30f32797862fcfd Reviewed-on: https://chromium-review.googlesource.com/c/1302323Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#603260}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a4f6a37d..6cc0ff81 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I5cae1492c12250d85f78b246eb682391a2876b8f Reviewed-on: https://chromium-review.googlesource.com/c/1302324Reviewed-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@{#603259}
-
Etienne Bergeron authored
This event will help figuring out a bug happening with sampling profiler. We currently don't know if the event is emitted from tracing sampler profiler or from UMA sampling profiler. This event should be rare, only on error cases. R=oysteine@chromium.org Change-Id: Id761ef1744c6a2ec924992229ce55e8bc6deac87 Reviewed-on: https://chromium-review.googlesource.com/c/1301968Reviewed-by:
oysteine <oysteine@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#603258}
-
Jun Mukai authored
With recent fixes for multi-display (crbug.com/892714), now some tests in tab-dragging works. Still the test code needs to wait for the bounds changes, since related display ID change arrives asynchronously. Two tests are still failing because of other reasons. BUG=890071 TEST=single_process_mash_interactive_ui_tests Change-Id: I2b73f5ded68fcf0431b67d03737cd137ea57e3d1 Reviewed-on: https://chromium-review.googlesource.com/c/1300689 Commit-Queue: Jun Mukai <mukai@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#603257}
-
rajendrant authored
Bug: 895035 Change-Id: Ie95cd3888fad2a45d7f0946f1a5c21bbb482cae7 Reviewed-on: https://chromium-review.googlesource.com/c/1297245Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#603256}
-
Nektarios Paisios authored
This is a reland of cb9c3091 R=dmazzoni@chromium.org,aleventhal@chromium.org TBR=afakhry@chromium.org,ellyjones@chromium.org,sky@chromium.org Bug: 811277 Original change's description: Adds code in ViewAccessibility to manage the focus of AXVirtualView descendants Also renamed some methods to make interface more consistent. In preparation for more changes in AXVirtualView. Change-Id: I815d6d941f18ef84864636bc02423af20b0bbc97 Reviewed-on: https://chromium-review.googlesource.com/c/1303093Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#603255}
-
danakj authored
The test takes a screen wake lock in an iframe, then navigates the iframe to another origin, and verifies the lock is released. The problem is the lock is released when the original iframe's renderer tears down and sends FrameHostMsg_SwapOut_ACK to the browser. But navigation in the iframe can complete before that (it's a race). So the test now waits for the old frame's RenderFrameHost to be cleaned up before verifying the lock is released. R=avi@chromium.org Change-Id: I4aed27d1a78b8fdf6451228e3ee125bd465f6f4f Bug: 899384 Reviewed-on: https://chromium-review.googlesource.com/c/1303176Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#603254}
-
Robert Liao authored
If we set |compositor_| during AddedToWidget() and not call Play(), the compositor could shutdown and we would never clear |compositor_| since we're not registered as an AnimationObserver and will miss OnCompositingShuttingDown(). BUG=899112 Change-Id: If1dbe4ae9db80d55d3d5db6d939da6008bf97160 Reviewed-on: https://chromium-review.googlesource.com/c/1300694 Commit-Queue: Robert Liao <robliao@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Reviewed-by:
Malay Keshav <malaykeshav@chromium.org> Cr-Commit-Position: refs/heads/master@{#603253}
-
Jun Mukai authored
My recent change on client_root actually had a side effect; the window may change its display when the display is gone (e.g. disconnected). Window server should send DisplayChanged event even in such case. BUG=890071 TEST=the new test case covers Change-Id: I8566e6439bc8e87a0e3252aded8c9aa08cb1c7a9 Reviewed-on: https://chromium-review.googlesource.com/c/1302734 Commit-Queue: Jun Mukai <mukai@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#603252}
-
Johannes Henkel authored
Just using std::move appropriately is probably sufficient for avoiding extra copies and it's easier to understand what's going on. Also less code. Bug: chromium:891377 Change-Id: I321e969bdede991c223cf842a6a572704d060f11 Reviewed-on: https://chromium-review.googlesource.com/c/1302109 Commit-Queue: Johannes Henkel <johannes@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#603251}
-
Luke Zielinski authored
This includes things like old prefs, metrics and finch features. Bug: 662944 Change-Id: Ib7199895bb3b588efcb88c8898eb696b75717fa8 Reviewed-on: https://chromium-review.googlesource.com/c/1294130 Commit-Queue: Varun Khaneja <vakh@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#603250}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/f74d12074e19..d8ed054e9af7 git log f74d12074e19..d8ed054e9af7 --date=short --no-merges --format='%ad %ae %s' 2018-10-26 sammc@chromium.org chromite: fix cros_mark_as_stable --list_revisions. Created with: gclient setdep -r src/third_party/chromite@d8ed054e9af7 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=chrome-os-gardeners@chromium.org Change-Id: I07670c8742410463d5c3666a2261f755af5cb1d2 Reviewed-on: https://chromium-review.googlesource.com/c/1302713Reviewed-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@{#603249}
-
danakj authored
These tests do a navigation then open tabs, measuring the number of RenderProcessHosts that exist. However the initial navigation does not wait for the original RenderProcessHost being navigated away from to be destroyed. Since that does not happen when the navigation is completed, but once the old renderer does a SwapOut_ACK, this test races with the SwapOut_ACK and counts the wrong number of processes if it does not wait for that first. R=avi@chromium.org Change-Id: I844cef55bd8bce3abb5df2820976a7d14354dfbb Bug: 442785 Reviewed-on: https://chromium-review.googlesource.com/c/1302860 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#603248}
-
Khushal authored
The decode ref is always released for an upload task, even if it is cancelled. But the ref was being added only when the task runs in the case of upload only tasks for bitmaps. Fix that. R=ericrk@chromium.org Bug: 899202,899198 Change-Id: I884755e6f4a7ad3bc7fcf93b762246695c732493 Reviewed-on: https://chromium-review.googlesource.com/c/1302495Reviewed-by:
Eric Karl <ericrk@chromium.org> Commit-Queue: Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#603247}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1ef5883ceab7..e060ac16d2fc Created with: gclient setdep -r src-internal@e060ac16d2fc The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I1128b61428a4bedb2583aadbd8a657e115f4a8dd Reviewed-on: https://chromium-review.googlesource.com/c/1302794Reviewed-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@{#603246}
-
Etienne Bergeron authored
We recently added error code to sampling profiler. This CL is whitlisting it's args to get the error code. see: https://cs.chromium.org/chromium/src/base/profiler/native_stack_sampler_win.cc?g=0&l=455 if (error_code != NATIVE_STACK_SAMPLER_SUCCESS) { TRACE_EVENT_INSTANT1(TRACE_DISABLED_BY_DEFAULT("cpu_profiler"), "RecordStackFramesFailed", TRACE_EVENT_SCOPE_THREAD, "error_code", NativeStackSamplerErrorToString(error_code)); } R=oysteine@chromium.org Bug: 867931 Change-Id: I1134ccdaaa0586d4102760d8cfc4df2869539f3d Reviewed-on: https://chromium-review.googlesource.com/c/1301835Reviewed-by:
oysteine <oysteine@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#603245}
-
Francois Doray authored
We want to experiment with more aggressive throttling for BEST_EFFORT tasks. With this experiment, there can be multiple seconds delay before a BEST_EFFORT task is scheduled. Because it is currently necessary to run a BEST_EFFORT task to stop tracing, using the chrome://tracing UI is painful when the experiment is enabled. This CL fixes this issue by changing the priority of the tracing coordinator service backend TaskRunner from BEST_EFFORT to USER_VISIBLE. Note that USER_VISIBLE is the appropriate priority for a task that may affect the UI. Bug: 831835 Change-Id: Iaebeddd006f802d8f73694ef4817ea976490b6a3 Reviewed-on: https://chromium-review.googlesource.com/c/1302321Reviewed-by:
oysteine <oysteine@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#603244}
-
Jesse McKenna authored
This involves changing SequenceSortKey from high == important to low == important, because IntrusiveHeap is a min-heap (as opposed to std::priority_queue, which is a max-heap). Bug: 889029 Change-Id: Ieeb2707d0112389b6cb7f4d187ec447bc58bef5a Reviewed-on: https://chromium-review.googlesource.com/c/1302319 Commit-Queue: Jesse McKenna <jessemckenna@google.com> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#603243}
-
Brian White authored
Talking with Bruce Dawson, it could be helpful to know all the generated boundary values in order to discern if there is a pattern. Bug: 836238 Change-Id: I40ddda5e93d298508fb89fe828245fea39c98b6c Reviewed-on: https://chromium-review.googlesource.com/c/1302315 Commit-Queue: Brian White <bcwhite@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#603242}
-
Xianzhu Wang authored
For a composited object whose layout location is at (10.5, 10.5), we snap the layer location to (11, 11), and keep a subpixel accumulation (-0.5, -0.5). RoundIntPoint(LayoutUnit(-0.5, -0.5)) is zero to ensure that the contents of the composited object will paint at correct location. Previously in CompositedLayerMapping::UpdateAfterPartResize() we used FloatSize::RoundedIntSize() which rounded (-0.5, -0.5) to (-1, -1) (which is based on the roundf() behavior), causing the iframe's document layer to be placed at unwanted -1px offset. Now use LayoutSize::RoundedIntSize() to keep consistent pixel snapping behavior. Bug: 898941 Change-Id: I50b27565850061aec9cffffbe77061570683610b Reviewed-on: https://chromium-review.googlesource.com/c/1302327Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#603241}
-
Alex Newcomer authored
Moves functions to match their orderings in h and cc. Also removes a little dead code. Bug: 899297 Change-Id: I9c8202f5c24c811025db6dadf72edd9d2f73f4bc Reviewed-on: https://chromium-review.googlesource.com/c/1302822Reviewed-by:
Weidong Guo <weidongg@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#603240}
-
siyua authored
The logic was moved to a legal message view class in the view_util.*, and when removing, metrics logging was not correctly set. Bug: 898724 Change-Id: I8f285b61003a49cdc884641a9ff526b1760abcb0 Reviewed-on: https://chromium-review.googlesource.com/c/1298713Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Siyu An <siyua@chromium.org> Cr-Commit-Position: refs/heads/master@{#603239}
-
Christopher Cameron authored
This splits AppShimHost into two separate structures, along its mojo interface lines. The AppShimHostBootstrap class is created as soon as a connection is created with the app shim process, and awaits the LaunchApp mojo call, through which the AppShimHostBootstrap will indicate its profile and app id. The AppShimHost class is created only after the LaunchApp call is made, and takes ownership of the AppShimHostBootstrap. The next patch in this sequence will allow the AppShimHost to be created independently AppShimHostBootstrap, to support the situation where Chrome launches the app shim. Bug: 896917 Change-Id: I0d240a9ded78fcea3a0a6e26a2bad466402d08fb Reviewed-on: https://chromium-review.googlesource.com/c/1299668Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#603238}
-
David Quiroz Marin authored
Use of new macro and added base=true to avoid extra suffix histograms Bug: 894043 Change-Id: I2f87f092a01897c43fcd8b61639967fed2330f50 Reviewed-on: https://chromium-review.googlesource.com/c/1283833 Commit-Queue: David Quiroz Marin <davidqu@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
Robert Kaplow (OOO until Nov6) <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#603237}
-
Yuri Wiitala authored
Fixes GLScaler::SupportsPreciseColorManagement() by using GL extension strings to detect the required GLES2 extensions. Also, use of half- floats in textures is governed by the "type" argument to glTexImage2d(), and not the "internal format" argument. Bug: 870036 Change-Id: I67e90cbadeb0b185025bce01c56b0f9e89e70a71 Reviewed-on: https://chromium-review.googlesource.com/c/1298643Reviewed-by:
Xiangjun Zhang <xjz@chromium.org> Commit-Queue: Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#603236}
-
Etienne Bergeron authored
There are strange behaviors observed in the field with the sampling profiler. It seems there are two running sampling profiler but only one is reporting events. This CL is adding trace events to help investigate this problem. R=wittman@chromium.org Bug: 882982 Change-Id: I70925e841b8a1f0e47564350d142f056d8b8ae99 Reviewed-on: https://chromium-review.googlesource.com/c/1302318Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#603235}
-
James Hawkins authored
R=hansberry@chromium.org Bug: 899324 Test: none Change-Id: I762ae359249c60481ba4866703aa1e7fbbc6552e Reviewed-on: https://chromium-review.googlesource.com/c/1302330Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: James Hawkins <jhawkins@chromium.org> Cr-Commit-Position: refs/heads/master@{#603234}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: I824af75f53227fa0df93dbf34cbe6b64b565a96a Reviewed-on: https://chromium-review.googlesource.com/c/1303044Reviewed-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@{#603233}
-
Fady Samuel authored
This is no longer used. Change-Id: I395e5e28f987326011e82b81c27534f23a8e6c7d TBR: sky@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/1302096 Commit-Queue: Fady Samuel <fsamuel@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#603232}
-