GitLab

We'll come up with better names later on.

BUG=none
TEST=none
R=ben@chromium.org

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

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

This does not change the current behavior, it simply opens a tab
by using chrome::Navigate().

However https://codereview.chromium.org/640103002/ will introduces
app-list search to Athena, then the direct use of chrome::Navigate()
is problematic. Athena will handle this method.

BUG=380875
R=xiyuan@chromium.org
TEST=no functional changes

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

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

BUG=421831
TBR=rtenneti@chromium.org

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

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

This CL adds a test which verifies that we read and change HTTP headers.

BUG=352293
TBR=rockot@chromium.org

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

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

R=stevenjb@chromium.org
BUG=401640

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

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

TBR=burnik@chromium.org
BUG=422164

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

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

No functionally should be changed.

BUG=422155
TEST=manually tested
TBR=fukino@chromium.org

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

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

R=brettw@chromium.org

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

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

This step is a giant search and replace for OVERRIDE to
replace them with their lowercase versions.

BUG=417463

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

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

BUG=None
R=cmasone@chromium.org, achuith@chromium.org
TEST=manually

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

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

The default implementation of SetProperty in the plugin (inside
ScriptableObject) will throw an exception. This can result in an
unexpected exception in JS when properties are set on the plugin
element. We should only call SetProperty if the plugin has that
property.

BUG=414842
TBR=dmichael@chromium.org

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

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

Started replacing the current WebsiteSettings dialog with a simple
implementation of the upcoming PageInfo dialog. Currently, the dialog
only contains the URL, a short message about the site and a 'Done'
button to close the dialog. Later, it will also contain individual
dropdowns to configure permissions for the website's content settings.

The new dialog is hidden behind the flag
--enable-new-website-settings. Without the flag, the old dialog will
be displayed.

BUG=365528

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

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

Use a proper WebMouseWheelEvent instance when validating the ToString
behavior for events of type WebInputEvent::MouseWheel.

BUG=422083

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

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

On dragging and dropping an item on a folder that is
currently showing its folder menu; the menu moves upwards
by an offset, regardless of its parent button moved or not.
This CL fixes the issue that the folder menu is moved only
when its parent button is moved. Also, the offset value
should be kBookmarkFolderButtonHeight.

BUG=311155
R=asvitkine@chromium.org

TEST=
1) Launch chrome and add a bookmark folder(folder1) to Bookmarks Bar
2) Add two folders(folder2 and folder3) within folder1.
3) Open folder1, now drag folder3 and hover it on folder2,
   wait until folder2 opens its folder menu, now drop the
   folder i.e release the mouse, and observe.
4) folder2's folder menu should not shift upwards, it
   should horizontally align with its button's frame.

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

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

So the core of the mojo spy can travel to new, exciting destinations.

BUG=none

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

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

BUG=

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

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

For SyncExponentialBackoffTest.OfflineToOnline, methods were added to
simulate and reset a network failure. The old (Python server) way of
doing this has been deleted from SyncTest.

For SyncExponentialBackoffTest.TransientErrorTest, a TRANSIENT_ERROR
is now triggered on FakeServer. The old way of doing this,
SyncTest.TriggerTransientError(), has been deleted.

BUG=406545

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/1598899..232f6b0

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

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

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

This allows us to clearly distinguish between entry
points that are part of termios and the top level
ones which are trying eliminate (by moving them to
the C libraries).

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

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

BUG=402671
TEST=udp_socket_unittest.cc (this CL hasn't run that on the bots)

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

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

We should initialize the |client_| pointer before launching the host process,
as the OnHostProcessLaunched() callback dereferences the |client_| pointer.

BUG=421500

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

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

BUG=128035

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

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

BUG=421665

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

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

Two tile-size cleanups in this patch:

- Fixes a bug where the minimum tile-height for GPU-raster
  pages is 512 until any amount of zoom is applied (all
  layers we being considered 'long-and-skinny' by the old
  logic).

- Reserves default_tile_size/max_untiled_layer_size for
  software-raster. GPU-raster now computes both of these,
  leaving only tile-grid-size which re-uses the setting.
  That will be removed in my next patch.

BUG=365877

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

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

This blacklisting allowed certain cameras to be manipulated
using the QTKit API side by side to the AVFoundation API.
This is not needed anymore since the only blacklisted cameras,
namely the Blackmagic ones, are manipulated via third_party
Decklink SDK.

Note that not all traces of blacklisting disappear: QTKit
Blackmagic must avoid certain resolutions that would
otherwise crash the browser (see http://crbug.com/396812).

BUG=408493, 408089

TEST=After running Chrome, plug in a thunderbolt Blackmagic
device, for instance an UltraStudio Mini. Wait 4 seconds or so,
then enumerate devices, e.g. using http://goo.gl/r0lnFQ. There
should be a number of Blackmagic/UltraStudio mini entries but
no "QTKit " prefixed camera (those are the removed ones).

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

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

BUG=422077

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

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

EasyUnlockKeymanager is not initialized when UpdateEasyUnlockKeys is called
from FinalizePrepareProfile

BUG=419883,422102

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

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

- Adds missing files in BUILD.gn
- path/to/grit/... would be more preferable than grit/...
- remove unnecessary consts

BUG=None
R=nkostylev@chromium.org
TBR=oshima@chromium.org
TEST=manually

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

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

Add surface sequence numbers, which are used to schedule the
destruction of surfaces. The child surface's destruction can
wait on a set of sequence numbers, and the parent surface can
later queue a frame that satisfies those numbers, causing the
former child surface to be destroyed.

Also move ownership of the SurfaceIdAllocator to the
ui::Compositor, so that the surface id namespace for a
compositor will stay the same across all output surfaces it
ever uses.

BUG=411118

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

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

development.

BUG=415309
R=rockot@chromium.org

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

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

Data reduction proxy should never be enabled for incognito tabs. So
moving it to profile_impl_io_data which is specific to non-ingocnito.

BUG=412873

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

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

This fixes the bots, even though when I log into the bots and run rdmsr
with the full path through Python, it works fine. This should be ok,
since Ubuntu includes the sbin directories in the path by default.

BUG=336556

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

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

BUG=none

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

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

This adds associative arrays to mojom to the main parser, and the C++ bindings generator. This adds a mojo::Map<> class to the C++ bindings, used by the generated bindings. Finally, it moves the clipboard.mojom interface over to associative arrays (which was the inspiration to add them to the mojom language).

BUG=413863

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

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

As InputDevice.getDevice() makes no guarantees that the returned device
will be non-null, always validate the return value before using in a
meaningful way as a Gamepad device.

BUG=421168

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

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

All these testers are now gone after the switch to swarming.

BUG=414808

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/e099dd7..1598899

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

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

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

In our egl_native support, the eglGetCurrentDisplay() returns
EGL_NO_DISPLAY which causes this test to fail.

Add this test to the test expectations so it will be skipped
for now.

BUG=chromium:421568, chromium:412865
R=kbr@chromium.org, piman@chromium.org
TEST=Build and run khronos_glcts_test binary. Ensure test is skipped.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>

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

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

- Adds missing rules of BUILD.gn
- removes unnecessary const which causes warning for some compiler
  flag set on GN.

BUG=None
R=mpearson@chromium.org, cmasone@chromium.org
TEST=manually

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

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

The method -shouldShowMenubarInImmersiveFullscreen failed to take into
consideration whether the screen containing the window had a menu bar.

BUG=NONE
TEST=On OSX 10.9 or OSX 10.10, set the screensHaveSeparateSpaces setting to NO.
On a second monitor, fullscreen a youtube video. Move the mouse to the top of
screen. The tabstrip should appear, and should not have extra space for a menu
bar. Prior to this CL, there would be extra space for a non-existent menu bar.

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

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