GitLab

Makes pages in the WebVR benchmark exit VR and navigate to a blank page
after everything else is done. This is to prevent unnecessary heat
generation caused by staying in VR while the traces are being processed.

This only has a minimal affect on devices that process the trace data
quickly, but on very slow devices (e.g. Raspberry Pis), this has
a significant effect on generated heat.

Bug: 
Change-Id: I21b7efdf141b4241f91f29908827c9f430a11c9c
Reviewed-on: https://chromium-review.googlesource.com/728337
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#510172}

The ax_dump_tree output puts out a lot of information, which can be too
noisy to efficiently read. This supports property filtering as follows:

ax_dump_tree --filters=[FILTERS_TEXT_FILE]

The filters file can have @ALLOW, @ALLOW-EMPTY and @DENY rules, similar
to the dump accessibility tree browsertests. It is not necessary to have
a platform prefix (e.g. @WIN- or @MAC-). The role of the object cannot
be filtered, but any other properties can. If no filters are provided
then all properties are shown.

Example, to filter out everything except role, name and value, use:
@ALLOW:name=*
@ALLOW:value=*

Put each filter on a separate line. For more info on writing rules, see
https://cs.chromium.org/chromium/src/content/test/data/accessibility/readme.md

Bug: 771747
Change-Id: If15a5c6f6baf6a1827749dae16825242a0913913
Reviewed-on: https://chromium-review.googlesource.com/725879
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510171}

This reverts commit 0ad0d051.

Reason for revert: This doesn't actually help V8, so I'm removing it for now.

Original change's description:
> [page_allocator] Support predictable ASLR calculation for fuzzers.
> 
> - 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}

TBR=palmer@chromium.org,bbudge@chromium.org,haraken@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: chromium:756050
Change-Id: I0f6a3618465470e93b7981580cb547474456dda9
Reviewed-on: https://chromium-review.googlesource.com/728459
Commit-Queue: Bill Budge <bbudge@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510170}

Bug: None
Test: braille routing over rich contextual output routes selection within rich text.
For example, routing over'tbl' moves the selection to the beginning of the table (i.e. a selection on the table node).

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I02bfbcf8e48dbb502f1e031c67bc778a219e4a92
Reviewed-on: https://chromium-review.googlesource.com/726383Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510169}

Capture was failing because data URLs are sometimes too long.
This avoids the use of GURLs with this limitation and creates
object URLs for PNG images to ensure that they are displayed
correctly.

Bug: 773981
Test: manual
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I9dd19aa346874a690f1fab2965baec69c9f6f3c2
Reviewed-on: https://chromium-review.googlesource.com/724526
Commit-Queue: David Reveman <reveman@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510168}

https://skia.googlesource.com/skia.git/+log/0341f160befa..00c6432dea51

$ git log 0341f160b..00c6432de --date=short --no-merges --format='%ad %ae %s'
2017-10-19 angle-deps-roller Roll skia/third_party/externals/angle2/ 6dee4d8c1..cbcb96fcd (1 commit)
2017-10-19 egdaniel Revert "Support creation/use of mipped proxy in GrBackendTextureImageGenerator"
2017-10-18 egdaniel Support creation/use of mipped proxy in GrBackendTextureImageGenerator
2017-10-19 mtklein speculative fix for Android roll

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: I100b7bdd70b8b6224c31a19301309bfb8dfbb49f
Reviewed-on: https://chromium-review.googlesource.com/728359Reviewed-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@{#510167}

Taking two callbacks API (CallMethodWithErrorCallback()) is
not familiar with OnceCallback unfortunately.
So, instead, this CL introduces a ResponseOrErrorCallback,
which takes either Response* or ErrorResponse*, and it is
called on completion of CallMethod task regardless of whether it
is success or fail.

CallMethodWithErrorCallback() is deprecated now,
and the callers will be migarted into CallMethodWithErrorResponse()
in following CLs.

BUG=739622
TEST=Build.

Change-Id: Ib12e27de0d1dc09f2878679c53e0ad741c916fe9
Reviewed-on: https://chromium-review.googlesource.com/704794Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510166}

Bug: 649017,649000,762380
Change-Id: Ic80908a4b883fbae23ba60f67c422d95478836db
Reviewed-on: https://chromium-review.googlesource.com/721850
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510165}

This CL removes some un-used info map instances from test fixtures in
web_request_api_unittest.cc

BUG=None

Change-Id: I6bf743e06ae6297676e8c9cbd1cfb596f63225cb
Reviewed-on: https://chromium-review.googlesource.com/722119Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510164}

- Unused after https://codereview.chromium.org/2911513002
- Causing compilation error with use_asan=true on iOS.

Bug: 593874
Change-Id: I448cdcc472faaa44fa914efe56219b2448ed0b71
Reviewed-on: https://chromium-review.googlesource.com/728395Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510163}

Bug: 738065
Change-Id: I1ca301942f151bea6a1665a02bc58a89b0eb2ad7
Reviewed-on: https://chromium-review.googlesource.com/726840Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Eugene Ostroukhov <eostroukhov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510162}

Trim the query parameters to make the URL easier to visualize.

BUG=776146

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Id5b13c27a20e868b67bb121d9339e1be0ca893ad
Reviewed-on: https://chromium-review.googlesource.com/727359
Commit-Queue: David Trainor <dtrainor@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510161}

This CL is to remove unused local variable which was added by c752fed4.

- Original CL: https://codereview.chromium.org/2449583002

Bug: None
Change-Id: I569d82abe3ebfcacb20b6466ec242206533cfd93
Reviewed-on: https://chromium-review.googlesource.com/727859Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Gyuyoung Kim <gyuyoung.kim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510160}

This reverts commit 5dfbdc57.

Reason for revert: error in code.

Original change's description:
> Chrome OS: Fix BootTimesRecorder crash on renderer crash.
> 
> This CL adds NULL checks to BootTimesRecorder so that it won't crash
> on renderer crash.
> 
> Bug: 768446
> Change-Id: Ia5c6ef4d2963f6dbf71227a39486a9a5d4a0b1f6
> Reviewed-on: https://chromium-review.googlesource.com/727192
> Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> Commit-Queue: Alexander Alekseev <alemate@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#510150}

TBR=oshima@chromium.org,alemate@chromium.org

Change-Id: I445a61033b98a5660d234441f845af88e6103c2b
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 768446
Reviewed-on: https://chromium-review.googlesource.com/728624Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510159}

Bug: 658880
Change-Id: I8f03010037dbc45daa9165e9e5ae8c47ade889d0
Reviewed-on: https://chromium-review.googlesource.com/726970Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510158}

Bug: 766678
Change-Id: Id38d07cc60a5a97f2e60903449050032ea0a6cb8
Reviewed-on: https://chromium-review.googlesource.com/696124
Commit-Queue: François Doray <fdoray@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510157}

Dialog element centering used the frame view's scroll offset
but needed to use the scrollable area's scroll offset to work
with root layer scrolling.

Dialog centering is not very intuitive in that it does not
re-center when the frame is resized. For this reason, it is
not associated with the viewport constrained object set on
LocalFrameView. Because of this, it is safe to use the local
frame view's size instead of the (unavailable) scrollable
area size. A comment has been added about this discrepancy.

Bug: 776129
Change-Id: I356e75799165cd3ee6202ce0ce54a638dacdfcae
Reviewed-on: https://chromium-review.googlesource.com/726851Reviewed-by: Stefan Zager <szager@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510156}

The jpeg decoder uses libjpeg_turbo which uses a "boolean" type
defined to be int. At the same time Windows has "boolean" type
which is unsigned char. If those headers meet in a
translation unit you get compilation errors.

An alternative fix would be to redefine libjpeg_turbo to use
unsigned char for its boolean type.

Bug: 775979
Change-Id: I268e0890dfc2fae79d0abe54bbd7bf5c0c23226f
Reviewed-on: https://chromium-review.googlesource.com/727980Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#510155}

Behaviour matches android now.

Test: ash_unittests SplitViewWindowSelectorTest.SelectUnsnappableWindowInSplitView
Bug: 775682
Change-Id: I9e3a6c321ea2c871b1cc7d438f8b70228030a2a1
Reviewed-on: https://chromium-review.googlesource.com/724212Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510154}

Delete relevant code now that rAF aligned touch and mouse have
both shipped for a couple of releases.

BUG=642368

Change-Id: Ib61e7023cc311e3967427566a5beb2875d7db469
Reviewed-on: https://chromium-review.googlesource.com/726406Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Daniel Bratell <bratell@opera.com>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510153}

svg/custom/radialGradient-focal-radius.svg

(https://skia-review.googlesource.com/c/skia/+/616600

BUG=776383
TBR=

Change-Id: Iecdda691c56e318966fffb5b7cb8ee9600ee908e
Reviewed-on: https://chromium-review.googlesource.com/727628Reviewed-by: Mike Klein <mtklein@chromium.org>
Commit-Queue: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510152}

To prevent JS console errors, ensure that all CDDs obtained from
extension and privet printers are sane. Do not need to check CDDs from
local printers, since they are generated by
SemanticCapsAndDefaultsToCdd.

Bug: None
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Idbbd9470cd966a47bb4b16472f05f30fe4990c4c
Reviewed-on: https://chromium-review.googlesource.com/679283
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510151}

This CL adds NULL checks to BootTimesRecorder so that it won't crash
on renderer crash.

Bug: 768446
Change-Id: Ia5c6ef4d2963f6dbf71227a39486a9a5d4a0b1f6
Reviewed-on: https://chromium-review.googlesource.com/727192Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510150}

Add LayoutNGBlockFlow::CachedLayoutResultForTesting method to enable 
fragment access from unit tests.

# Reason for patch:

Legacy has a fast layout code path that does not call
LayoutNGBlockFlow::UpdateBlockLayout. This path updates 
overflow, and position of OOF descendants. Because of this, 
Legacy containers must know about all OOF descendants.

Existing code did not let Legacy containers know about NG OOF 
descendants. This CL fixes this.

# Unit tests problems.

This patch will affect future webkit_unit_tests. NGBlockNode::Layout 
will DCHECK if done outside of the performLayout cycle if 
NGBlockNode has OOF descendants. 

The core cause is this:
NGBlockNode::CopyFragmentToLegacyLayout calls 
LayoutBox::LayoutPositionedObjects. LayoutPositionedObjects 
asserts that View()->IsInPerformLayout()

This patch fixes four existing failing tests.

1) NGBlockLayoutAlgorithmTest.CollapsingMarginsEmptyBlockWithClearance
Fixed by inspecting LayoutObjects instead of fragments.

2) NGOutOfFlowLayoutPartTest.FixedInsideAbs
Fixed by 

3) NGOutOfFlowLayoutPartTest.OrthogonalWritingMode1
4) NGOutOfFlowLayoutPartTest.OrthogonalWritingMode2
Removed, code already covered by existing LayoutTests.

Bug: 740993
Change-Id: I3a87ef5cdac883517bc3db33e0569668161ff806
Reviewed-on: https://chromium-review.googlesource.com/722760
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510149}

Seems this is not used (anymore).

Change-Id: I3ac38799038231537d4fbc16428d1b523c7528b1
Reviewed-on: https://chromium-review.googlesource.com/728319Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Rob Buis <rob.buis@samsung.com>
Cr-Commit-Position: refs/heads/master@{#510148}

Requires https://codereview.chromium.org/3008203003/

Bug: 723636
Change-Id: I3bda0037af48c78fd7b80912f4a84d0542a782e8
Reviewed-on: https://chromium-review.googlesource.com/655361
Commit-Queue: rnephew <rnephew@chromium.org>
Reviewed-by: rnephew <rnephew@chromium.org>
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510147}

The observers in scoped_layer_animation_settings,
CacheRenderSurfaceObserver, DeferredPaintObserver, and
TrilinearFilteringObserver, share the very similar pattern.

This cl abstracts the observers and reduces the duplication
of the code.

Bug: 774332
Test: local builds works with caching and trilinear filtering.
Change-Id: Idc4119d6ec680145c05161b504a7baf45080058b
Reviewed-on: https://chromium-review.googlesource.com/724362Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510146}

This CL contains:
 - Moves WTF::GetPtr overload for RefPtr to wtf/GetPtr.h,
 - Moves RefPtrValuePeeker to wtf/HashFunctions.h
 - Merges WTF::AdoptRef and base::AdoptRef.
as a preparation of RefPtr.h removal.

Bug: 763844
Change-Id: Iac2cfe6af0304ed4ea180f6ed50a08e9065672b9
Reviewed-on: https://chromium-review.googlesource.com/727683Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510145}

Previously, we'd sorted along world-space z which provided a stable
ordering given that the elements did not move in world space in a way
that would upset the element ordering.

However, with viewport-aware elements, this has now changed. With this
change, we instead order the elements semantically. When we add effects
which require sorting by depth (i.e., where elements dynamically change
their ordering), we can augment UiRenderer::GetElementsInDrawOrder to
account for the view vector. Currently, however, this is not required.

Bug: 765460
Change-Id: If17a9b19b35ff6c1e998694f2677cb5c19170d96
Reviewed-on: https://chromium-review.googlesource.com/727342Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510144}

This test is flaking on the CQ. Disable it on desktop until we can
assess the root cause.

BUG= b/67975693

Bug: 67975693
Test: CQ
Change-Id: I76ad684140460b10b819c45f77a75bff5a7fb935
Reviewed-on: https://chromium-review.googlesource.com/727076
Commit-Queue: Stephen Lanham <slan@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510143}

This has two changes.
- Remove gmock from document_scan_interface_chromeos_unittest.
- Remove friend from the testee class. Instead, pass
  LorgnetteManagerClient via ctor.

BUG=None
TEST=Ran bots.

Change-Id: I8bb910efb045ba6124fc0a42b70cd729e80c16bf
Reviewed-on: https://chromium-review.googlesource.com/727504Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510142}

At the end of the catch up loop, we notify observers that the image is
dirty and schedule a task for the next frame. The latter is unnecessary
since when the image is repainted, it will call StartAnimation to tick
itself at the end of the draw call.

The original intent of the code was to catch up to the desired frame
and synchronously draw it (see [1]). The assumption at the time was
that since this draw will happen synchronously, there will be no
StartAnimation call to schedule the next frame and it needed to be
done immediately after the catch up loop.

This is no longer true. We notify observers async after catching up
and when they draw, we will get a StartAnimation call to tick the
animation. So this additional bit of code is unnecessary complexity.

[1]: https://bugs.webkit.org/show_bug.cgi?id=19663#c6

R=pdr@chromium.org

Change-Id: If9684b9aa92dd69b5e3b87cadea5fc7582e4e7a4
Reviewed-on: https://chromium-review.googlesource.com/727198Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510141}

Bug: 699017
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I0ad635a08ffed1fdca4e370a320e12854e2ef227
Reviewed-on: https://chromium-review.googlesource.com/727406
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510140}

scoped_refptr is allowed in Blink now, and WTF::RefPtr is an alias of
scoped_refptr for migration. This CL inlines the alias to the RefPtr
users in core/frame to remove RefPtr.

Bug: 763844
Change-Id: I4cd5877a45c20aba61018c532b09336aa24050f7
Reviewed-on: https://chromium-review.googlesource.com/727447Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510139}

Bug: 
Change-Id: I39ab598aae721bdd8f88c0dd9b1668c45d7e0559
Reviewed-on: https://chromium-review.googlesource.com/727599Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510138}

Creation of <div>'s is a repeated part of the media controls so
this refactors it into a single function (there are more uses of the
function coming).

BUG=761305

Change-Id: If3530a416fd6f169100072899fbe3fcfb159155a
Reviewed-on: https://chromium-review.googlesource.com/727897Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510137}

Bug: 776236
Change-Id: I41f84b07f6ebd28434897bb77edcc9254987ec1b
Reviewed-on: https://chromium-review.googlesource.com/727024Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Ben Chan <benchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510136}

https://chromium.googlesource.com/angle/angle.git/+log/d042fba..cbcb96f

BUG=765919

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Ie29f5ce96fd63f1c1f9c51a5646cfa5da12d17f6
Reviewed-on: https://chromium-review.googlesource.com/726756Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Frank Henigman <fjhenigman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510135}

This extends what we did for ChromeHome at
https://chromium-review.googlesource.com/520712: when moving focus from
an EditText to non-editable placeholder does not automatically hide
keyboard, but restart input with TYPE_NULL, which results in a visual
glitch such as flickering of number panel on keyboard app. This can be
prevented by hiding soft input ourselves.

BUG=708259

Change-Id: I05d3714202381e42af04b3fa4ed1bf4452908beb
Reviewed-on: https://chromium-review.googlesource.com/728389Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510134}

For low frequencies, use a 3-point or 5-point Lagrange interpolation
scheme to improve the accuracy of the oscillator instead of using
simple linear interpolation.

For a typical context, the linear interpolator is used if the
frequency >= 3.2 Hz; the 3-point, for 3.2 > frequency > 1.7 Hz; and
the 5-point for all other cases.  Thus, typical use-cases are not
impaired by this change.

Some benchmark results from running an oscillator for 1000 seconds in an
offline context.  This is the time measured from startRendering()
until the promise is delivered.  The SNR is the measured SNR between
the test signal and a reference 440 Hz signal.  The linear time was
the same before and after this CL.

linear:
time: 1844.6 ms, stddev: 154.4
SNR: 27.7 dB

3-point:
time: 2426.5 ms, stddev: 265.0
SNR: 37.2 dB

5-point:
time: 2752.6 ms, stddev: 215.1
SNR: 59.3 dB

7-point (for reference, not used now):
time: 3239.4 ms, stddev: 263.8
SNR: 82.5 dB

Bug: 773507
Test: Oscillator/osc-440hz.html
Change-Id: Ib49fab4fb27738f4f02bd41f8adcc2e3b2dd2137
Reviewed-on: https://chromium-review.googlesource.com/713576
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510133}