GitLab

Add a new metric to track category index after it has been moved up due
to a click. This is done in order to check how stable to order is and
whether it is becoming more stable.

BUG=687505

Review-Url: https://codereview.chromium.org/2668063004
Cr-Commit-Position: refs/heads/master@{#447968}

All test in this directory are disabled, and the implementation and the
specification were removed some years ago.

This CL has no behavior changes.

BUG=685886
TBR=kochi@chromium.org

Review-Url: https://codereview.chromium.org/2676783002
Cr-Commit-Position: refs/heads/master@{#447967}

See the loading-dev@ thread for more context:
https://groups.google.com/a/chromium.org/forum/#!topic/loading-dev/_cXkjQ0-L_E

BUG=623165

Review-Url: https://codereview.chromium.org/2666993006
Cr-Commit-Position: refs/heads/master@{#447966}

This CL has no behaivor changes.

BUG=685886
TBR=kochi@chromium.org

Review-Url: https://codereview.chromium.org/2674833002
Cr-Commit-Position: refs/heads/master@{#447965}

From comments in https://codereview.chromium.org/2663003003/.

BUG=none
R=huangs@chromium.org

Review-Url: https://codereview.chromium.org/2670133002
Cr-Commit-Position: refs/heads/master@{#447964}

Changing the preferred experiment group from "30" to "70" based on recent
experiment results. This is now the most likely candidate for launch.

BUG=672476

Review-Url: https://codereview.chromium.org/2676563002
Cr-Commit-Position: refs/heads/master@{#447963}

When a frame is throttled, its compositing state cannot be queried,
so don't try to set main thread scrolling reasons.  This fixes
DCHECK failures when root layer scrolling is enabled.

BUG=490942
TEST=FrameThrottlingTest with RLS enabled
R=skobes@chromium.org

Review-Url: https://codereview.chromium.org/2662153004
Cr-Commit-Position: refs/heads/master@{#447962}

BUG=554289

Review-Url: https://codereview.chromium.org/2658013002
Cr-Commit-Position: refs/heads/master@{#447961}

This records a histogram, at most once per main-frame navigation, when "Login
not secure" is shown in a password form. This will allow us to measure the
frequency of the warning (e.g. the number of times the warning is shown per
million navigations.)

BUG=687823

Review-Url: https://codereview.chromium.org/2670733002
Cr-Commit-Position: refs/heads/master@{#447960}

This CL moves test for the following elements:
 BODY, ARTICLE, SECTION, NAV, ASIDE, H1, H2, H3, H4, H5, H6, HGROUP, HEADER,
 and FOOTER.

This CL has no behaivor changes.

BUG=685886
TBR=kochi@chromium.org

Review-Url: https://codereview.chromium.org/2669403002
Cr-Commit-Position: refs/heads/master@{#447959}

Makes the test result of xss-DENIED-window-name-navigator.html
deterministic and fixes the flakiness.

BUG=686470

Review-Url: https://codereview.chromium.org/2673583003
Cr-Commit-Position: refs/heads/master@{#447958}

With this change, I merged protocol CRIWVWebView and class
CRIWVWebViewImpl into a class CRIWVWebView. But the class still has two
headers (public/criwv_web_view.h and
internal/criwv_web_view_internal.h) to define public and internal
methods.

BUG=687827

Review-Url: https://codereview.chromium.org/2675633002
Cr-Commit-Position: refs/heads/master@{#447957}

BUG=682002

Review-Url: https://codereview.chromium.org/2667753005
Cr-Commit-Position: refs/heads/master@{#447956}

Avoid clashes with YES/NO keywords in Objective-C.

BUG=687822

Review-Url: https://codereview.chromium.org/2671643002
Cr-Commit-Position: refs/heads/master@{#447955}

Previously, BS and return key events were consumed by the message center and the custom contents couldn't receive them.

This patch adds a check if the current input mode is none or not. If the type is not none (it means the focus is on edit box), we don't handle  BS/Return key events and pass them to the custom notification content.

BUG=679664
TEST=manually (BS and Return keys work on custom notification)

Review-Url: https://codereview.chromium.org/2670213002
Cr-Commit-Position: refs/heads/master@{#447954}

BUG=682002
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2660403006
Cr-Commit-Position: refs/heads/master@{#447953}

This is part 2 of 5 in the effort to move the FeaturePolicy implementation
into the content layer, which will facilitate use of the framework for browser-
based policy decisions.

See the other CLs in this series:
[1/5] https://codereview.chromium.org/2648423002/ (Rename classes)
[2/5] (This CL)                                   (Centralize content-side code)
[3/5] https://codereview.chromium.org/2655663004/ (Maintain parallel FP in browser)
[4/5] https://codereview.chromium.org/2651883008/ (Use content/ FP in blink)
[5/5] https://codereview.chromium.org/2656533004/ (Remove unused blink code.)

BUG=685195

Review-Url: https://codereview.chromium.org/2654873004
Cr-Commit-Position: refs/heads/master@{#447952}

This migrates the WebGL task timers dispatchContextLostEventTimer and restoreTimer to TaskRunnerTimer and correctly puts them in the WebGL task source.

BUG=624694
CQ_INCLUDE_TRYBOTS=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

Review-Url: https://codereview.chromium.org/2668573002
Cr-Commit-Position: refs/heads/master@{#447951}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/53604dda661b..4dd2f587ffc3

$ git log 53604dda6..4dd2f587f --date=short --no-merges --format='%ad %ae %s'
2017-02-02 yolandyan Fix Verity calls in adb_wrapper and add test

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2672993002
Cr-Commit-Position: refs/heads/master@{#447950}

This CL also adds dom/domparsing/README.md.
This CL has no behaivor changes.

fast/dom/DOMParser-marquee-crash.html is removed. It's for Blink-in-JS MARQUEE
implementation, which we removed.

BUG=685886
TBR=kochi@chromium.org

Review-Url: https://codereview.chromium.org/2667303004
Cr-Commit-Position: refs/heads/master@{#447949}

hasWillChangeTransformHint now takes offset-path and offset-position
into account.

BUG=648113

Review-Url: https://codereview.chromium.org/2671763002
Cr-Commit-Position: refs/heads/master@{#447948}

BUG=688190

Review-Url: https://codereview.chromium.org/2674783004
Cr-Commit-Position: refs/heads/master@{#447947}

Review-Url: https://codereview.chromium.org/2675833002
Cr-Commit-Position: refs/heads/master@{#447946}

- Return empty RenderingDelay from StreamMixerAlsaInputImpl when
  underflowing.
- Fix expected value in MultizoneBackendTest after an underflow.

BUG=internal b/34841900

Review-Url: https://codereview.chromium.org/2677643002
Cr-Commit-Position: refs/heads/master@{#447945}

This CL has no behaivor changes.

BUG=685886
TBR=kochi@chromium.org

Review-Url: https://codereview.chromium.org/2667393004
Cr-Commit-Position: refs/heads/master@{#447944}

Some observers are not actually interested in targets, but rather all the models.

BUG=none

Review-Url: https://codereview.chromium.org/2674573006
Cr-Commit-Position: refs/heads/master@{#447943}

BUG=687741

Review-Url: https://codereview.chromium.org/2674533002
Cr-Commit-Position: refs/heads/master@{#447942}

RendererCompositorFrameSink holds its own thread checker similar to what
WindowCompositorFrameSink and DirectCompositorFrameSink do. This way,
cc::CompositorFrameSink::client_thread_check_ is no longer needed and we have
one less field in the API class.

BUG=673543
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2669213004
Cr-Commit-Position: refs/heads/master@{#447941}

Revert of Update component updater URLs. (patchset #2 id:20001 of https://codereview.chromium.org/2654033009/ )

Reason for revert:
Lots of perf benchmarks started failing on Android. Bisect pointed to this change.

https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/5173
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%281%29/builds/4443
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf%20%281%29/builds/4826
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%281%29/builds/4667
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%281%29/builds/4012

Original issue's description:
> Update component updater URLs.
>
> BUG=685897
>
> Review-Url: https://codereview.chromium.org/2654033009
> Cr-Commit-Position: refs/heads/master@{#447564}
> Committed: https://chromium.googlesource.com/chromium/src/+/9fefd20253ceb6af4fc3604ca29fcafc4c8454cd

TBR=sorin@chromium.org,rkaplow@chromium.org,pastarmovj@chromium.org,waffles@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=685897

Review-Url: https://codereview.chromium.org/2675903002
Cr-Commit-Position: refs/heads/master@{#447940}

This CL has no behavior changes.

BUG=685886
TBR=kochi@chromium.org

Review-Url: https://codereview.chromium.org/2670273002
Cr-Commit-Position: refs/heads/master@{#447939}

BUG=676080
TEST=None

Review-Url: https://codereview.chromium.org/2670703002
Cr-Commit-Position: refs/heads/master@{#447938}

Move the property table-layout and its enum, ETableLayout,
to be generated in ComputedStyleBase. Also moved getter / setter /
initial value methods to be generated in ComputedStyleBase.

BUG=628043

Review-Url: https://codereview.chromium.org/2669433002
Cr-Commit-Position: refs/heads/master@{#447937}

When trying to open a render node, we should look up to kDrmMaxMinor
included. The previous logic didn't consider the last render node path.

BUG=

Review-Url: https://codereview.chromium.org/2670283002
Cr-Commit-Position: refs/heads/master@{#447936}

See readme for how-to use.

BUG=none

Review-Url: https://codereview.chromium.org/2669593003
Cr-Commit-Position: refs/heads/master@{#447935}

This CL reverts changes to the rendering of console objects. The goal is to
restore clarity to the fact that text shown to the right of the arrow is a stale
snapshot while items in the tree expansion are computed live once on expand.

Expanded titles will just show the 'i' note, instead of an abbreviated title:
https://codereview.chromium.org/2139043002

Italic titles will be restored, once removed in:
https://codereview.chromium.org/2514123003

BUG=688137

Review-Url: https://codereview.chromium.org/2676773002
Cr-Commit-Position: refs/heads/master@{#447934}

This CL adds some adjustments make the three bar (hamburger) icon and
the domain (the controlledBy/business) icon look sharper.

BUG=636231
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2672963002
Cr-Commit-Position: refs/heads/master@{#447933}

BUG=679905
R=lazyboy

Review-Url: https://codereview.chromium.org/2669563004
Cr-Commit-Position: refs/heads/master@{#447932}

https://skia.googlesource.com/skia.git/+log/1db215a8efb4..3f36369a94d2

$ git log 1db215a8e..3f36369a9 --date=short --no-merges --format='%ad %ae %s'
2017-02-02 bsalomon Batch across matrix changes in drawVertices and add GM to test.
2017-02-02 bsalomon fix up shadow_utils gm dimensions

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
TBR=halcanary@google.com

Review-Url: https://codereview.chromium.org/2668423008
Cr-Commit-Position: refs/heads/master@{#447931}

BUG=546953

Review-Url: https://codereview.chromium.org/2675853002
Cr-Commit-Position: refs/heads/master@{#447930}

Remove the usage of FeatureSwitch::extension_action_redesign in the
declarativeContent API. This was used to simulate an extension not
having a page action and us returning the proper error. These tests
are still somewhat valid (though certainly not as prevalent as they
were), so simulate an extension with no action by a) loading a
component extension and b) loading an extension with a browser action.

Clean up ShowPageActionWithoutPageActionTest api test by making it
parameterized.

BUG=590321

Review-Url: https://codereview.chromium.org/2675563002
Cr-Commit-Position: refs/heads/master@{#447929}