GitLab

Revert of Remove deprecated cursor event filter for Ozone (patchset #2 id:20001 of https://codereview.chromium.org/580553002/)

Reason for revert:
This appears to be causing ImmersiveFullscreenControllerTest.MouseEventsVerticalDisplayLayout to fail on Chromium OS Ozone bots.
http://build.chromium.org/p/chromium.chromiumos/buildstatus?builder=Linux%20ChromiumOS%20Ozone%20Tests%20%281%29&number=3404
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Ozone%20Tests%20%281%29/builds/3405

Original issue's description:
> Remove deprecated cursor event filter for Ozone
>
> Removes the old filter in favor of the new one which is enabled
> by default on non-Ozone CrOS builds.
>
> BUG=none
> TESTS=ran ash_unittests --gtest_filter=MouseCursorEventFilterTest.* on an Ozone build and manually tested on link_freon
>
> Committed: https://crrev.com/cee48a5ba8c24eb8b8ea7f789e3025ac79549a4d
> Cr-Commit-Position: refs/heads/master@{#295169}

TBR=oshima@chromium.org,dnicoara@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=none

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

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

This patch adds a field to the BufferedFileStreamReader constructor, which says
how much bytes in total are going to be requested. This information is used for
an efficient buffering strategy.

TEST=unit_tests: *BufferingFileStreamReader*
BUG=398338

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

Added at https://codereview.chromium.org/306753003 but not included into
the GN build.

R=brettw@chromium.org
BUG=335824

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

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

Notes for discussion:

1) This API provides a low level interface to Chrome's video decoders. Chrome's implementations differ by codec and platform. H264 and VPX expect very different formats, so the plugin must know details about these codecs. In particular, some parsing of the stream is required to extract the frames, and during Reset, the plugin may have to parse into the frames to find start points and make sure the decoder is in the proper state to resume. Some platforms may only provide software implementations. Software and hardware decoders have very different latency and throughput.

2) The PP_VideoPicture struct (in pp_codecs.idl) exposes low level details about the texture format of the decoded pictures so the plugin can render the textures. These are platform-specific.

  GL_TEXTURE_2D is the standard one.
  GL_TEXTURE_RECTANGLE_ARB will be used by Mac in the future (but is not yet used).
  GL_TEXTURE_EXTERNAL_OES is used on ARM ChromeOS systems.

Plugins should be prepared to handle all of them.

3) The plugin continually calls GetPicture to pump the decoder. There is a little weirdness with Flush, where we signal the end of stream by returning PP_ERROR_ABORTED to the plugin's last GetPicture call.

BUG=281689

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

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

R=dbeam@chromium.org,tbreisacher@chromium.org
BUG=393873
TEST=third_party/closure_compiler/runner/how_to_test_compiler_pass.md

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

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

This reverts commit bd1cc624.

Original CL:
Refactor ExtensionManifestTest to allow usage in src/extensions
https://codereview.chromium.org/572813002

Reason:
Broke the official Win builders due to differences in how they report their
version channel.
http://master.chrome.corp.google.com:8011/builders/win%20trunk/builds/26150

BUG=414917
TEST=unit_tests
TBR=rockot@chromium.org

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

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

BUG=402005

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

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

BUG=413853

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

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

Removes the old filter in favor of the new one which is enabled
by default on non-Ozone CrOS builds.

BUG=none
TESTS=ran ash_unittests --gtest_filter=MouseCursorEventFilterTest.* on an Ozone build and manually tested on link_freon

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

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

BUG=408637

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

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

If the SafeBrowsing service couldn't come up with a definite verdict for
some reason (e.g. couldn't reach the backend or encountered some error)
it would default to a verdict of SAFE. This in turn could cause a
download that would've been considered dangerous due its file type to be
considered safe. This change introduces an UNKNOWN verdict that the
SafeBrowsing service can use to indicate that a verdict couldn't be
determined.

Downloads then uses that signal to revert to the old behavior of
displaying a dangerous downloads warning based on the file type.

BUG=269157

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

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

If a profile is signed in, but has a default name (because this is after
enabling the new profiles UI but the Gaia profile name hasn't been downloaded)
display the email address rather than the default profile name.
It's one step better.

BUG=412809
TEST=Start Chrome with an empty user data dir and
--disable-new-avatar-menu. Create two profiles, and sign one of them in
with a profile that has a clean sync (or reset the sync data after signin).
Make sure that the last active profile is the *not* signed in one
(so close all the browser windows for the signed in profile). Restart Chrome
with --enable-new-avatar-menu. You should be in the local profile. Choose "Switch
person" from the avatar menu. The user manager should display the other profile's
email address in the pod. Once you launch that profile, the name should update to
the gaia name.

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

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

Revert of Set the javac target and source to 1.7 (patchset #2 id:20001 of https://chromiumcodereview.appspot.com/545363002/)

Reason for revert:
Not all bots have Java 7 yet :(

Original issue's description:
> Set the javac target and source to 1.7
>
> BUG=336589
> TBR=yfriedman@chromium.org
>
> Committed: https://crrev.com/165c0f17fe5760a3f346940d4fb2574d62cfe53b
> Cr-Commit-Position: refs/heads/master@{#295162}

TBR=cjhopman@chromium.org,yfriedman@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=336589

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

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

include_next must be outside the include guard!

When naclports builds a package, it copies the headers from
$NACL_SDK_ROOT/include/$toolchain directly into the toolchain include
directories (i.e. toolchain/linux_x86_newlib/x86_64-nacl/usr/include).

This means that the same header is included twice in the header seach path,
e.g.:
$NACL_SDK_ROOT/include/newlib/foo.h
$NACL_SDK_ROOT/toolchain/linux_x86_newlib/x86_64-nacl/usr/include/foo.h

If include_next is inside the include guard, then the full include chain for
that header name will not be followed (it will stop when it hits the same
include guard).

BUG=none
R=bradnelson@google.com, sbc@chromium.org, bradnelson@chromium.org

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

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

the fly.

Instead register a new Dictionary,
browser.app_window_placement, at startup and put apps'
placement/size info in sub dictionaries.

Also migrate values from the old dynamically-registered
preferences to their new statically-registered home.

BUG=167256

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

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

BUG=336589
TBR=yfriedman@chromium.org

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

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

I'm reasonably confident that all of the seccomp-bpf/*.h files are now
IWYU clean. There might still be some missing/superfluous #include lines
in some of the .cc files, but it should overall be much better than
before.

Two particular changes to note:

1. "base/basictypes.h" is deprecated in favor of <stdint.h> (for standard
*int*_t types) and/or "base/macros.h" for DISALLOW_*() macros.

2. This also moves the #include "foo.h" lines to the top of each foo.cc
file, per style guide.

BUG=408845

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

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

The code will continue to load the 200P pak file and fall back to those
resources, but the supported scale factor on @3x devices will now be 300P.

This CL adds a unittest to ensure that image conversion works properly when the
scale factor of the source image does not match the current supported scale
factor of the system.

BUG=413300
TEST=None

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

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

The previous fix for positive start times http://crrev.com/93c37f1b is
incomplete. It fixed seeking, but did not fix rendering. As such, the
media timeline will start playback from 0 and advance in real time to
any positive start time... even if the actual start is hours away.

When testing I used a test clip with a short positive start time so
did not notice the issue.  In attempting to write a layout test, I
retested with a larger start time which revealed the deficiency in my
first solution.

This change reverts the removal of Demuxer::StartTime() with the added
restriction that it must always be positive.  Pipeline uses this time
like it did before, during initialization and as a minimum bound for
seeking.

BUG=413292
TEST=four new tests! layout test forthcoming.

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

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

specified.

BUG=409724
TEST=SplitViewcontrollerTest.SplitModeActivation

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

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

BUG=none
TEST=cq
TBR=brettw

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

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

BUG=414467

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

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

Previously the local NTP thumbnails were stretched. We now make preserve
ratio preserved by setting height to "auto", but keep min-height to 100%
so if thumbnail is too short we won't see blank space.
To accommotate Material Design thumbnails, we make stored thumbnails
taller. In the thumbnail <iframe>, the extra height is hidden from view.

BUG=414878

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

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

This should increase the quantity of perf profiles collected for
chromiumos-wide-profiling by a factor of 8. Based on the current amount of
data received, this should increase the number of profiles collected to a
quantity less than it was before the collection scheduling was changed in
https://codereview.chromium.org/282093011/

TEST=Not really... This is just turning a knob. I did compile it.
BUG=chromium:413951

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

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

CreateTrailsFromString function accepts values for trails_string argument without last separator symbol

BUG=401298

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

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

Revert of mojo: Create a basic clipboard. (patchset #29 id:540001 of https://codereview.chromium.org/562483002/)

Reason for revert:
Breaking GN builders.

http://build.chromium.org/p/chromium.linux/buildstatus?builder=Android%20GN&number=10604

http://build.chromium.org/p/chromium.linux/builders/Linux%20GN/builds/12120/steps/gn/logs/stdio

Original issue's description:
> mojo: Create a basic clipboard.
>
> This creates a basic clipboard interface and uses it from
> html_viewer. This is a minimal implementation and does not actually
> interact with the system clipboard.
>
> BUG=411039
>
> Committed: https://crrev.com/757286d8a2c778fe4622890140c9b9d2afd21063
> Cr-Commit-Position: refs/heads/master@{#295143}

TBR=dcheng@chromium.org,darin@chromium.org,sky@chromium.org,erg@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=411039

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

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

Relanding  https://codereview.chromium.org/564553002/ with fixes for the unit test failures which required addition of some more plumbing in the form of dummy IO and file blocking threads. The IO thread is needed to ensure that the RenderWidgetHelper instances get freed corectly.

When we switch tabs in chrome, the tab being switched away from gets hidden/shown/hidden.

This occurs in the NativeViewHostAura::NativeViewDetaching code path where we first remove the
clipping window which is the intermediate parent of the web contents view. The clipping window
is hidden which causes the RWHVA::Hide function to get called which initiates the hiding sequence.
Then the web contents view is reparented to the main view which is still visible. Now the RWHVA::Show
function is called which initiates the show sequence. Eventually the main view is hidden, which then
initiates the hide sequence.

Addressed this with the following changes.
1. WebView::AttachWebContents and WebView::DetachWebContents
   now show and hide the webcontents native view. The
   WebContents is shown and hidden as before in
   WebContentsNativeViewAura::OnWindowVisibilityChanged.

2. Removed the WebContentsNativeViewAura::OnWindowParentChanged function.
   This function was present to show and hide the webcontents if the window was visible.
   This should not be needed with the change in #1 above.

3. Added a new file webview_unittest.cc. This contains the unittest WebViewUnitTest.TestWebViewAttachDetachWebContents
   This is run as part of unit_tests.exe.

BUG=412989
R=sky

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/1e78fc4..170f90b

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

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

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

./run_benchmark --output-format=json --output-format=html foo

BUG=

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

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

The SDK has a dependency on an inner interface on the nacl side.
We use a fake to share code.
Updating the fake to actually provide what the nacl side expects.

BUG=None
TEST=trybots
R=sbc@chromium.org,binji@chromium.org

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

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

BUG=366145

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

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

This allows for specifying more than one urls for update checks and pings.
The urls are then tried in the order they are specified.

BUG=413879

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

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

We haven't been using the Safe Browsing timing histograms. Remove the
timing code and mark the histograms obsolete.

BUG=

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

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

A new version of Issue 565583005: Clean up GestureEventDetails
constructors
https://codereview.chromium.org/565583005/

BUG=350942

TBR=tdresser@chromium.org, jdduke@chromium.org, sadrul@chromium.org

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

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

This creates a basic clipboard interface and uses it from
html_viewer. This is a minimal implementation and does not actually
interact with the system clipboard.

BUG=411039

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

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

Relanding of https://codereview.chromium.org/465543004
with a fix for official builds.

This establishes a ManifestFetchDataDelegate for use
by ExtensionDownloader and ManifestFetchData, and moves
ManifestFetchData into //extensions/browser/updater.

The delegate provides implementation details for
update manifest fetching, including brand code,
boilerplate query parameters, and ping data.

Chrome's implementation has knowledge of the
Google brand, the metrics service, and Omaha-specific
query parameters necessary for CRX item queries.

BUG=398671
TBR=isherman@chromium.org

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

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

While TapDown gestures are a typical part of the touch-gesture pipeline,
they are not required and probably even undesirable in the case of
synthetic Tap gestures (e.g., with tap disambiguation). Allow such
synthetic taps through the gesture stream validator.

BUG=414372

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

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

BUG=414766

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

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

This picks up:
Update NDK to r10c-rc4
https://gerrit.chromium.org/gerrit/71574

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

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