GitLab

Now retrieving driver information with PnP Configuration Manager, which is much
faster than using Setup API.
With the new approach we are now able to fetch information from the actual
device driver, instead of the software interface on top which seems to be always
provided by Microsoft.

BUG=512433,642604
R=toyoshim@chromium.org

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

BUG=641995

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

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).

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

build:
  https://crrev.com/fedd382eb821d2766ff835440d6017b357b7edff Remove old dartium_factory builders, clean up slaves.cfg files. (whesse@google.com)

TBR=martiniss@chromium.org,phajdan.jr@chromium.org
BUG=https://bugs.chromium.org/p/chromium/issues/detail?id=618379

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

path() is being deprecated, GetPath() has better checking against wrong use.

For more context, see https://codereview.chromium.org/2275553005/.

R=mmenke@chromium.org
BUG=640599

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

A mostly-automated change to convert instances of WrapUnique(new Foo(...)) to
MakeUnique<Foo>(...). See the thread at
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/iQgMedVA8-k
for background.

To avoid requiring too many manual fixups, the change skips some cases that are
frequently problematic. In particular, in methods named Foo::Method() it will
not try to change WrapUnique(new Foo()) to MakeUnique<Foo>(). This is because
Foo::Method() may be accessing an internal constructor of Foo.

Cases where MakeUnique<NestedClass>(...) is called within a method of
OuterClass are common but hard to detect automatically, so have been fixed-up
manually.

The only types of manual fix ups applied are:
1) Revert MakeUnique back to WrapUnique
2) Change NULL to nullptr in argument list (MakeUnique cannot forward NULL
   correctly)
3) Add base:: namespace qualifier where missing.

WrapUnique(new Foo) has not been converted to MakeUnique<Foo>() as this might
change behaviour if Foo does not have a user-defined constructor. For example,
WrapUnique(new int) creates an unitialised integer, but MakeUnique<int>()
creates an integer initialised to 0.

git cl format has been been run over the CL. Spot-checking has uncovered no
cases of mis-formatting.

  BUG=637812

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

This is a preparation to erase animations_ data stored in ElementAnimation.

BUG=592873
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

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

This removes maxEffectRect(), determineMaximumEffectRect() and the
associated state (m_maxEffectRect) from FilterEffect. The replacement is
the new method absoluteBounds() that computes bounds for the node in
question using the filter primitive (sub)region and the filter region.
This should match what determineMaximumEffectRect() was computing for
use from SVGFilterPainter.

BUG=642035
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

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).

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

build:
  https://crrev.com/9202514fa25ad6f5c113e9f111c6af35254d5b5e Allow more max fail fallback tasks in perf builder (shinyak@chromium.org)

TBR=martiniss@chromium.org,phajdan.jr@chromium.org
BUG=606987

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

The Wayland platform for Ozone currently implements the following
deprecated API from SurfaceOzoneCanvas:

* CreateViewGLSurface
* CreateOffscreenGLSurface
* GetNativeDisplay
* LoadEGLGLES2Bindings

That code is moved into a separate GLOzoneEGLWayland helper class
implementing GLOzoneEGL. This also allows to better handle the fact that
the support is restricted to the kGLImplementationEGLGLES2
implementation.

Also OzonePlatformWayland is updated to prepare support for the newer
variants of InitializeForUI and InitializeGPU with initialization
parameters, even if every callers do not set these parameters correctly
at the moment.

Currently, InitializeGPU checks whether surface_factory_ has been
initialized and otherwise creates a WaylandSurfaceFactory with a null
Wayland connection. Some comments are added to clarify these two
workarounds. In particular, the verification could be made clearer with
args.single_process when the migration to the new InitializeGPU variant
is complete. Additional changes better protect the part of
WaylandSurfaceFactory that assumes a non-null Wayland connection and
ensure that we always fullfill this assumption inside the
WaylandSurfaceFactory and WaylandCanvasSurface helper classes.

R=rjkroege@chromium.org
BUG=none

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

This replaces key_exchange_info with key_exchange_group at all layers
but net::SSLInfo, fixing key_exchange_info's type issues. Then we route
it over to DevTools as an optional new field "Key Exchange Group".

Later work, once the TLS 1.3 draft 15 negotiation is implemented, will
make the DevTools able to handle missing key_exchange. In 1.3, what
DevTools currently calls a "Key Exchange" isn't really meaningful and
is just described by the group. (https://crbug.com/639495)

Screenshots:
https://drive.google.com/folderview?id=0Bz14lOW5Hke4VFlBVXJOY0Z0cUU&usp=sharing

(Note: the TLS 1.3 picture is a mock of how it will look when the
new cipher suite negotiation is implemented and a second change made.)

BUG=639421,618035

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

R=rjkroege@chromium.org
BUG=none

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

TBR=haraken@chromium.org,oilpan-reviews@chromium.org
BUG=645253

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

BUG=644510

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

Revert of Add GetAssociatedOutputDeviceID support to pulse. (patchset #7 id:120001 of https://codereview.chromium.org/2258143002/ )

Reason for revert:
Breaks audio playback on Linux Chrome OS
target_os = "chromeos" in gn args

( SoundsManager::Play fails).

Original issue's description:
> Add GetAssociatedOutputDeviceID support to pulse.
> We use the bus path for identification of devices. I have verified that it works with a headset connected with 3.5 mm connectors, and with a USB headset. Another nice thing with  his approach is that we should be able to easily find if a webcam has a built-in mic, since in this case the webcam and mic will typically be connected via the same USB port.
>
> BUG=636300
>
> Committed: https://crrev.com/cff5a1f78bd76f764a70efcdb9b908ff6a87c60f
> Cr-Commit-Position: refs/heads/master@{#415024}

TBR=guidou@chromium.org,tommi@chromium.org,maxmorin@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=636300

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

Add a CHECK() to crash the browser if a destruction order problem is
encountered.

This will be reverted once the information is collected.

BUG=641013

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

This patch moves |m_caretVisibility| from |CaretBase| class to |FrameCaret|
since |m_caretVisibility| is used only in |FramreCaret| class for improving code
health.

BUG=n/a
TEST=n/a; no behavior changes

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

Previously we invalidate paint (which will also cause raster invalidation)
of the subtree if z-index, transform changed on an object which will not
be composited. This requires logic to precisely predict compositing status
which is fragile and causes unnecessary paint invalidations.

We don't need to invalidate paint of object which just changes z-index,
transform etc. We can invalidate raster if needed after painting.

If a cached display item is moved out of the original chunk, invalidate
raster for it on both the old chunk and the new chunk.

If a cached display item is moved within the chunk behind any other
cached display item, invalidate raster for it.

Otherwise we don't invalidate raster.

BUG=526191
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

BUG=627008
TBR=jsbell

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

There is still only a single Blimp tab, and the logic is for now very
simple: If there is already a blimp tab available, a new tab will be
WebContents based. If there are no blimp tabs, a blimp-based tab will
be created.

Also, when tabs are closed, it takes a while before the tab is really
destroyed, in case the user wants to undo the action. This feature
stays, but if the user selects "New Tab" or clicks the new tab button,
all the pending closures are first committed, ensuring that the tab
to be created might become a blimp tab, even if the current blimp tab
was pending closure.

Before this CL, the value 0 was always used fro the tab ID. This meant
that there would be a mixup between tabs that are closed and new tabs
that are created. This CL changes this so that each BlimpContentsImpl
gets its own unique ID, created client-side, and transferred to the
engine to be used for all communication regarding that tab, by an
update to the TabControlFeature to now include the ID.

The NavigationFeature is also updated to support receiving messages
after BlimpContentsImpl has been destroyed, which may happen, and
it now just logs those errors.

To ensure that this is visible in the tab switcher as well, a
workaround is added to ensure that the theme color is always shown,
even when on the new tab page. This is important in case where there
are many new tab pages, and one can not see which one is the blimp
tab, since the theme color is only updated when the tab navigates
away from the NTP.

To support the multiple IDs on the engine side, the Tab class is now
the implementor of the
EngineRenderWidgetFeature::RenderWidgetMessageDelegate instead of the
BlimpEngineSession. IME and compositor protos use the ID of the current
tab for their messages.

BUG=644467, 644774

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/091029905a83..d961ec30c833

$ git log 091029905..d961ec30c --date=short --no-merges --format='%ad %ae %s'
2016-09-08 benjhayden Delete FailureValue
2016-09-08 benjhayden Move unit.html from value to base

TBR=catapult-sheriff@chromium.org

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

It served its purpose and is no longer needed. This is a simple revert
of r414123, r413080, r412464, r411775, and r410031.

BUG=623986

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

Now ChromeCast has switched to use mojo Renderer, nobody is using this
path any more.

BUG=571155
TEST=No functionality change

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

- Pin keyboard backspace can be held down to keep deleting.
- Pin keyboard key events used to doubled on settings/options.
- Pin keyboard placeholder displays correct message.
- Removed "clear" string, since the backspace is icon only now.
- Bubble now disappears when user presses a pin keyboard button after a wrong password has been entered.

BUG=642587
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

It fails rather than times out after:
https://crrev.com/6f3528e03445a08f492462007724dd25120d372a

BUG=508734
TBR=jsbell

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

https://chromium.googlesource.com/chromium/src/+/8e6237357

BUG=643623
TBR=fmalita@chromium.org

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

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

BUG=

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

R=rch@chromium.org
CC=jokulik@chromium.org,fayang@chromium.org
BUG=

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

(Redo due to http://crbug.com/645052)

By returning a signed simple challenge that can actually be parsed as SignedData, we allow callers of the FakeCryptohomeClient to extract the original data back and process it, making for better fake behavior and simpler tests.

Note that the signature is purposedly not verifiable in the FakeCryptohomeClient.

BUG=643245
TEST=chromeos_unittests; unit_tests and components_unittests also pass
TBR=xiyuan@chromium.org

Committed: https://crrev.com/911199cb30f608636c79d47e50dca84735e3a08f
Cr-Commit-Position: refs/heads/master@{#417118}

patch from issue 2297193006 at patchset 120001 (http://crrev.com/2297193006#ps120001)

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/2f63c684f0aa..091029905a83

$ git log 2f63c684f..091029905 --date=short --no-merges --format='%ad %ae %s'
2016-09-08 benjhayden Make ValueSet use an ES6 Map.
2016-09-08 benjhayden Improve usability of value-set-table's groupby-picker.

TBR=catapult-sheriff@chromium.org

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

This is a step towards turning all tree outlines into independent web components,
removing global styles related to it and allowing more components to encapsulate their inner details.

BUG=none

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

Currently, we only send encodedDataLength for redirects. However, we
already know how much we read when sending ResponseReceived. This will
improve reporting for failed requests, as they don't get loadingFinished
with full encodedDataLength.

Previous CL: https://codereview.chromium.org/2101073002
BUG=622018

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

NativeWidgetMus::SetBounds() was not correcting for the display origin.

Also fix NativeWidgetMus::GetBoundsInScreen(), which had the same problem.

BUG=645291,644895
TEST=run mash with --multi-display, shelf appears on second display

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

SVGImageForContainer tracks a container zoom factor independently of
the actual container size.  This zoom factor needs to be accounted for
in imageForCurrentFrame() -- otherwise we end up producing an SkImage
with a different size than reported by SVGImageForContainer::size().

The easiest way to accomplish this is to use size() when calling
SVGImage::imageForCurrentFrameForContainer(), instead of the unzoomed
m_containerSize.

BUG=643623
R=fs@opera.com,davve@opera.com

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

Potentially used in: https://codereview.chromium.org/2280513002/

R=tsergeant@chromium.org
BUG=598017

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

BUG=641215

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

Now that Oilpan is shipped, we no longer need public/features.gni.

BUG=

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/d046985fcb95..2f63c684f0aa

$ git log d046985fc..2f63c684f --date=short --no-merges --format='%ad %ae %s'
2016-09-08 benjhayden Approve Destructuring and Subclassable Built-ins in style-guide.md.
2016-09-08 benjhayden Display "(empty)" and "(missing)" in value-set-table

TBR=catapult-sheriff@chromium.org

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

Assertions are removed from some of the InputConnection methods that
merely post on UI thread. In doing so, mPendingAccent was changed to be
accessed only on UI thread.

However, beginBatchEdit() / endBatchEdit() implementations are quite
complicated and no evidence calling those on UI thread was found so far.

Also, for get* methods we return cached results.

BUG=643477

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

This removes some duplicated code.

BUG=634443

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

If a _loadCompletions was started while an earlier one was active, the earlier one could still be used.

BUG=none

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