GitLab

This CL has the following changes
- Adds a showFeedback method to HelpAndFeedback which starts Feedback
  without the "Help" portion.
- FeedbackCollector can be initialized to not take screenshots (screenshot
  makes less sense for the VR feedback usecase).
- FeedbackCollector can set a CategoryTag to route the reports to a specific bucket.

BUG=722972

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

Adding this helper method allows us to simplify the implementation of
DocumentMarkerController::SetTextMatchMarkersActive(), which was previously
depending on details of the implementation of TextMatchMarkerListImpl (whether
or not it stores its markers in sorted order).

BUG=707867

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

These had been automatically disabled on Mac 10.10, 10.11 and 10.12. But
they are failing on ALL platforms, including Mac 10.9 which wasn't
explicitly mentioned. Updated to just mention "Mac" without specific
versions.

TBR=mgiuca@chromium.org

Bug: 726571
Change-Id: Ia1c33e13181a5b75f9e20f81f203c2d473c67811
Reviewed-on: https://chromium-review.googlesource.com/516863Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#474913}

After crrev.com/2721813002 tapping an insertion handle triggered a contextmenu event
which led to bug 717337. This CL fixes this bug by keeping track that the insertion
handle tap contextmenu event came from touch.

BUG=717337

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

Replace raw pointer with a stack variable.

BUG=chromium:690521, chromium:726579
TEST=passed trybots.

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

I accidentally introduced a bug in DocumentMarkerController::ShowMarkers() in
https://codereview.chromium.org/2820633002 causing it to crash if we have a node
with a DocumentMarkerList for at least one MarkerType but not all MarkerTypes
(this is very common). I hadn't noticed it until just now because this is a
method only used to assist with debugging. This CL fixes the bug.

BUG=

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

SelectionPaintRange has members of |selection_start_|,|selection_end_,
 |selection_start_pos_| and |selection_end_pos_| which LayoutSelection
 had directly.

BUG=708453
TEST=No change in behavior

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

When I moved mus_gpu_unittests into service_unittests, I didn't copy the
ozone initialization into the new test runner.

BUG=722546

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

This CL stores surface layer ids on LayerTreeHost which is pushed onto
LayerTreeImpl on commit and activation. These ids are used make the
compositor frame metadata instead of LayerTreeImpl::surface_layers and
so this patch also deletes LayerTreeImpl::surface_layers.

This CL is required to stop pushing hidden subtrees at commit.
(See comments in crrev.com/2846653002)

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

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

Allows the overlay to be any PersistentPrefStore, thereby allowing us to
use a PersistentPrefStoreClient to connect to a remote in-memory pref
store in the Mojo pref service instead of using a local one.

Bug: 719770
Change-Id: I992c416503ab6f115cbf3d98d658bc0911c4c0c7
Reviewed-on: https://chromium-review.googlesource.com/514842Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Johan Tibell <tibell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#474906}

Enables developers to apply command-line flags on user builds of Android
by setting the Debug App setting appropriately in Developer Options.
Matches the usage in ChromeApplication.

/data/local/tmp/castshell-command-line on a public, user build of
Android (7.1.2 NHG67N on Pixel) iff ADB is enabled and DEBUG_APP is set
to "com.google.android.apps.mediashell".

Bug: internal b/62042278
Test: Verified that command-line flags were properly loaded from
Change-Id: Iabb6ed29bee8812bd8a9eb9a9815ac8f68192187
Reviewed-on: https://chromium-review.googlesource.com/516243Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Le-Chun Wu <lcwu@chromium.org>
Commit-Queue: Bryan Henry <bryanhenry@google.com>
Cr-Commit-Position: refs/heads/master@{#474905}

This patch makes TextIndentLine an enum class for better type safety.

BUG=684966

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

This patch
- Removed use of RefPtr::Release where the result is not used. Replaced
  this with setting the RefPtr to nullptr.
- Added WARN_UNUSED_RESULT to RefPtr::Release() to prevent it from
  being used in this way in future.

BUG=494719

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

This test is identical to the version available in the Web Platform
Tests project and may therefore be removed without impacting coverage.

BUG=688116
R=falken@chromium.org

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

Currently, the text-security property is a 'storage_only' field,
so it has no generated public getters/setters. This patch changes it to
a 'keyword' field so that its getters/setters can be generated as well.
We also generate the EWordBreak enum and use the generated
CSSValueID <-> EWordBreak mappings.

Diff of generated files:
https://gist.github.com/darrnshn/2811407420cd06be91eca37e52c974d6/revisions

BUG=628043

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

This patch makes TextEmphasisPosition an enum class for better type
safety.

BUG=684966
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

Certain tabs API tests expect errors for passing invalid arguments.
Update the tests to accept the errors from the native bindings system.

BUG=653596
TEST=ExtensionApiTabTest.TabAudible --native-crx-bindings=1,
     ExtensionApiTabTest.TabMove --native-crx-bindings=1

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

This fixes a regression where we can't scroll the message center when
the mouse is over ARC notifications.

BUG=726574

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

CSSParserLocalContext represents local context for each property.
Currently it only has one boolean field (use_alias_parsing), but it
will be later extended to contain other info, such as whether the
property is a longhand of a shorthand.

BUG=668012

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

Currently the jinja template generates the properties getters/setters
in the order they appear in the group. This means changing groups will
change the location of the getter/setter making the diff generated hard
to read.
See diff here for example: https://codereview.chromium.org/2889323002

This CL sorts fields and subgroups deterministically in alphabetical
order.

Diff: https://gist.github.com/7b50d7f151021057eded58e5a405e724/revisions

BUG=710938

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

With browser-side navigation enabled, navigations in new foreground tabs are
considered to have started in the background. This is a change in behavior.
This causes page load metrics to incorrectly consider these page loads to have
started in the background, which skews all of Chrome's page load metrics
(PageLoad.* in UMA).

clamy explains:
"""
the background/foreground issue seems to be due to the ordering of calls in
chrome/browser/ui/browser_navigator.cc when we create a new tab.
What happens is:
- we first create a WebContents and ask it to navigate
(https://cs.chromium.org/chromium/src/chrome/browser/ui/browser_navigator.cc?type=cs&l=557).
This result in the creation of a NavigationHandle, so we fire DidStartNavigation.
In the current architecture, we fire DidStartNavigation after receiving
 DidStartProvisionalLoad.
- then we insert the WebContents in the tab strip
(https://cs.chromium.org/chromium/src/chrome/browser/ui/browser_navigator.cc?type=cs&l=589).
This fires WebContentsImpl::WasShown.
"""

This patch implements Nasko's proposed fix to expose the WebContents
CreateParams to interested WebContentsObservers, page load metrics's
MetricsWebContentsObserver being the first consumer.

We don't have the CreateParams in all places where a WebContents is passed to
TabHelpers, so we wrap the CreateParams in a base::Optional<> and provide
CreateParams in cases where they are available.

BUG=725347

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

Remove most of CronetTestFramework.  Cronet tests haven't passing options
on the command line for a long time so remove the command-line-args
abstraction layer.  Saves 250+ lines of code.

BUG=547160

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester

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

This patch makes TextDecorationSkip an enum class for better type
safety.

BUG=684966
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

BUG=None

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

Currently, pref service connections are queued until all pref store
connections and the persistent pref store are ready. This is
unnecessarily restrictive and complicates changes necessary to support
sharing of default pref values. This CL changes the initialization of
pref connections to be more incremental.

Bug: 719770
Change-Id: Ie94f037b3ec9262ac12c048a2f31be20e0a3291c
Reviewed-on: https://chromium-review.googlesource.com/513644
Commit-Queue: Sam McNally <sammc@chromium.org>
Reviewed-by: Johan Tibell <tibell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#474891}

When a user clears a chunk of history, the recency rule (previews aren't
shown for ~5 minutes after an opt out). Should be reset if the chunk of
history is longer than 5 minutes.

BUG=722436

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

The new login screen for multiple user pods involve creating small pods
and place them on a scroll bar.
 
The ‘small pod’ is implemented as an ‘add-on’ to the existing user pod
template, instead of being a new prototype. Pods can easily transform
itself among the ‘large’, ‘small’ and ‘extra small’ states, by toggling
the visibility of corresponding parts.
 
1) Pod placement works as follows:
Upon receiving the user list from backend, create a new pod for each user
(in rebuildPods()), append them to the pow row as children, and call
initialize(). This part remains the same with the old implementation, and
at this point there is no need to determine what size the pod should be
shown.

rebuildPods() calls placePods(). placePods() first determines the ‘main
pod’ (the one displayed as the large pod), and append all other pods to a
‘small pods container’, because they should be displayed as small pods.
This is done in appendPodsToParents().

The actual placement process starts here:
it’s done by: placeSinglePod_(), placePodsOnPodRow_(),
placePodsOnContainer_() or placePodsOnScrollableContainer_().

The placePods() function decides which one to call based on the number of
users we have. There’re lots of details in the placement process but the
general logic is simple, because we do not have to determine the best
numbers of rows and columns and can just follow the spec instead.

One special handling is: when scrollable container is shown it should
occupy the full screen, and a gradient mask is applied to avoid blocking
the header bar. The z-indexes should be well selected.
 
2) User removal works as follows:
A pod should always be switched to the main pod before being removed
(except the trivial 2-user case). Therefore after removing it from its
parent (the pod row), the main pod is set to null.

We call placePods(), and the following works exactly the same with the 1)
scenario. This is because placePods() will determine the main pod and re-
append the pods to different parents if necessary.
 
3) Window resizing works as follows:
Once there is a window resizing event, call placePods() directly. The
difference with the above two scenarios is that the main pod is not null
when window resizing happens. Therefore, placePods() will skip the main
pod selection and re-appending children process, and start the actual
placement directly.
 
4) Click event:
The only click event on small pods is to trigger the switch between the
small pod and the large pod. In the click event handler, we first find
out if it’s for a small pod, and if it is, simply switch it with the main
pod by switching the parents as well as positions / other relevant styles
(handled by changeMainPod()).

Please note:
We do not call placePods() because it may result in reordering the pods.
It’s OK that the pods are not in LRU order temporarily.

BUG=718159

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

This will affect both new and old login UI: 1) The exclamation mark should
have the same padding with the texts (i.e. body.chromeos .bubble). 2) The
'margin' of the bubble seems unnecessary but it make the position off a
little bit, so it's removed.

BUG=721978

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

Moves preserve log to a setting. This should allow it to be changed in
the actions menu and will allow NetworkLog to check the state of
preserve log for followup patch to move some functionality into
NetworkLog.

R=dgozman,pfeldman
BUG=None

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

Recorders are created by the tracing::Coordinator and sent to the
agents at StartTracing. Agents should flush their trace events to
the recorder when then receive the StopTracing message.

A prototype of the final product (a little bit stale and incomplete):
https://codereview.chromium.org/2833873003/

Design doc (use @chromium.org account):
https://docs.google.com/document/d/1osLqctK_rTiioKFOG9wDLkrCQ9DLJZmm4j-S335u-vM

BUG=640235

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

This is similar to Login.PromptToCompleteLoginTime, but for existing
users.

BUG=726345
TEST=manually confirmed that the path is taken when an existing
 user signs into Chrome OS

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

The preventFollow was first introduced to prevent links in Elements panel's tree
outline and SSP from opening on click
https://codereview.chromium.org/661103002

A later migration to preventClick removed all instances of preventFollow except
the one in this CL:
https://codereview.chromium.org/2519213002

BUG=none

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

Avoid the bright jarring cursor when Night Light is on, since the
layer temperature filter is not applied to the cursor.

BUG=726473

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

ui/app_list/resources

Bug: 522168
Change-Id: Iab90e558f7df5feb0731c4fde85c57bcee7b6870
Reviewed-on: https://chromium-review.googlesource.com/516247Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#474882}

We introduce web platform tests for parsing of
- offset-position
- offset-path
- offset-distance
- offset-rotate
- offset-anchor

The unshipped properties offset-position and offset-anchor currently
fail a test because we have not yet updated position parsing for
a recent CSS Values spec change (see http://crbug.com/717833).

offset-rotate currently fails a test because we parse 0 as an angle.
This was correct (but leads to shorthand parsing ambiguities) until
https://github.com/w3c/csswg-drafts/issues/1162

offset-path fails some tests because we don't yet support url or
basic-shape || geometry-box shapes.

BUG=722757

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

Add a base::Feature entry for checker-imaging finch trial and report
the status on chrome://gpu

BUG=725351
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;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/2902773004
Cr-Commit-Position: refs/heads/master@{#474880}

There are cases where we want to delete an object held by a unique_ptr in
another thread. SequencedTaskRunner::DeleteSoon takes a raw pointer, which
means we need to call release(), like

task_runner->DeleteSoon(FROM_HERE, pointer.release());

This CL makes it possible to use std::move, like

task_runner->DeleteSoon(FROM_HERE, std::move(pointer));

Bug: None
Change-Id: I269d82547103ebe8c78c2498d269ba28ee5ca88f
Reviewed-on: https://chromium-review.googlesource.com/515264
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#474879}

It's possible stderr's buffer is full and that's causing the main thread
to hang, so just attempt to send the error message to the browser
process instead of possibly blocking as well.

BUG=609252
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;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/2902383003
Cr-Commit-Position: refs/heads/master@{#474878}

Instead of std::unique_ptr<char* []>.

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

This CL is part of the Mojo Video Capture work. For the bigger picture,
see [1] CL25_enable_win.

* Added a ScopedCOMInitializer to ServiceImpl in order to initialize COM on
  the service main thread, which is also the thread that interacts with the
  video capture devices.

BUG=584797
TEST=
  content_browsertests --gtest_filter="VideoCaptureBrowserTest.*"

[1] https://docs.google.com/a/chromium.org/document/d/1Qw7rw1AJy0QHXjha36jZNiEuxsxWslJ_X-zpOhijvI8/edit?usp=sharing

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