GitLab

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/dfb7da3..9e447c0

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=scroggo@google.com

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

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

To prevent concurrent updates and reading old state, operations have to executed in sequence if they read or modify an extension's StateStore.

This change is not affecting/modifying the crypto operations but only changes the processing order of the operations.

BUG=450167

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

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

This also makes the chrome.platformKeys.subtleCrypto().sign() working.
Still missing: per extension key permissions and UI changes.

Reland of
https://codereview.chromium.org/884073002/

BUG=450167
TBR=arv@chromium.org (for renderer_resources.grd change)

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

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

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

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

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

And make the flag --enable-physical-keyboard-autocorrect as
ENABLE_DISABLE_VALUE_TYPE.

TBR=stevet@chromium.org
BUG=422869
TEST=Verified on linux_chromeos.

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/f6f8050..dfb7da3

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=scroggo@google.com

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

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

When tapping a date, in landscape, on tablet the focus row color doesn't
change. Fix this by focusing the title link when anywhere in the entry
box is tapped (it's going to navigate to the link anyways).

R=dpapad@chromium.org
BUG=437438
TEST=date a date, in landscape, on tablet -- color changes for .5s

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/3a92a61..4526c29

TBR=

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

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

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

TBR=

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

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

It is possible that another unzip is installed on a device and ends up
being found first in $PATH.

This can be problematic when binaries such as device_forwarder need to
be re-uploaded, as other unzip implementations tend to loop forever
asking whether the existing binary should be overwritten. Instead, put
the path to our unzip implementation first so it is always used.

BUG=428729, 433101

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

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

Upstreams an iOS helper class for managing lists of observers using an
ObjC protocol.

BUG=None

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

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

R=vmiura@chromium.org
BUG=451216
TEST=local traces + trybots

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

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

This is a workaround for views layer bug (458753)

BUG=379777
TEST=maual

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

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

Was reviewed here: https://codereview.chromium.org/884073002/
Tried upload with CQ here https://codereview.chromium.org/927843002/
which didn't work.
Landing again with 'git cl land'.

BUG=450167
TBR=kaliamoorthi@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/d5c9410..f304e1a

TBR=

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

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

Revert of Adding binary files for platform_keys tests. (patchset #1 id:1 of https://codereview.chromium.org/927843002/)

Reason for revert:
Binary upload with CQ is not working. Will re-land with 'git cl land'

Original issue's description:
> Adding binary files for platform_keys tests.
>
> Was reviewed here: https://codereview.chromium.org/884073002/
> Manually landing the binary files separately as 'git cl upload' chokes on them.
>
> BUG=450167
> TBR=kaliamoorthi@chromium.org
> NOTRY=true
>
> Committed: https://crrev.com/1e61ba10e22ce271d1b7ae23754a1856d3c0f9a4
> Cr-Commit-Position: refs/heads/master@{#316389}

TBR=
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=450167

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

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

BUG=458510
TEST=browser_test: *FileManager*

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/0eaee17..d5c9410

TBR=

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

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

BUG=457908

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

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

ChildAtIndex() is method of AxNode that does the same thing of
children()[index], but reads better.

BUG=None
TEST=content_unittests
R=dmazzoni@chromium.org

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

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

This is from investigation on PreMainMessageLoopRunImpl

BUG=454789

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

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

Rename key_mobile_sites_cycler -> key_mobile_sites (all the pages do not run any
page interactions).

Rename key_mobile_sites.json -> key_mobile_sites_smooth.json
Rename key_mobile_sites_cycler.json -> key_mobile_sites.json

BUG=418375

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

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

Was reviewed here: https://codereview.chromium.org/884073002/
Manually landing the binary files separately as 'git cl upload' chokes on them.

BUG=450167
TBR=kaliamoorthi@chromium.org
NOTRY=true

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

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

This reverts commit 594333f0.
Reverting because it broke gn.

R=pneubeck@chromium.org
BUG=450167

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

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

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

This also makes the chrome.platformKeys.subtleCrypto().sign() working.

Second change after
https://codereview.chromium.org/875373002/
to implement chrome.platformKeys.

Still missing: per extension key permissions and UI changes.

BUG=450167
R=asvitkine@chromium.org, kaliamoorthi@chromium.org, kalman@chromium.org, rsleevi@chromium.org
TBR=arv@chromium.org (for .grd change)

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

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

WebRTC 8348:8372
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/41cb873..21b6665

Libjingle 8347:8369
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/75c3f0a..244a04e

TBR=kjellander@chromium.org

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

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

BUG=455284

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

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

Remove references to 'libpeer_allocator_shim' gyp variable. This variable isn't used anymore.  I'll delete the source files in an upcoming cl.

R=kjellander@chromium.org
BUG=446865

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

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

BUG=458356
TEST=manually tested by dragging each separator on the column header.

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

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

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

BUG=457436
TBR=dpolukhin@chromium.org

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

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

This adds the "threading" example which was unreferenced in the GYP build, despite existing and compiling OK.

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/43466a1..f6f8050

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=jvanverth@google.com

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

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

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

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

As content_jni_onload.h was added, android_library_loader_hook is not needed be a content API, move it to content/app/android/

BUG=447393

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

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

Short Design Doc: http://goo.gl/w6Q9k8
1) Compute ElidedText on demand
2) Separate elided text and non elided text. Create elided text and runs only when necessary.
3) Use known width in RenderText::Elide
4) Don't reshape to get GetGraphemeIterator.

This CL also adds a few trace event so that we can identify the UI jank caused by text rendering performance.

BUG=451459
R=msw@chromium.org

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

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

Focus the textfield as needed (even with an empty clipboard).

Leave the cursor trailing the newly pasted text.
(don't restore and offset the prior cursor/selection)

Update and expand tests.

BUG=456581
TEST=Linux textfield/omnibox middle-click behaves as expected.
R=pkasting@chromium.org

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

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

In 'normal' setting (i.e. non-HighDPI), the coordinate space of a
DesktopWindowTreeHostX11 and the aura::Window it hosts is the same.
So when converting an event's location from one host's coordinate
space to another host's coordinate space, it is sufficient to use
the aura::Window API to convert the location between the hosts'
aura::Window. However, in HighDPI, the coordinate space of the host
is different from that of its aura::Window, and using aura::Window
API to do the coordinate conversion results in incorrect location.
Use a simpler method to do the conversion to avoid this.

BUG=400837
R=pkotwicz@chromium.org

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

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