GitLab

R=phajdan.jr@chromium.org

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

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

This API was never officially supported, but I left in ABI compatibility for a while for the Google Earth prototype. They're now on the stable 1.2 version, so this version of the API can go away.

sky TBRed for trivial change to chrome/common/ppapi_utils
binji TBRed for native_client_sdk

BUG=414398
TBR=sky@chromium.org,binji@chromium.org
NOPRESUBMIT=true

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

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

This CL is adding a content switch that is used by WebView to not create
a ScreenOrientationDelegate which will prevent locking to work on WebView
and will correctly return that locking isn't supported to Javascript.

BUG=466080

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

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

We have run into a driver issue where after we invalidate a Frame
Buffer Object it gets into a state where it will randomly drop
draw calls and/or texture copies. I have added a workaround for this
issue by skipping frame buffer invalidations on Adreno 420s. This is
valid because invalidations set the frame buffer to be in an undefined
state so skipping them is technically okay, however we may lose
optimizations that could happen at the driver level for operations
being performed on an undefined FBO.

R=sievers@chromium.org, vmiura@chromium.org
BUG=443060

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

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

The session_manager has been mitigating some potential Owner settings
edge cases for quite some time, mostly around the user whitelist being
enabled without the owner on it! While these should all be gone, very
old devices being used for the first time could still run into
this. That said, Chrome's in a better position to handle this issue,
so let's move the functionality here.

BUG=chromium:422046
TEST=unit

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

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

- Copy Android relocation packer source from AOSP:
    bionic/tools/relocation_packer/
- Remove golden test data generation scripts (not needed here)
- Add a local ScopedFd.h, to avoid any dependency on base
- Add gyp and gn build files for chromium
- Update third_party/android_platform/README.chromium

BUG=385553
R=rmcilroy@chromium.org

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

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

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

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

BUG=

TBR=tsepez@chromium.org,pfeldman@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/da5a017..12736d7

TBR=loislo@chromium.org,pkasting@chromium.org

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

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

BUG=470835

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

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

BUG=466867

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

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

BUG=

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

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

This unifies the painting code path between Views that are and are not
backed by layers, they all go through View::Paint now.

View::Paint will only translate the canvas relative to the parent when
layer() is false, keeping the origin at the origin of the view when it
is backed by a layer().

R=sky
BUG=466426

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

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

We are using .svg file in ServiceWorkersView but the mime-type for .svg file is not correctly set.

BUG=466871

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

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

BUG=467712

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

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

This re-lands https://codereview.chromium.org/750183008 (originally
by loislo@) with the output chunk size reduced down from 10M to 100K
(close to what it used to be originally). The reason for telemetry
failures of original change on Windows was the bug in websocket-client
(https://github.com/liris/websocket-client/issues/163) that caused
it to fragment Python heap when receiving a large frame.

Original issue description:
Move serialization into a worker thread. As a result
IO thread will be able to send messages to the browser.

The original implementation did serialization on IO thread
and was not able to send the messages because ipc had
is_blocked_on_write_ = true and had no chance to check
the actual state of the channel. So the messages were
collected in output_queue. Also the messages could be quite
big and could block the IO thread for a long time.

BUG=463572
TBR=dsinclair
(as he already l-g-t-m-d the original patch)

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/3a82b4f..da5a017

TBR=loislo@chromium.org,pkasting@chromium.org

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

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

BUG=none
R=glider@chromium.org

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

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

At present, the initialization of the guest's zoom level in
GuestViewBase::StartTrackingEmbedderZoomLevel() is ineffective since the
guest web contents may not have navigated yet ... this occurs for
example when embedding extension options pages in the settings-
extensions page.

Also, the extension options guest should place its guest into isolated
zoom mode since changes to the zoom of settings-extensions page should
not affect the zoom level of the associated extension.

BUG=468397, 468404

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

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

Leaving the QuicDispatcher unchanged for now. Will unify that in
a followup.

Also removes the remaining balsa dependency in QuicInMemoryCache.

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

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

Follow up to https://codereview.chromium.org/1029423004 that cleans up
the now-unused plumbing for the Cache Storage API routed through
Service Worker and Embedded Worker classes. Service Workers and other
contexts can access the API via the embedder API.

BUG=439389
R=kinuko@chromium.org,michaeln@chromium.org

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

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

BUG=470873
TBR=yoz@chromium.org
NOTRY=true

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

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

We'll need this to do touchscreen (and other absolute) device testing
with real event dumps as input since the axis information must be valid.

Replace the shell script to capture capabilities with a python script,
because the absolute axis bounds aren't exposed in sysfs. We have
python-evdev on test images. Unfortunately it's a bit incomplete & buggy,
so fall back to sysfs for the missing & incorrect bits.

The "sw" field was accidently omitted previously and is now populated.

BUG=none
TEST=events_unittests

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

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

image_decoder has been refactored into a Leaky (accessible from multiple threads) LazyInstance (singleton), that uses one utility process running in batch mode to decode all images.

This CL fixes a performance problem with scrolling in bookmarks on Android.
Previously we were using a new image_decoder and therefore a
new utility process for each image we wanted to decode. Now we
use one shared image_decoder that has one utility process running in batch mode for decoding all images.

BUG=451201

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

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

BUG=451004

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

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

After https://codereview.chromium.org/197013007
ConfigurationPolicyHandler provided a default implementation of ApplyPolicySettings() that simply called NOTREACHED.
Also it wasn't clear anymore what of ConfigurationPolicyHandler is the public interface and what is default implementation.

Both issues are resolved with this change.

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

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

In the public sdk API, apps should be able to hold a strong WebView
reference from WebChromeClient or WebViewClient, without having to worry
about preventing WebView from gc-ed.

Simulate that behavior in testCreateAndGcManyTimes by having the
AwContentsClient hold a strong reference to AwContents.

And remove the strong ref from AwWebContentsObserver to
make the test pass.

BUG=469803

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

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d125e47c..b8c26baf

Please follow these instructions for assigning/CC'ing issues:
https://code.google.com/p/v8-wiki/wiki/TriagingIssues

TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelheim@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/211c921..3a82b4f

TBR=loislo@chromium.org

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

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

We need to do this because when doing a PGO build the /GL flag gets automatically set everywhere, and we're hitting this warning: https://msdn.microsoft.com/en-us/library/b8s7ctwz%28v=vs.90%29.aspx because of the custom memset implementation (https://code.google.com/p/chromium/codesearch#chromium/src/chrome/installer/mini_installer/mini_installer.cc&q=mini_ins&sq=package:chromium&l=862)

TBR=robertshield@chromium.org
BUG=309849

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

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

This makes it possible to use the types it contains in non-Blink
embedders such as iOS. The blink::WebCredential constructor of
CredentialInfo is now a factory function that stayed in content/.

BUG=470815
TBR=jochen

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

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

The BackgroundSyncManager is the class that handles registration of
background syncs. This first CL handles storage and retrieval of
registrations and sequential ordering of async operations. Future CLs
will add permission checks and incorporate a scheduler.

Eventually the BackgroundSyncManager will be created and owned by the
BackgroundSyncMessageFilter, which will be owned by the RenderViewHost.

BackgroundSync Design Doc: https://docs.google.com/document/d/1MAuNzV0q5FporLZVJMh7CMrwTHwcZsWX6YUwPwKMGco/

BUG=449443

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/36352bf..ce86687

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=hcm@google.com

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/a81080d..211c921

TBR=loislo@chromium.org

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

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

The PIEX library has been submitted to official chrome repository.
The CL let Files.app use the library to load RAW thumbnails.

BUG=396702
TEST=None

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

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

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

BUG=371368, 470848
TBR=eugenis@chromium.org
NOTRY=true

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

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

Revert of Enable distance field text on Android. (patchset #1 id:1 of https://codereview.chromium.org/884793003/)

Reason for revert:
Apparently causing significant perf regressions in thread_times.key_silk_cases.

Original issue's description:
> Enable distance field text on Android.
>
> Sets the Android default for Ganesh-rendered text to use signed distance fields.
> The non-Android default still disables distance fields.
>
> BUG=446722
> OWNERS=jam@chromium.org
>
> Committed: https://crrev.com/58c4e746a47894de46dbfaa978f163d2072df7e0
> Cr-Commit-Position: refs/heads/master@{#320272}

TBR=vangelis@chromium.org,vmiura@chromium.org,djsollen@chromium.org,robertphillips@chromium.org,jam@chromium.org,robertphillips@google.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=446722

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

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

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/05035d4..36352bf

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=hcm@google.com

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

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