GitLab

This CL moves the ZoomController code for WebView out of
ChromeWebViewGuestDelegate and into GuestViewBase and WebViewGuest. This
will allow non-chrome builds to access the WebView zoom api.

BUG=none

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

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

BUG=
NOTRY=True

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

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

third_party/libc++/trunk/src/support/solaris/xlocale.c from the license checker.

BUG=329819
R=phajdan@chromium.org
NOTRY=true

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

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

This pulls in the following Native Client changes:

r14179: (kschimpf) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r14180: (ncbray) GN: fix layering of library dependencies.
r14181: (shyamsundarr) enable all nonspecial avx1 instructions.
r14183: (dschuff) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r14184: (dschuff) Use an architecture-specific newlib build for nacl-clang
r14185: (dschuff) Make libc.a a linker script for nacl-clang
r14186: (jvoung) Don't use pnacl raw toolchain in llvm nightly and libcxx tests.
r14187: (hamaji) Non-SFI Mode: Build PIE nonsfi_loader
r14188: (dschuff) Update revision for PNaCl r14173->r14185
r14189: (dschuff) PNaCl: Update Clang revision in pnacl/COMPONENT_REVISIONS
r14190: (jvoung) Remove a few locale-related "known failures" from libcxx list.
r14191: (dyen) NaCl Core SDK libs for both x86-32/x86-64 x86 newlib/glibc toolchains.
r14192: (sbc) Update glibc version in tools/REVISIONS (f78e18e->1106743)
r14193: (dyen) Fixed package_version reusing work dirs between revision packages.
r14194: (ncbray) Roll GCC toolchains.
r14195: (hidehiko) Non-SFI mode: Override NACL_BUILD_ARCH and _SUBARCH in build_nexe.py.
r14196: (dschuff) Remove cygwin support from buildbot_pnacl_toolchain.py
r14197: (jvoung) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r14198: (sbc) ncval_new: on success don't produce any output by default.
r14200: (ncbray) GN: do not assemble toolchain in output directory.
r14201: (grt) Stop closing thread handles owned by the Win32 debugging API.

BUG=none
TEST=browser_tests and nacl_integration
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_rel_precise32,linux_arm_compile,linux_nacl_sdk

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

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

Changing in the intialization order of WeakPtrFactory such that all
member variables should appear before the WeakPtrFactory to ensure
that any WeakPtrs to Controller are invalidated before its members
variable's destructors are executed, rendering them invalid.

BUG=303818

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

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

TBR=machenbach@chromium.org

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

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

I've been playing around with a build of Chrome that asserts all bitmaps
recorded into pictures are immutable.  Most are, but this one popped out
on sites that use native widgets (checkboxes, text fields, etc.).

While we're here, we can just call SkCanvas::setMatrix() instead of
concating the matrix with its inverse.  That works fine with SkPicture now.

BUG=

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

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

BUG=441258

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

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

BUG=NONE
TEST=
Note: this test step depends on xkb extension update first. It should be soon available in canary channel.
1. In chrome://settings/languages page, add "Dutch"
2. Check if you see two IMES available for this language(netherland and belgian)
3. enable the two imes and switch to them (assume netherland first)
4. verify the default virtual keyboard is a compact qwerty keyboard and can
switch to us-intl full layout
4. switch to belgian keyboard, verify it is azerty full keyboard and no compact
layout for it

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

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

The test sometimes fails on windows, because entry file is not yet
closed when the test tries to write into it.

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

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

BUG=440120

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

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

BUG=438230

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

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

This logic can also be used for keyboards, mice, touchpads, and tablets.

TEST=chrome on link_freon & rush_ryu
BUG=437539

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

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

BUG=

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

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

This patch removes all uses of ShowDesktopNotificationHostMsgParams and replaces
it with a more directed PlatformNotificationData. The PlatformNotificationData
structure has the same content as the WebNotificationData structure in the Blink
API, and included are canonical conversion functions between the two.

The reason for this change is two-folded:
  (1) The content/ layer now has the ability to initialize Web Notification
      objects, whereas this previously could only be done by Blink. This means
      that we have to carry all associated data around.

      The primary user for this are Persistent Notifications, which can outlive
      the page they were created by (and thereby the JavaScript objects).

  (2) The Web Notification specification is being updated with new features, a
      number of which will eventually have to be known to the browser process.
      This makes future plumbing significantly clearer.

Also, the *Desktop*Notification.. name is outdated.

BUG=432527

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

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

TBR=machenbach@chromium.org

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

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

This patch optimizes the way we do eviction at the tiling level.

Instead of using sort, it uses a reverse spiral iterator to iterate
tiles in reverse order of what they would have been rasterized in.

In addition to that, shared tiles are returned only by one tiling set
eviction queue. This way tiling set eviction queues can skip shared
tiles those priorities for tree priority are closer to those of unshared
tiles of the twin tiling. This lessen the number of out of reversed
priority order tiles returned by tiling set eviction queues (which
were previously handled by sorting). This will also allow eviction tile
priority queue not to check for shared tiles returned twice.

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/757d75a..8e6fc6d

TBR=lushnikov@chromium.org,vsevik@chromium.org,dglazkov@chromium.org

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

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

BUG=382924
TBR=pkasting@chromium.org

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

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

Prompt for notifications if the Notification permission was not
previously granted.

Refactor a bit the browser tests to accomodate pages with
different manifests.

BUG=432930
TBR=fgorski

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

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

The reason for this separation is to distinguish the glue layer code
(which is shared amongst all of the WebView .apks) from the apk-specific
bits (which are not shared at all).

BUG=440792

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

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

According to specs http://rawgit.com/w3c/aria/master/core-aam/core-aam.html

aria-pressed {true, mixed} should set STATE_SYSTEM_PRESSED and false should
clear STATE_SYSTEM_PRESSED

This CL depends on https://codereview.chromium.org/767183002/

BUG=171625

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

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

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

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

The CL separates the X11 implementation into an independent file so
one may implement different versions for other platforms (e.g.,
ozone). To avoid compilation error, a stub ozone implementation is
also added.

Contributed by sheckylin@chromium.org

BUG=400022
TEST=link and link_freon ChromeOS build

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

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

TBR=aa@chromium.org

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

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

Add a wrapper around libwebp to decompress WebP images and re-encode them
to uncompressed TIFF (if small enough) or JPEG/PNG (dependending on image
features).

BUG=436897

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

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

Revert of Use Surfaces on Windows, Linux, and Mac OS (second try) (patchset #1 id:1 of https://codereview.chromium.org/796693003/)

Reason for revert:
Speculative revert: virtual/slimmingpaint/fast/text/fallback-traits-fixup.html is crashing on Mac.

Example build: http://goo.gl/Ol8CHS

Flakiness dashboard: http://goo.gl/KGLmLS

Original issue's description:
> Use Surfaces on Windows, Linux, and Mac OS (second try)
>
> Surfaces should be feature-complete, so try enabling them on Windows, Linux, and Mac OS. They're still disabled on Chrome OS because they rely on single-threaded browser compositing, and on Android because they haven't been implemented there yet.
>
> BUG=334090
> TBR=piman@chromium.org
>
> Committed: https://crrev.com/8a61bd41b8a04bde04d7b538e3d9a42acd7c4ec7
> Cr-Commit-Position: refs/heads/master@{#308028}

TBR=piman@chromium.org,jbauman@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=334090

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

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

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

Revert of Isolate remaining tests under ui/ (patchset #21 id:400001 of https://codereview.chromium.org/724603004/)

Reason for revert:
Speculatively reverting due to chromium.win not triggered testers at all.

http://build.chromium.org/p/chromium.win/builders/Win%20Builder/builds/5439/
succeeded in triggering testers
http://build.chromium.org/p/chromium.win/builders/Win%20Builder/builds/5440/
didn't.

There was no build.git commit nor recipe change.

BUG=441690

Original issue's description:
> Isolate remaining tests under ui/
>
> BUG=98637
> R=maruel@chromium.org,jam@chromium.org
>
> Committed: https://crrev.com/4d293d79bd67b683942fd727c46f2b3173d7f03e
> Cr-Commit-Position: refs/heads/master@{#307954}

TBR=jam@chromium.org,phajdan.jr@chromium.org,jochen@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=98637

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

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

PFM serves potentially multiple frames by providing (auto)fill
information for each. That happens through drivers, which are
recently one per frame. The PFM only supports one driver so far.

This CL makes it handle a queue of drivers until it retrieves
the credentials from the store, and then serve each of the
associated frames through the drivers.

BUG=440438

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/a274a19..757d75a

TBR=lushnikov@chromium.org,vsevik@chromium.org,dglazkov@chromium.org

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

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

Note: https://codereview.chromium.org/754963009 removes the usage of
textTrackIndex() and has to be applied first.

BUG=440777
R=philipj@opera.com

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

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

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

Revert of Updating OTS repo from https://github.com/khaledhosny/ots.git (patchset #4 id:60001 of https://codereview.chromium.org/775893002/)

Reason for revert:
Broke bots

Original issue's description:
> The original CL is https://codereview.chromium.org/658573004
>
> Updating with to new OTS repo from https://github.com/khaledhosny/ots.git
> Hash tag imported: c24a839b1c66c4de09e58fabaacb82bf3bd692a4
>
> Some important differences between new and old version of OTS:
> 1. Support for MATH table
> 2. Implementation changes related to new WOFF 2.0
> 3. Bug fixes related to OTF tables (GDEF, GSUB etc) parsing
> 4. Accept platform 0 encoding 1 cmap subtables
> 5. Allow fonts with CMAP format-12 or format-13 table
>
> A dummy version of EnableWOFF() is added to get Blink compiled.
> After the following CL is landed in Blink, it'll be removed.
> Blink CL: https://codereview.chromium.org/774253008
>
> # TODO(jschuh): 4267, 4334 are 64-bit cleanness issue. http://crbug.com/167187
>
> # TODO(h.joshi) : Make 4800 go away. <https://github.com/khaledhosny/ots/issues/44>.
> Currently patch to github (https://github.com/himanshuispresent/ots/commit/02f724f758ddb1cb264cc0259ffd5ef1cafa164a) is
> submitted so that taking OTS repository to Chromium should not cause issue on Windows bots.
>
> TEST: Blink layout tests: fast/css/font-face*
> BUG=339857
>
> Committed: https://crrev.com/3b6cd2d4bf9e0b4a9311343a2997ef9363530b14
> Cr-Commit-Position: refs/heads/master@{#308054}

TBR=jshin@chromium.org,behdad@chromium.org,h.joshi@samsung.com
NOTREECHECKS=true
NOTRY=true
BUG=339857

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

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

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

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

In ServiceWorkerURLRequestJob::DidDispatchFetchEvent(), if response.stream_url of ServiceWorkerHostMsg_FetchEventFinished is set, ServiceWorkerURLRequestJob starts reading the body of the response from the stream instead of the blob.

But the stream may not be registered yet.
It is because ServiceWorkerHostMsg_FetchEventFinished is sent from the worker thread but StreamHostMsg_StartBuilding which triggers the stream registration is sent from the main thread of the ServiceWorker process.
So if ServiceWorkerURLRequestJob can't get the stream in DidDispatchFetchEvent(), call StreamRegistry::SetRegisterObserver() to receive the stream registration event.

When ServiceWorkerURLRequestJob successfuly gets the stream, it starts reading the stream.
The codes for reading the stream is almost same as the codes in StreamURLRequestJob.

This change depends on these changes:
  https://codereview.chromium.org/760823002
  https://codereview.chromium.org/759823003

BUG=436424

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

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

- key_silk_cases (disabled)
- sync_scroll.key_mobile_sites (enabled on Android)

Disabled/Enabled attributes are added referring Smoothness test.

BUG=438074

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

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

BUG=433728
TEST=GYP_GENERATORS=ninja tools/gyp/gyp --depth . ui/file_manager/gallery/js/compiled_resources.gyp && ninja -C out/Default | grep "image_util.js"

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/c996f78..a274a19

TBR=rtoy@chromium.org,lushnikov@chromium.org,vsevik@chromium.org

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

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

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