GitLab

Prior to this change, VTVDA would disable reordering when there was no
VUI max_num_reorder_frames syntax element. This is incorrect; excluding
an explicit list of profiles, it should be MaxDpbFrames.

The incorrect behavior is masked during normal playback, because
decoding is typically faster than rendering. This causes the reorder
queue to fill up even though reordering is supposed to be turned off,
and frames therefore get a chance to be ordered correctly.

BUG=634007

Review-Url: https://codereview.chromium.org/2272233002
Cr-Commit-Position: refs/heads/master@{#414499}

The buttons in ToolbarPhone have their y translation modified to make it appear
like they are scrolling with the new tab page. This change fixes the calculation
to cancel this translation while in tab switcher mode.

In addition, this fixes a regression where the buttons would pop in after
defocusing the omnibox instead of sliding in from the side.

BUG=628597

Review-Url: https://codereview.chromium.org/2275073002
Cr-Commit-Position: refs/heads/master@{#414498}

Specifically, when no layout tests are fetched for a particular build,
log a warning and continue instead of raising an exception and aborting.

I noticed this error when running the script on my workstation.

This CL also adds several TODO notes.

BUG=629275

Review-Url: https://codereview.chromium.org/2277303003
Cr-Commit-Position: refs/heads/master@{#414497}

and removing bots not longer on the waterfall.

This is to prepare for auto generation of this file in
 https://codereview.chromium.org/2272603005/.

Note this does not attempt to do any refactoring of what
shards these tests are run on etc, it is only cleanup. That will
be saved for a follow on task.

BUG=chromium:633253

Review-Url: https://codereview.chromium.org/2277003004
Cr-Commit-Position: refs/heads/master@{#414496}

This is for testing the upgrade to 10.11.

BUG=641066
CQ_INCLUDE_TRYBOTS=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
TBR=dpranke@chromium.org,zmo@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2281693002
Cr-Commit-Position: refs/heads/master@{#414495}

BUG=None

Review-Url: https://codereview.chromium.org/2277293002
Cr-Commit-Position: refs/heads/master@{#414494}

This is a belated regression test for https://crbug.com/519120

BUG=523806

Review-Url: https://codereview.chromium.org/2274953003
Cr-Commit-Position: refs/heads/master@{#414493}

BUG=641000

Review-Url: https://codereview.chromium.org/2280713002
Cr-Commit-Position: refs/heads/master@{#414492}

Somehow VS2015 does not apply tail-recursion, and hits stack overflow
even in official build. Crashes were reported on CrOS too.

This patch changes it to loop.

No behavior changes.

BUG=583711, 640869

Review-Url: https://codereview.chromium.org/2267363007
Cr-Commit-Position: refs/heads/master@{#414491}

The program cache was disabled on Adreno 4/5xx due to crashes.

I'm hoping that this issue was caused by invalidations/issues with the
on-disk program cache, possibly with driver updates or other issues.

To test this, I'm re-enabling the in-memory portion of the cache
only. The cached objects will not outlive the GPU process.

I've also confirmed that the related Adreno 3xx bug, crbug.com/510673,
does not impact the Adreno 400 (and I'm guessing 500, but will track
down a device to double check).

We should watch crash rates for gfx::GLApiBase::glProgramBinaryFn to
make sure this change doesn't re-introduce these crashes.

BUG=598060, 486117
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2267163003
Cr-Commit-Position: refs/heads/master@{#414490}

Some cleanup and restructuring in anticipation of a CL to make root scrollers
work across iframes:

-Removed ChildViewportScrollCallback

This was essentially a no-op ViewportScrollCallback that would be used inside
iframe RootScrollerControllers to make everything more consistent. On reflection,
I think this was a bad choice and we'll just have one ViewportScrollCallback that
gets moved between frames. I've removed ChildViewportScrollCallback and folded
RootViewportScrollCallback into ViewportScrollCallback. RootScrollerController's
m_viewportApplyScroll is now NULL for child frames.

- Initialize ViewportScrollCallback in RootScrollerController

This was in FrameView because FrameView previously didn't expose the
RootFrameViewport which is needed in this callback.  FrameView had to expose
that for other reasons so this cleans things up a little and keeps
RootScrollerController more encapsulated.

- Remove isViewportScrollCallback method on Document

RootScrollerController is now exposed so there's no sense in growing Document's
interface footprint.

- Add m_currentViewportApplyScrollHost

This removes the need for effectiveRootScroller to be the element that has the
apply scroll callback and foreshadows changes coming in a CL to split the
RootScrollerController responsibilities across two classes.

BUG=505516

Review-Url: https://codereview.chromium.org/2273163002
Cr-Commit-Position: refs/heads/master@{#414489}

BUG=633022
TEST=webgl2_conformance
R=piman@chromium.org
CQ_INCLUDE_TRYBOTS=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

Review-Url: https://codereview.chromium.org/2278823002
Cr-Commit-Position: refs/heads/master@{#414488}

BUG=640612

Review-Url: https://codereview.chromium.org/2275983002
Cr-Commit-Position: refs/heads/master@{#414487}

BUG=638411

Review-Url: https://codereview.chromium.org/2270143002
Cr-Commit-Position: refs/heads/master@{#414486}

THe tests were marked as flakey after an unexplained increase in
flakiness plus some uncertainty about the baselines. So this
patch rebaselines them and re-enables since we have reason to
believe the flakiness has been addressed.

TBR=wangxianzhu@chromium.org
BUG=638942

Review-Url: https://codereview.chromium.org/2274573006
Cr-Commit-Position: refs/heads/master@{#414485}

BUG=

Review-Url: https://codereview.chromium.org/2268403007
Cr-Commit-Position: refs/heads/master@{#414484}

This was focused on ng_units and ng_margin_strut, though I also updated
some more variables in ng_block_layout_algorithm.

https://google.github.io/styleguide/cppguide.html#Variable_Names

R=ikilpatrick@chromium.org,eae@chromium.org
BUG=635619
NOTRY=true

Review-Url: https://codereview.chromium.org/2272313004
Cr-Commit-Position: refs/heads/master@{#414483}

This has a side effect of causing metrics reporting to be enabled during the session that the pref is changed.

BUG=609987

Review-Url: https://codereview.chromium.org/2248243002
Cr-Commit-Position: refs/heads/master@{#414482}

BUG=633139

Review-Url: https://codereview.chromium.org/2245633002
Cr-Commit-Position: refs/heads/master@{#414481}

Micros to millis instead converted micros to nanos

BUG=640758

TBR=tedchoc@chromium.org

Review-Url: https://codereview.chromium.org/2283433002
Cr-Commit-Position: refs/heads/master@{#414480}

TBR=dschuyler@chromium.org
BUG=640871

Review URL: https://codereview.chromium.org/2272353003 .

Cr-Commit-Position: refs/heads/master@{#414479}

Strings to be shown with ARC's intent picker, these will be displayed on
a dialog used to warn the user while browsing on incognito mode.

BUG=632161
TEST=NA

Review-Url: https://codereview.chromium.org/2267273005
Cr-Commit-Position: refs/heads/master@{#414478}

https://chromium.googlesource.com/chromiumos/platform/system_api.git/+log/c74bf51d..f5afa58d

$ git log c74bf51d..f5afa58d  --date=short --no-merges --format='%ad %ae %s'
2016-08-13 cylee@chromium.org DBus constants: Add a new method SetOomScoreAdj in debugd interface.
2016-07-26 tnagel@chromium.org login_manager: Remove unused D-Bus constants.
2016-07-21 nya@chromium.org Revert "Add a constant for GetFreeDiskSpace()."

BUG=

Review-Url: https://codereview.chromium.org/2272163004
Cr-Commit-Position: refs/heads/master@{#414477}

Certain OEMs are triggering disk reads that are outside of our control.

BUG=640993

Review-Url: https://codereview.chromium.org/2271243004
Cr-Commit-Position: refs/heads/master@{#414476}

Also update the activeSourceBuffers list on track status changes.

BUG=639151

Review-Url: https://codereview.chromium.org/2263823002
Cr-Commit-Position: refs/heads/master@{#414475}

R=eae@chromium.org,ikilpatrick@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2275363002
Cr-Commit-Position: refs/heads/master@{#414474}

Update each of the context menus in AppList to use the ASYNC runtype for menus.
None of the menus had followups to menu closure. I left the current lifetime
of the MenuRunners as is.

TEST=manually tested each context menu, app_list_unittests
BUG=557136

Review-Url: https://codereview.chromium.org/2272023002
Cr-Commit-Position: refs/heads/master@{#414473}

Do not call check-webkit-style with empty affected file list as it tries to check all edited files including the skipped ones

This patch changes _CheckStyle to prevent calling check-webkit-style with empty arguments list if all files got filtered out.

BUG=635619
TEST=third_party/WebKit/PRESUBMIT_test.py

Review-Url: https://codereview.chromium.org/2236993002
Cr-Commit-Position: refs/heads/master@{#414472}

All CDMs released since M43 support the CDM_8 interface, so remove
support for CDM_7 as it is no longer used.

BUG=640437
TEST=browser_tests pass

Review-Url: https://codereview.chromium.org/2280433002
Cr-Commit-Position: refs/heads/master@{#414471}

Update the mash windowing example app to use async context menus.

TEST=manually test example app
BUG=557136

Review-Url: https://codereview.chromium.org/2275783002
Cr-Commit-Position: refs/heads/master@{#414470}

Revert of Use ScaleToEnclosingRect when converting the viewport to window. (patchset #1 id:1 of https://codereview.chromium.org/2258493002/ )

Reason for revert:
This seems to have broken virtual/scalefactor200withzoom/fast/hidpi/static/popup-menu-appearance.html.

Original issue's description:
> Use ScaleToEnclosingRect when converting the viewport to window.
>
> This guarantees that the viewport is always contained in the window.
>
> BUG=none
>
> Committed: https://crrev.com/88fd07f9af5311a6e85502aedca5ce94c9ddfe23
> Cr-Commit-Position: refs/heads/master@{#414452}

TBR=oshima@chromium.org,piman@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=none

Review-Url: https://codereview.chromium.org/2279873002
Cr-Commit-Position: refs/heads/master@{#414469}

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).

Please review the expectation changes, and LGTM as normal. The recipe roller
will *NOT* CQ the change itself, so you must commit the change manually.

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug
(or complain)

build:
  https://crrev.com/b02b5193532977e75ea91ec9d011a6561f43e158 Chromium trybots on linux: kill git fetch after 20 minutes. (tandrii@chromium.org)

R=tandrii@chromium.org
BUG=635641

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Review-Url: https://codereview.chromium.org/2279593003
Cr-Commit-Position: refs/heads/master@{#414468}

This file was added as part of https://codereview.chromium.org/2211473003
but looks like it was done so by mistake. Remove it again.

TBR=fdoray@chromium.org
BUG=616447

Review-Url: https://codereview.chromium.org/2276423002
Cr-Commit-Position: refs/heads/master@{#414467}

Behind --enable-experimental-web-platform-features flag.
Not yet hooked up on Android Marshmallow or below, which
use custom layouts for notifications.

Intent to implement:
https://groups.google.com/a/chromium.org/d/topic/blink-dev/FQxPB5GEQjo/discussion

Screenshot: https://imgur.com/a/SM3tq

Depends on https://codereview.chromium.org/2261283002

BUG=614456

Review-Url: https://codereview.chromium.org/2273033002
Cr-Commit-Position: refs/heads/master@{#414466}

Revert of Remove MessageLoop::current() from base::win::ObjectWatcher. (patchset #5 id:80001 of https://codereview.chromium.org/2125763003/ )

Reason for revert:
Breaks Win10 builder. crbug.com/632184

Original issue's description:
> Remove MessageLoop::current() from base::win::ObjectWatcher.
>
> Why? The fact that there's a MessageLoop on the thread is an
> unnecessary implementation detail. When browser threads are migrated to
> base/task_scheduler, tasks will no longer have access to a MessageLoop
> but they will be able to get the current ThreadTaskRunnerHandle.
>
> Before this CL, ObjectWatcher implemented
> WillDestroyCurrentMessageLoop() to stop the watch when the
> MessageLoop responsible for running the callback was destroyed.
> This prevented the watch callback from being sent to a destroyed
> MessageLoop.
>
> Now that ObjectWatcher keeps a reference to a TaskRunner, this is
> no longer required. The TaskRunner can't be deleted while there are
> references to it. If the underlying MessageLoop has been deleted
> when the watch callback is posted, the callback will simply not run.
>
> Note that the watch will still be stopped when the ObjectWatcher is
> deleted.
>
> TBR=ben@chromium.org
> BUG=616447
>
> Committed: https://crrev.com/76db1513714741d8d6e6dd6e872d50f20b090fce
> Cr-Commit-Position: refs/heads/master@{#407874}

TBR=grt@chromium.org,ben@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=616447

Review-Url: https://codereview.chromium.org/2277333002
Cr-Commit-Position: refs/heads/master@{#414465}

https://pdfium.googlesource.com/pdfium.git/+log/cae6bdfff7e4..43cbe9ea0ff1

$ git log cae6bdfff..43cbe9ea0 --date=short --no-merges --format='%ad %ae %s'
2016-08-25 npm Remove unused methods in CPDF_TextPage and nits
2016-08-25 tonikitoo Drop CPDFSDK_PageView::Annot_HasAppearance
2016-08-25 tsepez Tidy up CFX_PathData

TBR=dsinclair@chromium.org

Review-Url: https://codereview.chromium.org/2278793004
Cr-Commit-Position: refs/heads/master@{#414464}

https://codereview.chromium.org/2272713004/ breaks
official builders so this CL ensures the offical build scripts work as
they used to.

BUG=640877
TBR=dpranke@chromium.org, brettw@chromium.org

Review-Url: https://codereview.chromium.org/2278983002
Cr-Commit-Position: refs/heads/master@{#414463}

Add a reference to the chromestatus entry regarding document level
passive event listeners.

BUG=627104

Review-Url: https://codereview.chromium.org/2272993004
Cr-Commit-Position: refs/heads/master@{#414462}

BUG=640857

Review-Url: https://codereview.chromium.org/2282493002
Cr-Commit-Position: refs/heads/master@{#414461}

svg/W3C-SVG-1.1/filters-composite-02-b.svg and svg/custom/use-clipped-hit.svg
are failing on Win10, and the latter may be flaky. But the flaky one is
mostly failing and only occasionally passing, which would be better reversed.
The former test seems to be always failing, so rebase to see if it's really flaky.

TBR=pdr@chromium.org
BUG=636311,632217

Review-Url: https://codereview.chromium.org/2278683002
Cr-Commit-Position: refs/heads/master@{#414460}