GitLab

All other accesses of bound_instance_ in this file check if the pointer
is null before using it. This appears to be an oversight.

Bug: 803391
Change-Id: Iaba41bf8e676696a9c7db9bcd327c6125da8c4ed
Reviewed-on: https://chromium-review.googlesource.com/877202Reviewed-by: Bill Budge <bbudge@chromium.org>
Commit-Queue: Raymes Khoury <raymes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533037}

font-variation-settings shipped to stable in M62.

The CSSVariableFonts feature flag is no longer needed.

BUG=669453

Change-Id: I3061318331dda4f12a325caea49296b64cd8a05f
Reviewed-on: https://chromium-review.googlesource.com/892759Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533036}

As first seen in bug 799092, the AudioWorklet trial uncovered problems where
[OriginTrialEnabled] interfaces were not being exposed for module scripts in
worklets.

The root cause is that WorkletGlobalScopes are defined to have a unique, opaque
origin. This defeats the trial token validation which requires both a secure
context, and that the origin for the context matches the origin in the token.

For the purposes of origin trials, we believe it is sufficient to consider the
context of the document that created the worklet. If the document is secure, and
has valid token(s), the origin trial should be enabled. Analogous to this thread:
https://github.com/whatwg/fetch/pull/527#issuecomment-335677387

This CL changes so that any tokens from the document are passed along to the
worklet, and the origin of the document is used to validate any tokens. This
applies to all types of worklets, although the problem was initially found for
AudioWorklet.

As well the AudioWorkletProcessor interface has the [OriginTrialEnabled]
attribute reinstated (was removed in a previous CL as a short-term workaround).

Bug: 799960
Change-Id: I98cca05a7710e463a10dcd8c17f302f311f531b3
Reviewed-on: https://chromium-review.googlesource.com/862257
Commit-Queue: Jason Chase <chasej@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533035}

https://webrtc.googlesource.com/src.git/+log/cf30d8b1ec22..1a2f20748581

$ git log cf30d8b1e..1a2f20748 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Id30233f73403779d43d29c02479dedb41f28c4d9
Reviewed-on: https://chromium-review.googlesource.com/894127
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#533034}

Adds the MobileOmniboxDeleteUrl metric and records it whenever the user
clears the contents of the omnibox with the delete button.

Change-Id: Idddeccb89999ceeea45873a05ba2b052f0e7d2d2
Reviewed-on: https://chromium-review.googlesource.com/892140Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Troy Hildebrandt <thildebr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533033}

Previously the Control and Alt bits were being replaced with AltGraph
on keyup/keydown events for printable characters, but keypress events
were still reporting the Control and Alt modifiers.

Bug: 25503
Change-Id: I7aa4517dd629c2b4c0113c3f33429fd1c4ad56d8
Reviewed-on: https://chromium-review.googlesource.com/874528Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533032}

After changes, webrtc expects capture_time_ms_ to be same as render_time_ms() of
EncodedImage passed for encode. Instead of deriving something from current time,
we can do the best effort of preserving it.

Bug: 801327
Change-Id: I66f80f059da0c96d6e052ed105c86e9269d0e1e5
Reviewed-on: https://chromium-review.googlesource.com/893425Reviewed-by: Christian Fremerey <chfremer@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533031}

The setting of the CC layer's PremultipliedAlpha flag was (still!)
wrong in the case where the workaround was taking effect.

Added a new test to catch this. Currently Mac-specific; ChromeOS is
the only other platform that could catch it and there aren't any such
machines on the GPU waterfalls.

Bug: 804061
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2;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
Change-Id: Ib71832e48d4880defba01f675806294066eb2e4f
Reviewed-on: https://chromium-review.googlesource.com/887967Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533030}

Bug: 805357
Change-Id: Id3a6124a2fab1cfe40598d087aec86d82c567c70
Reviewed-on: https://chromium-review.googlesource.com/887635
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533029}

This CL adds a helper method to TabModelUtils for getting all the child tabs of
a specified tab (that is, all tabs opened from that tab). This is useful for UI
prototyping.

Change-Id: I54cf3aa2aeaac87e8f06dd5cde8090ae84c0cfc1
Reviewed-on: https://chromium-review.googlesource.com/892338
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533028}

Previously, when running layout tests on Android, the test runner would
map the host's test path to the device path and then the content_shell
would map it to the corresponding HTTP url that points at the host. This
approach makes little sense. The test runner can map test location
directly to the URL which can be passed to the content_shell.

Change-Id: Ia8b50344e6473960c7083058c34bfcd23eadd663
Reviewed-on: https://chromium-review.googlesource.com/887173
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533027}

This CL adds a boolean UMA metric to proof that with unified touch
adjustment enabled, GestureTap will hit in the same node as before.
This CL makes gesture events go through both old touch adjustment code
and also the "unified touch adjustment" which do adjustment
on touchstart. It adds extra hit tests.

This CL also adds feature flag for finch support.

This this CL should be revert after finch trial.

Bug: 625198, 805650
Change-Id: Ie82fcafef4a895eceb3ad3e2fe40fe4c05c7447d
Reviewed-on: https://chromium-review.googlesource.com/852479Reviewed-by: Rick Byers <rbyers@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533026}

Change-Id: I6de19017f4f49a062f41121a90df990c400785bb
Reviewed-on: https://chromium-review.googlesource.com/889651Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533025}

Bug: None
Change-Id: Ib881ec300b0fa0d3ee5666a905fb650d2dd9a9c5
Reviewed-on: https://chromium-review.googlesource.com/887727
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533024}

Find-in-page UI would disappear if re-invoked while the close animation was progressing but not yet finished.

Make sure any close animation is finished and the drop-down bar state is consistent before showing.

Bug: 790889
Change-Id: I5a8edbfe398d048ef226ea849c4c9d285b1ec564
Reviewed-on: https://chromium-review.googlesource.com/893213Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Allen Bauer <kylixrd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533023}

This CL was uploaded by git cl split.

R=kbr@chromium.org

Bug: 177475
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I36c23dfa011f28bb190540b9bd8ee78de68dc4bd
Reviewed-on: https://chromium-review.googlesource.com/889732Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533022}

This CL was uploaded by git cl split.

R=tbarzic@chromium.org

Bug: 177475
Change-Id: Ie043227144ac242f6c4939f54e59370e1c65743e
Reviewed-on: https://chromium-review.googlesource.com/891780Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533021}

This CL was uploaded by git cl split.

R=pavely@chromium.org

Bug: 177475
Change-Id: Iec6559dc79f52f0b2e18b5197bdd75c70ab5d529
Reviewed-on: https://chromium-review.googlesource.com/891482Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533020}

Bug: 803343
Change-Id: Ida606541b5391c38bbe776ef558ae2e342b6ac2b
Reviewed-on: https://chromium-review.googlesource.com/894022
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533019}

The data is only used by ash_unittests, so the data reference should
live in that target.

Fixes a TODO in ash/BUILD.gn

Bug: none
Test: ash_unittests
Change-Id: If94c055facb3db19fc6cc51fcb58a7c3f6b2481f
Reviewed-on: https://chromium-review.googlesource.com/891602Reviewed-by: Greg Levin <glevin@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533018}

Fixes a missing break that was accidentally deleted in
https://codereview.chromium.org/2701003002/diff/140001/components/sync/syncable/model_type.cc
which caused each SUPERVISED_USER_SHARED_SETTINGS to also receive an
ARTICLES default value.

This CL was uploaded by git cl split.

R=zea@chromium.org

Bug: 177475,806921
Change-Id: Iaa5b42a8d2ac5787b787b6163adb2f3f7407e6c8
Reviewed-on: https://chromium-review.googlesource.com/891746
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nicolas Zea <zea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533017}

The original test is flaky in both virtual test and nonvirtual test.

For the non-virtual test, it was expected to fail for one reason but it's
reasonable to fail for other reasons as well. We should include those failures.

For the virtual test, the test failed since long tasks could be present in a
slow environment. We fix it by ignoring those longtasks & attributions that are
not generated by us. Also, we allow waiting for multiple entry lists until we
find the interesting one.

Bug: 775626
Change-Id: Ief2a3bc4016dc3f808cb17be0122e35f75b58f9a
Reviewed-on: https://chromium-review.googlesource.com/891571
Commit-Queue: Liquan Gu <maxlg@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533016}

Set input task queue to always be high priority when field trial is
enabled.

Add testing trial config for this experiment.

R=rkaplow@chromium.org,dtapuska@chromium.org
BUG=806271

Change-Id: If299590b2e3d023af493975c98c71853d04604c0
Reviewed-on: https://chromium-review.googlesource.com/890523Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533015}

For Range objects where min or max value can't be queried (due to
the node being detached), we currently fall through to the splitter
code which then returns a value of 50 for the range. This Cl makes it
explicit that this behavior is intended.

This CL was uploaded by git cl split.

R=dmazzoni@chromium.org

Bug: 177475
Change-Id: Ife0beab1bc377ca17998601934f4dd38c2349159
Reviewed-on: https://chromium-review.googlesource.com/890074Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533014}

TBR=mlamouri@chromium.org

Bug: 807356
Change-Id: I3b0c2389090b44128b1ccfd283973737ce856cc4
Reviewed-on: https://chromium-review.googlesource.com/894122Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533013}

Only PaintChunks need ref-counted PropertyTreeState objects, because they
are the only ones that store the objects in a persistent manner. Further
the performance overhead of RefPtr for other use-cases is too big to
justify.

Bug:798378

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Iac4d4e1bcf0e377033ab9c129f290e0745830343
Reviewed-on: https://chromium-review.googlesource.com/892561Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533012}

net::CookieStore::ChangeCause and net::CookieMonster::DeletionCause
contained extra values that were added for debugging crbug.com/548423
and are no longer used, thus they are being removed.

Bug: 736978
Change-Id: I7b16526f0029222d166e09726954e0695123c4bd
Reviewed-on: https://chromium-review.googlesource.com/877515Reviewed-by: Randy Smith <rdsmith@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Nick Harper <nharper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533011}

If you have too many open, we'd crash from exhausing all JNI references.
Shouldn't be an issue in practice but saw it from 726426
BUG=726426

Change-Id: I30ac884275154068a0232b62dae7b22e00d9e5e3
Reviewed-on: https://chromium-review.googlesource.com/893532Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533010}

Change-Id: Ifb7fa05f95509b4f573dbb1a045d64ee0d9e40d8
Reviewed-on: https://chromium-review.googlesource.com/893707Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533009}

https://skia.googlesource.com/skia.git/+log/c4e31092b13e..4e95956f117f

$ git log c4e31092b..4e95956f1 --date=short --no-merges --format='%ad %ae %s'
2018-01-30 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 6969132c1..13fd988cf (1 commit)
2018-01-30 jvanverth Revert "Reduce the amount of padding needed for SDFs."
2018-01-30 reed handle paths with degenerate verbs

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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=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
TBR=bungeman@chromium.org

Change-Id: I5f3af94fd36fb6d17fffbea3013e7744d7c636d9
Reviewed-on: https://chromium-review.googlesource.com/893883Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#533008}

Test testGoBackAndGoForward fails on Waterfall for Chrome v65.
Disabling test execution in Waterfall build.

Bug: 803678
Change-Id: I0e084797f727dbd911cb16032fbb642040a1de3a
Reviewed-on: https://chromium-review.googlesource.com/893420Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533007}

Remove WebRTC-SystemUDPSendSocketSize which is long expired and not useful anymore.

Also removing an unused include from ipc_socket_factory.cc which I missed in
https://chromium-review.googlesource.com/c/chromium/src/+/854947

Bug: 799180
Change-Id: Iaa733fff48e7334ceafb3b212866c83822f369d1
Reviewed-on: https://chromium-review.googlesource.com/857884Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533006}

An unintended side effect of:
https://chromium-review.googlesource.com/875002

is that NetworkingPrivateDelegate::HandleConnectFailed no longer
behaves as expected.

Instead we need to:
* Set check_error_state = true when calling ConnectToNetwork in the
  networkingPrivate implementation.
* Clear any error state when Shill properties are set to ensure that
  a connnection attempt after configuration does not fail when
  check_error_state is true.
* Move configuration handling on error to the UI that calls startConnect.

ALso:
* Show the details dialog when connected networks are selected in OOBE.


This should provide a more robust / consistent experience in both oobe
and the Settings UI.

Bug: 805357
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I0030fe5f6f6d054213cec812297829996a73bcfd
Reviewed-on: https://chromium-review.googlesource.com/884846
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533005}

The check is needed to avoid password prompt when a user clicks
a link instead of submitting a filled form.  The original condition
was a weak signal to detect click-on-link, and fails with
UserActivationV2 which changes the scope of a user activation.

For records, only one test relied on the original activation check
is PasswordManagerBrowserTestBase.NoPromptIfLinkClicked .

Bug: 803193, 772432
Change-Id: I33545d9550f7bd125ff8eb739c998ee1f1a48c52
Reviewed-on: https://chromium-review.googlesource.com/884368
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533004}

Update the computation of the scale factor to match what the spec [1]
has to say about a value of zero: i.e yield (near) infinity rather than
zero. Also update the case where the computed path length is zero.

[1] https://svgwg.org/svg2-draft/paths.html#PathLengthAttribute

Bug: 803127
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I6816b6bdd47cbaee90e8ad22e16d1dcf44498c7d
Reviewed-on: https://chromium-review.googlesource.com/893184Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#533003}

https://chromium-review.googlesource.com/865558 fixes this flaky tests
on win7_chromium_rel_ng, but it only waits for dispatching of the
first wheel event before sending the others.

This cl makes sure that each wheel event gets dispatched before sending
the next one.

I haven't been able to reproduce the bug on my local windows official
build but I suspect that after using async wheel targeting for wheel
events some of the wheel events in RunTest get coalesced to each other
before getting dispatched.

Bug: 800822
Change-Id: Id693ef3beff19daf08c3e11c2119b2bf90ef6737
Reviewed-on: https://chromium-review.googlesource.com/893803Reviewed-by: James MacLean <wjmaclean@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533002}

The:

 template<typename T> bool IsSVG*Element(const T*)

overload is a remnant after RawPtr<T>, but in its current form it would
only produce infinite recursion.

Also update some nearby documentation and rewrite the const Node&
overload to use the same form of condition as the other ones.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Iecbc75423010bf26383dfd7504831bf1768a722d
Reviewed-on: https://chromium-review.googlesource.com/893270Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#533001}

This reverts commit 91310914.

Reason for revert:
Multiple failures on Linux, for example:
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty/39500
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20%28dbg%29/9251

Original change's description:
> Port another set of sticky tests to JS rather than reftests
> 
> Change-Id: Idf6dd882d2d50b1ec349f245d76717553ee266b3
> Reviewed-on: https://chromium-review.googlesource.com/882002
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532966}

TBR=flackr@chromium.org,smcgruer@chromium.org

Change-Id: I7a773131066157e0d4216d7fa7c228bd8bff2021
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/893536Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533000}

BUG=805976

Change-Id: Icdaf76079b16f7664c5dde3b63f429ae5473532f
Reviewed-on: https://chromium-review.googlesource.com/893647Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532999}

When under memory pressure, the activity is destroyed and the search
result lost.
By explicitly saving the query in the instance state bundle, the search
results can be recovered even though the activity is recreated.

Bug: 807306
Change-Id: Ice12994cdeefc7ee293114207b5faa93cebda5a5
Reviewed-on: https://chromium-review.googlesource.com/893187Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532998}