GitLab

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/37dd331..a6ca5a0

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

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

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

The TitleCondensed string property is now used to pass strings
for accessibility.  This gets around the inability to
set the content description normally for the custom menus.

BUG=293658

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

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

Add a new FindTextData class to store the index to avoid all the size_t
to int casts.

BUG=416696

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

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

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

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

BUG=397019

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

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

R=lcwu@chromium.org,byungchul@chromium.org
BUG=429837

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

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

BUG=none
TBR=asargent

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

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

These are uninteresting because they are not keyboard keys and because
they are redundant with button presses & MT contacts in gestures. We
could possibly pass on the "tool" used (BTN_TOOL_*) for touch, but we
currently don't use it.

BUG=none
TEST=ran chrome on link_freon, no more "unknown key" errors

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

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

Now that the CDM is generating SessionKeysChange events, it is no
longer necessary to intercept Update() and Load() promises and
call ResumePlayback() when they are resolved.

BUG=370251,413413
TEST=existing EME tests pass

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

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

BUG=378741
TEST=Start Chrome with --enable-new-profile-management. You'll need to
create a supervised user so that Lock is available to signed in profiles.
Lock a profile, and in the User Manager type an incorrect password. Once
the error bubble shows up, resize the User Manager. The bubble should be
repositioned along with its parent pod.

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

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

On ChromeOS, Chrome links in the remoting host, which isn't gn-ified yet.
I'm not quite sure why app_shell doesn't work, but it might be the same
issue.

TBR=cmasone@chromium.org
BUG=424337

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

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

Use the existing views API (views::Widget::GetWidgetForNativeView()) to
get any existing views::Widget for an athena::Activity, instead of asking
its ActivityViewModel.

BUG=none
R=oshima@chromium.org

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

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

Also measure the number of frame loads for comparison, and the number of Flash instances created while we are at it.

BUG=403800

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

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

Currently both of two are measured by one metric, but there is no meaning of JavaScript measurements in application test and of Speed Index in micro benchmark. This patch separate the two types of performance tests into different page_sets, and different measurements.

BUG=372759
TEST=./tools/perf/run_benchmark --browser=android-chrome-shell service_worker.service_worker
TEST=./tools/perf/run_benchmark --browser=android-chrome-shell service_worker.service_worker_micro_benchmark

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

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

BUG=426948
R=mfoltz@chromium.org,wez@chromium.org,davidben@chromium.org

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

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

VT is disabled with Freon. VTM is not really needed anymore and thus removing this.

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

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

This works for touch events, but not for wheel events. Use the existing
touch latency machinery to enable logging of wheel events.

Update ComputeInputLatencyHistograms to report latency of
INPUT_EVENT_LATENCY_ACK_RWH_COMPONENT in the absence of a
INPUT_EVENT_LATENCY_UI_COMPONENT, as it is still valid.

BUG=224781

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

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

BUG=419586
TEST=none
R=tengs@chromium.org

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

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

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

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

BUG=

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

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

BUG=none
R=kelvinp@chromium.org

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

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

Even though it's having WebContents without a ContentViewCore
is a support scenario in //content, it's not a well tested
path, especially the webview only code. This makes sure
ContentViewCore and WebContents are destroyed together.

Instead of posting on native side to destroy WebContents,
post on Java side and have one call destroy both Java and
native side.

More specific details:
* All caller except destroy to AwContents.destroyNatives
  either have already detached webview so ok to move detach
  to destroy.
* Need to remove some asserts that objects are null when
  mIsDestroyed is true.
* Reordered some native AwContents members so they are
  naturally destroyed in the correct order.

BUG=

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

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

This is temporary - will be removed once we pin down the crash.

BUG=424024
TEST=
TBR=kbr@chromium.org
NOTRY=true

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

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

If an extension desires to act, it should pop itself out of
the overflow menu.  There should also be a visual queue for
extensions that are already visible, but what exactly that
should be is still being discussed.

BUG=417441

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

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

Failure to do so causes UI issues on some sites, and causes form submission
to fail on Yahoo.

BUG=159043

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

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

If the user entered name is accepted and saved, then the entire view is refreshed and the
new name is displayed. Automatically committing the name is too eager, since
UpdateProfileName might reject the name in some cases (if it's identical to the original
one), and we might ignore the display rules around single profiles and "You".

BUG=428683
TEST=Start Chrome with --enable-new-avatar-menu. Make sure you only have one, brand new
profile. Open chrome://settings and in the avatar bubble (which should display "You")
enter the same name that the profile has in chrome://settings (like Person 1). The name
displayed in the bubble should stay as "You"

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

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

Galaxy Core rendered incorrectly on image search.  This is an Adreno 203
device.  Also remove Galaxy Win which has the same GPU.

NOTRY=true
BUG=428401

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

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

This initial implementation does nothing. Eventually it will talk to privet
and buffet to determine setup state and show progress.

BUG=428853
TEST=app_shell_unittests

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

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

EglSwapInterval doesn't take any effect when using a Surfacless
Context and will just return EGL_BAD_SURFACE in this case. This
patch adds checks to track if the current context is surfaceless
and ignores swap interval call in that case.

Tested by building Chromium with ChromesOS and
Ozone builds options and by launching chromium with the
following run time options:
chrome --no-sandbox --ozone-platform=gbm --ozone-use-surfaceless

After this change, I don't see any more EGL error as result of setting the SwapInterval
with surfaceless context during the launch time.
i.e. libEGL debug: EGL user error 0x300d (EGL_BAD_SURFACE) in eglSwapInterval

BUG=380861

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

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

histograms.xml is also updated. This update includes the ones for PLT measurement.

BUG=405690, 406200

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

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

Without this, the browser may get created with old finder_options because FindBrowser has a caching decorator.

This should fix flakiness of telemetry/page/page_runner_unittest/PageRunnerTests/testUserAgent.

http://build.chromium.org/f/chromium/flakiness/
[test type: telemetry_unittests]

BUG=428967

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

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

BUG=

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

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

Making all implementations except for ash's use the new default base class.

I left the ash's implementation as is, since I am not sure if the display origin
is always the same as the root window origin. My suspicion is that it's not..

BUG=NONE

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

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

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

BUG=

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

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

net: batch of (manual) HSTS updates.
Cr-Commit-Position: refs/heads/master@{#302499}

This helps investigate the root cause of the BUG.

BUG=427624

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

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

BUG=429393

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

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

This patch removes another service from ExtensionSystem that can easily
be its own browser context keyed service. If the ExtensionPrefs
dependency Blacklist can be removed it could be promoted to a true
singleton.

BUG=

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

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

BUG=422621

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

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