GitLab

Some clients (in tests) doesn't call SetPrefModelAssociatorClient.
This leaves pref_model_associator_client_ in uninitialized state.
And CreateSyncable call creates PrefServiceSyncable with
invalid client_ pointer.

Change-Id: I89b310729ef817d75374d2fe66245d7538665e5b
Reviewed-on: https://chromium-review.googlesource.com/923968Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537645}

This string was added to chromium_strings.grd in r515542, but was
accidentally left out of google_chrome_strings.grd.

BUG=None
R=finnur@chromium.org

Change-Id: I9d5054121f729fb96c973b47b62e09db6147b6bd
Reviewed-on: https://chromium-review.googlesource.com/925265Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537644}

This CL chnages IsPasswordFormReappeared so it doesn't compare form actions
if they are empty.

R=cfroussios@chromium.org, kolos@chromium.org

Bug: 699539
Change-Id: Ia57c6ec7245d972e5df5f88b64c5ddac9c2c5c43
Reviewed-on: https://chromium-review.googlesource.com/916565
Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org>
Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537643}

BUG=813547
TBR=rtoy

Change-Id: Ibe7e66ee64a0ccffda81bab85a33068c1226680a
Reviewed-on: https://chromium-review.googlesource.com/924195Reviewed-by: Thiemo Nagel <tnagel@chromium.org>
Commit-Queue: Thiemo Nagel <tnagel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537642}

Previously, active sessions and recent users were reported separately,
that is confusing on the server side.
This change adds 'user_email' field to ActiveTimePeriod proto message
and populates it for affiliated users that are eligible for reporting.
Also, user email is reported only if user reporting is turned on.

Initially landed in https://crrev.com/c/904527
Reverted in https://crrev.com/c/923228

TBR=xiyuan@chromium.org

BUG=810093
TEST=Browser tests added.
TEST=ASAN_OPTIONS="detect_leaks=1" ./out/asan/browser_tests --gtest_filter=DeviceStatusCollectorTest*
TEST=ASAN_OPTIONS="detect_leaks=1" ./out/asan/browser_tests --gtest_filter=Blub*

Change-Id: I9db2c07f6aa0ba89b9f5fc6fc890207ad5e9a97b
Reviewed-on: https://chromium-review.googlesource.com/924005
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537641}

Bug: 603319
Change-Id: I4e649017a696562b30c986129c73cb777f42a0af
Reviewed-on: https://chromium-review.googlesource.com/909389
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537640}

This adds a class that holds a log of events related to a single
app's push install process. The class is not hooked up to anything
yet, so no log entries are read or written.

Bug: b/73277923
Test: unit_tests
Change-Id: I046f5c4871e1ae8867c96c3f6bd5c6cee31b8e01
Reviewed-on: https://chromium-review.googlesource.com/915924
Commit-Queue: Bartosz Fabianowski <bartfab@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537639}

https://chromium.googlesource.com/catapult.git/+log/4aa92ef01607..8273e472c811

$ git log 4aa92ef01..8273e472c --date=short --no-merges --format='%ad %ae %s'
2018-02-19 perezju [soundwave] Use oauth2client.tools.run_flow for user authentication

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-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.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

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

See discussion thread: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/8PJU6CEyGwg

No-Try: true
Bug: 812523
Change-Id: Ie021ad6803dbbaf02a4caba37c6b8a50a006b251
Reviewed-on: https://chromium-review.googlesource.com/919066
Commit-Queue: Max Morin <maxmorin@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537637}

Fixes performance regression by only sending event for non *created* tree changes.

 Bug: 808061
Original change's description:
> Add hooks for AXTreeDelegate when a relation target changes
>
>
> Problem
> Suppose a node a has an active descendant b. A page author might change |b| to aria-selected="true" immediately after setting |b| to be the active descendant.
> As a result, we have the events and actions:
> active descendant changed on |a|
> client gets event on |a| and emits output
> attribute changed on |b|
> client gets attribute changed on |b| but focus remains over |a|
>
> Solution
>
> Let the client know about changes in its related nodes.
> For example, changes to |b| would cause an event on |a|.
>
> Bug: 808061
> Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
> Change-Id: I58a3d99d3187db348320223f0bde588015ab6f55
> Reviewed-on: https://chromium-review.googlesource.com/899862
> Commit-Queue: David Tseng <dtseng@chromium.org>
> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#534885}

TBR=dmazzoni@chromium.org,dtseng@chromium.org,nektar@chromium.org,aleventhal@chromium.org

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

We use the proto enum directly in most places, and leave Android code
unchanged for now (we may want to consider exposing proto lite to
Android code in future CLs, but this particular enum doesn't seem to
justify it).

Bug: 681921
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ia3e030a6058a3f7e4e6feb1800fe618ae435ffb4
Reviewed-on: https://chromium-review.googlesource.com/921283Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Nicolas Zea <zea@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537635}

- Bookmarks JSON file size is instrumented when it's read (at startup).
This represents the whole populations of bookmarks users.

- Time to write is instrumented in ImportantFileWriter.
Metrics in ImportantFileWriter are reported with suffix
"BookmarkStorage" in our case. And accordingly, we can get accurate
metrics values for time to write bookmarks file.
This is instrumented at the write time. Bookmarks are written after
an update in the bookmarks and hence the metric will be biased by
bookmarks that are updated frequently. This is an intended
behavior though in order to assess the impact of increasing the size
of the JSON file.


Bug: 808439
Change-Id: I7570727931e52b9f7dcdd5a48fd812faf2c4b6ab
Reviewed-on: https://chromium-review.googlesource.com/901422
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537634}

Chrome sometimes hides selections*. CTRL+C should not copy
such selections because users expect that CTRL+C has no
effect when their browser doesn't display a selection.

What about cut and paste?
Cut and paste are read/write-operations so they only operate
on _focused_ selections. A focused selection is always visible:

  bool FrameSelection::IsHidden() const {
    if (SelectionHasFocus())
      return false;
    ...

=> Cut and paste already follow the principle of visibility
so we only need to fix "copy". This CL does that.

* See the explainer in crrev.com/525029 for more information.

Bug: 813416
Change-Id: Ibb5f3868e7a5fc37c7522bb753a41ae9568d98e2
Reviewed-on: https://chromium-review.googlesource.com/924027
Commit-Queue: Hugo Holgersson <hugoh@vewd.com>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537633}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/016d6b24..8afe6561

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

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=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Ie9c0932f5c444432166a8de11c832d7fb23a0f55
Reviewed-on: https://chromium-review.googlesource.com/923540Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537632}

As per mocks
https://docs.google.com/presentation/d/1nIm5OmaOnb85ZAwMZPSVqHT0vkFbsRYZhOzbmznWU_c/edit#slide=id.g284db53a0f_0_226

Bug: 789561
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I504755e6f362e130a59c806ed700866df5ef06f4
Reviewed-on: https://chromium-review.googlesource.com/924065
Commit-Queue: Christos Froussios <cfroussios@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537631}

The Sync confirmation dialog title has four versions:
1. signin disallowed
2. non-dice and non-unity
3. dice and non-unity
4. unity (which requires dice too)

Before this CL, the unity version of the dialog was shown in case (3).
This CL changes the logic to instead show the non-unity version of the
dialog, with just a different title.

Bug: 807801
Change-Id: I87b2e023d431a3c20f191a81622984d4d3cc8f59
Reviewed-on: https://chromium-review.googlesource.com/913576Reviewed-by: Scott Chen <scottchen@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537630}

Bug: chromium:811764
Change-Id: I2d41e6941135dc9bd23f840a0ed7d992b85afa95
Reviewed-on: https://chromium-review.googlesource.com/920992Reviewed-by: Hans Wennborg <hans@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Patrik Höglund <phoglund@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537629}

This policy is a potential security vulnerability and it's not really used therefore removing.
More details on the linked bug.

Only removing the policy decoding part, and keeping some of the internals as it's used for a
cros setting.

Bug: chromium:809463
Change-Id: I487b2ae5c029e59846aeb935bb6c094588e06b03
Reviewed-on: https://chromium-review.googlesource.com/909218Reviewed-by: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Ivan Šandrk <isandrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537628}

Bug: 801583
Change-Id: I5818718ae8304925390ddf6e758f510130fc214f
Reviewed-on: https://chromium-review.googlesource.com/915781
Commit-Queue: Trent Apted <tapted@chromium.org>
Reviewed-by: Patti <patricialor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537627}

There was a flurry of activity in upstream WPT on February 15th when Mozilla
exported several changes to web-animations/.

Some tests were renamed and later heavily modified, and our infrastructure
cannot recognize those renames. Since some of the changed tests had entries
in TestExpectations, I'm manually adding ones with the new names so that
things continue to work (some of those tests have been blocking WPT imports
for several days).

TBR=smcgruer, robertma, lukebjerring

No-Try: True
Change-Id: I90bef1595da67f6fe5f8ce4f399c98284537e3f7
Reviewed-on: https://chromium-review.googlesource.com/924192Reviewed-by: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#537626}

wincrypt.h and OpenSSL can't be in the same translation unit
since both define X509_NAME. There is a crypto/wincrypt_shim.h
to use instead of wincrypt.h but in this case the includes were
left by mistake when code moved elsewhere and can be removed.

This fixes jumbo build in Windows.

TBR=pmonette@chromium.org

Bug: 746957
Change-Id: I3fa0dadaf8e423302c353bfb7bc7e5484b58ff68
Reviewed-on: https://chromium-review.googlesource.com/924223Reviewed-by: Daniel Bratell <bratell@opera.com>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#537625}

It must not be possible to create elements with invalid namespace and
prefixes, and the DOM specification doesn't ask to check it.

This CL must have no behavior changes.

Bug: 812089
Change-Id: I598081857d10116a195ecb572c9c65588d6a7734
Reviewed-on: https://chromium-review.googlesource.com/923618Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537624}

This typically means a path based on the directory containing the
BUILD.gn file that defined the jumbo target, which generally makes
sense.

The old solution of finding a suitable directory by looking at the
directories containing the target's source files can generate the
same name for multiple targets, meaning such targets can't all be
jumbo enabled. This is rare, but is the case for the targets

  //extensions:test_support

and

  //extensions/browser:test_support

since the former has source files from //extensions/browser/ that
end up being used as the target directory.

Change-Id: Ie0c9ee2fcef25c6b0705e0fed3f1dce060459537
Reviewed-on: https://chromium-review.googlesource.com/924023Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Jens Widell <jl@opera.com>
Cr-Commit-Position: refs/heads/master@{#537623}

When there's only one web account to turn on sync,
the "Sync to another account" button should directly open
the sign-in flow for a new account instead of opening
a submenu with only the "Use another account" button.

Bug: 812269
Change-Id: I99757042f9a03b78c8145cb13faea893b64db32a
Reviewed-on: https://chromium-review.googlesource.com/924185
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537622}

The DiceSigninButton should show an arrow pointing
downwards instead of to the right. This CL fixes
this.

Screenshot from before:
https://drive.google.com/file/d/13T9Wv99rezwCDQ9EnW3drrSmrGIoAtor/view?usp=sharing
Screenshot from after:
https://drive.google.com/file/d/1d9_N_IOvjLhohMrm4eEWE8-4ElaC7qBv/view?usp=sharing

Bug: 812283
Change-Id: Ic0c2229c24532f45fbdb236fe222505cd36cd572
Reviewed-on: https://chromium-review.googlesource.com/924070Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537621}

ConvertToContentUrl is a new async function being added by crrev.com/c/906222
It can handle ARC media URLs that the existing function can't handle.

Bug: chromium:767982
Bug: chromium:811679
Test: out/Default/exo_unittests --gtest_filter="DataOffer.*"
Change-Id: Ibfacfe3ce86687b45b2f60ed18d6dfefbbe6f685
Reviewed-on: https://chromium-review.googlesource.com/910540Reviewed-by: Shuhei Takahashi <nya@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Satoshi Niwa <niwa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537620}

This patch captures 3 SkFontMgr in minidump so that we can figure
out how SkFontMgr was initialized better from minidump.

Bug: 561873
Change-Id: Icafac73fc0ccc8df4ffffcd01697e2227055eb02
Reviewed-on: https://chromium-review.googlesource.com/923925
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537619}

Following patchsets crrev.com/c/924061 and crrev.com/c/924062, SHA1 for
traffic annotation auditor executable for Windows is updated.

Bug: 690323
Change-Id: Ic6112c60ea6d98c16bffcd596b669d69df8d1d3b
Reviewed-on: https://chromium-review.googlesource.com/924004Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537618}

When the drop down arrow on the DiceSigninButton is
clicked, a submenu listing all GAIA web accounts
except the first one should be displayed. This CL
adds this feature.

Screenshot:
https://drive.google.com/file/d/1va4fXSFtf7PastkuXgVUc5B5mrFIEZzJ/view?usp=sharing

Bug: 812282
Change-Id: I52a73392dc6543fc44d2553c76f046685fb17672
Reviewed-on: https://chromium-review.googlesource.com/922204
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537617}

https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/4a03f17449ae..713d68ee9f47

$ git log 4a03f1744..713d68ee9 --date=short --no-merges --format='%ad %ae %s'
2018-02-17 wl [sfnt] Prefer `CBDT'/`CBLC' over `glyf' table (#53154).
2018-02-17 wl Split off ChangeLog.28.
2018-02-17 wl s/sub-pixel/subpixel/.

Created with:
  roll-dep src/third_party/freetype/src

Bug: pdfium:1016
Change-Id: I7fd6f0278075546e9be8a58ff5aa7cc51705f93c
Tbr: bungeman@chromium.org, eae@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/924152Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537616}

CORS::GetErrorString takes multiple arguments, and required parameters
depend on error kinds. This will make developers who want to call it
be confused, when we add more parameters, we need to modify all call
sites.

This patch introduces CORS::ErrorParameter to unify parameters for
GetErrorString. This solves problems mentioned above, and also allows
us to have better coding error checks.

Once the OOR migration is done, we will be able to remove error specific
ErrorParameter builders, or can even remove ErrorParameter again because
we can remove the most intermediate call sites from Blink.

Bug: 803766
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I2647ddfea4c48aa48a744b8b636d032aec3531e1
Reviewed-on: https://chromium-review.googlesource.com/918323
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537615}

Address the review comment of
https://chromium-review.googlesource.com/c/chromium/src/+/920329/7#message-b9399a526b29ba08927301f8baec6c8d30c20682

TBR=futhark@chromium.org

Bug: 776656
Change-Id: I3e6084b7dde05df54fddf38bfeb3220c9c585bb2
Reviewed-on: https://chromium-review.googlesource.com/923667
Commit-Queue: Hayato Ito <hayato@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537614}

This is part of efforts to replace default timer task runners with
other appropriate task runners in the renderer.

Bug: 624694, 804694
Change-Id: I72ba24174da8d1557d4963b0f4336b50b2f01667
Reviewed-on: https://chromium-review.googlesource.com/925124Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537613}

Show the reset screen immediately if powerwash has previously been
requested before reboot. This addresses a case where the screen
wouldn't show because the pending TPM availability test
incorrectly turns the eligibility check negative immediately after
reboot.

BUG=chromium:780817
TEST=Reboot-to-powerwash-with-TPM-firmware-update flow works for enrolled devices

Change-Id: Ia9c56a2422c70d19dc2cccea6b5fb21c62fa510a
Reviewed-on: https://chromium-review.googlesource.com/921842Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Mattias Nissler <mnissler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537612}

Bug: 807127
Change-Id: I29dc398b9b2809abc0d2eba7345d00aa03acfc9a
Reviewed-on: https://chromium-review.googlesource.com/920566
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537611}

'remoting/client' and 'remoting/host' are added to the set of targets
that network traffic annotation tests are activated for them.

Bug: 690323
Change-Id: I415cf930df8d788437ac48ba5bfb2bcef925a4ab
Reviewed-on: https://chromium-review.googlesource.com/888618
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537610}

Internal elementFromPoint call might allow HitTest to get child frame
content, in which case retarget is not needed. In this case, we don't
call retarget for the hit test result.

Bug: 812138
Change-Id: I17047f5e4b407cbe2ce58ffd0e191f73413ac3bc
Reviewed-on: https://chromium-review.googlesource.com/923247
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537609}

This CL adds the fullscreen capability for the bottom toolbar.
The other bottom toolbar are still not connected to the bottom toolbar.

Bug: 804728
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I966b5dca9b92e1e31b9746d2eb3ee146e809a419
Reviewed-on: https://chromium-review.googlesource.com/919166
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537608}

Bug: 813481
Change-Id: I63ca84f2e191082b2685aafdaaa5fed5072221e6
TBR: halliwell@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/923745
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537607}

This patch is to split sandboxed-iframe-fetch-event.https.html into small
chunks. Each promise_test has smaller number of assertions, so that now we can
see the results for each situation.

Bug: 771815
Change-Id: I75cdd67f92bbb07d6b538b209e1f0819752c3bc8
Reviewed-on: https://chromium-review.googlesource.com/923901
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537606}