GitLab

* Pull out the CompatibilityTextInputLayout from the EditorTextField
  so it can be used elsewhere.

* Switch to using the CompatibilityTextInputLayout instead of the
  FloatLabelLayout in the autofill preferences.

* Put the AutoCompleteTextView in its own XML file so that the imeOptions
  will be accepted properly by Android.

* Set the statusbar color to black for fullscreen windows like the
  app does.

BUG=603635

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

BUG=623648
TEST=KeyboardControllerTest.DisplayChangeShould

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

In order to build translate_core_browser from projects built
with gyp, variations is needed as a dependency.

BUG=

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

This CL does two things:
1. Track the performance of a toBlob API call. Because toBlob has a call
   back, so we put a timer in the CanvasAsyncToBlob class.
2. Track how often the complete timeout delay happens in toBlob calls.

BUG=612585, 608815

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

This CL updates strings and layout to match the latest spec.

BUG=591958
TEST=manually confirmed
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

These match the in app activity transitions in Android.

BUG=613685

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

by recursively checking for shadow dom

BUG=582317

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

Now that we have a chooser on all supported platforms we can move the
First Device Chooser fallback to content shell, the only place where it's needed.

BUG=524780

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

And nukes WmShellCommon.

BUG=none
TEST=none
R=jamescook@chromium.org

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

This fixes a crash in SSL Interstitial code which expects that cert
exists. Error page with ERR_SSL_SERVER_CERT_BAD_FORMAT error code is
used in this case which matches other platforms.

BUG=622450

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

These tests often change dom/style after a complete paint and test how
the rendering pipeline handles the changes. They are good candidate
for under-invalidation checking.

BUG=619103

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

As we are cleaning up transform tree logic, we need to remove animation
scale computation and data from transform tree. And instead, we compute
it when we need it.

However, computing animation scale may reuse animation scale data which
belongs to other transform nodes, so we need a PropertyTreesCachedData
to store this information, and invalidate it every time we update the
transform tree.

BUG=623564
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

This CL addresses the bug below. Earlier on, we experimented and
decided that we would fallback to SW decoded after 50 consecutive
HW decode errors. However, after an error in keyframe, non-keyframes
would be dropped and not added to the error counter. As a result,
we would wait for 50 keyframe errors before SW fallback, which
takes a long time. This CL fixes the issues resulting from this.

BUG=616968
TEST=Tried the problematic Cisco stream referred in bug.
First 3-5 seconds, we don't get a video(due to HW errors) but works
afterwards(falling back to SW).

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

This is to be enforced per the following spec change:
https://github.com/martinthomson/http-encryption/commit/d11c8263ef3a9fa9cec261898b5d462162045099

BUG=538576

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

History items with extremely long titles are very slow to render,
due to needing to layout the entire title in order to determine where to
cut it off with ellipses. This greatly degrades the performance of MD
History in a profile which has visited several of these items.

This CL trims titles down to at most 300 characters before they are
rendered, which has no visible effect, but greatly improves performance.
On a profile that has visited crashsafari[dot]com, load time is reduced
from ~5000ms to ~1800ms on my Z620. Scrolling performance is also
greatly improved.

BUG=621347
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

MCAD and AndroidVideoDecodeAccelerator share lots of code
to interact with MediaCodec.  This CL splits out much of
that into a new MediaCodecLoop class.

MediaCodecLoop manages driving the I/O loop for MediaCodec
and interacting with a client (AVDA or MCAD).

This CL only affects MCAD.  AVDA's event loop is more
complicated, and will be merged into MediaCodecLoop as
part of a separate CL.

BUG=583082

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

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

It is a dependency of SystemTray.

* Move files to //ash/common/system/chromeos/audio
* Fix include guards
* Fix IWYU

BUG=619636
TEST=ash_unittests

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

This CL adds type checking for dialog elements
found by this.$.dialog. There is no functional
change aside from the type checking.

BUG=393873
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

These libraries are dependencies for Robolectric 3.0.

BUG=522043

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

Since MediaCodec::release() can hang, this CL moves more cases of
it to a separate thread when needed.  Previously, we did this only
during AVDA destruction.  This CL adds support for other cases in
which we replace or clear |media_codec_|.

BUG=613238

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

BUG=

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

This jar is a dependency for Robolectric 3.0.

BUG=522043

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

The notifications are shown at most once per hour, or whenever the severity of the notification changes.

BUG=622590
TEST=./out/Release/unit_tests --gtest_filter=LowDiskNotificationTest.*

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

This jar is a dependency for Robolectric 3.0.

BUG=522043

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

BUG=624958
NOTRY=true

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

App information is a subset of system information, so link both
to chrome://system

BUG=b:29875183

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

We were previously declaring two different classes with the name
blink::TestExtraData, which is an ODR violation. As it happens,
their implementations compiled to the same machine code, which
allowed the tests to pass in most normal circumstances. However,
the ODR violation causes test failures in CFI mode (e.g. [1]) as a
result of stricter type checking. The fix is to move both classes to
an anonymous namespace which makes them internal to their TUs.

[1] https://build.chromium.org/p/chromium.fyi/builders/CFI%20Linux/builds/5924/steps/webkit_unit_tests/logs/WebURLResponseTest.ExtraData

BUG=464797
R=thakis@chromium.org

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

- Before, deepActiveElement() returned the deepest shadow root's
activeElement. Now, it returns the deepest activeElement (which may not be in
the deepest shadow root)
- Buttons 'Add pattern', 'Add custom device', 'Add custom profile' in the
Blackboxing, Devices, and Throttling settings tabs now have default focus
- Now that Dialog's keydown handler is on the body, pressing Esc now closes the
settings dialog, even after the document blurs

BUG=614902

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

The MR dialog will always be opened when starting a PresentationRequest,
even if there are no sinks that support the presentation url.  The
default cast mode will then be some form of mirroring.  This means that
whether the user selects a device in the dialog or not, the promise from
start() will be rejected with an AbortError.  Instead, a NotFoundError
should be used if there were no devices which supported the presentation
url.

BUG=621161

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

This reverts commit 9a07dc6b. Broke styling of
paper-item.

BUG=624680
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

Enables using NV12 textures as video decoder picture buffers on systems
where that's supported - those that use D3D11 video decoding, support
NV12 texture sharing, and can use NV12 as video processor outputs.

The additional copy uses extra power over the new zero-copy DXGI path,
but should work on systems where that hits driver issues, either due to
sharing of the decoder device with ANGLE or with using decoder output
textures as shader resources.

BUG=574292

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

BUG=b:29824233

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

Using update-w3c-deps in Chromium 7b1c45ee.

BUG=

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

Implement BroadcastChannel as specified in https://html.spec.whatwg.org/multipage/comms.html#broadcastchannel

BUG=161070

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

BUG=None

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

This allows Chrome to render at the native resolution on each display on
Windows 10.

BUG=426656,624672

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

In line with
https://security.googleblog.com/2015/10/sustaining-digital-certificate-security.html
this CL requires that all Symantec-issued certificates
after 1 June 2016 be CT qualified, as defined by the
Certificate Transparency in Chrome Policy -
https://www.chromium.org/Home/chromium-security/certificate-transparency

Any certificates that are not CT qualified will cause
an interstitial with ERR_CERTIFICATE_TRANSPARENCY_REQUIRED.

BUG=620178

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

Introduces a new RuntimeEnabledFeature "MediaSourceNewAbortAndDuration"
which enables new behavior corresponding to the recent MSE spec change
[1], fixing cross-platform spec ambiguities. New behavior:
* abort() gives error if there is a remove() in progress. abort() is
  intended to only abort in-progress appends, not removals.
* setting MediaSource.duration to a value which would truncate currently
  buffered media will now result in error. Apps can use explicit
  remove() to perform the desired buffered media truncation prior to
  lowering the duration.
Note that both of these behavior changes are intended to fix
previously ambiguous spec text related to asynchronous range
removals. There is no other strong reason why these two behavior
changes are included in the same CL (other than to reduce some
process redundancy.)
If "MediaSourceNewAbortAndDuration" is not enabled, then the old
behavior remains along with emission of new deprecation messages.
This change only enables that flag in 'experimental' status (see [2]).

Intent to implement thread is at [3].

[1] https://github.com/w3c/media-source/pull/65
[2] http://www.chromium.org/blink/runtime-enabled-features
[3] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/oboI-rINUt0

BUG=623729,398130
TEST=Updated many of http/tests/media/media-source/* and added SBSTest.GetHighestPresentationTimestamp
R=chcunningham@chromium.org, dcheng@chromium.org, holte@chromium.org, tkent@chromium.org

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

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

SM_CXSIZEFRAME from GetSystemMetrics is based off of the primary monitor's DPI.
GetSystemMetricsForHwnd accounts for the system metrics taking into account the
DPI of the HWND.

BUG=426656

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