GitLab

print_preview_ui.cc previously specified different specified a system
print dialog shortcut message of "(Ctrl+Shift+P)" for Windows and
ChromeOS, and "(Shift+Ctrl+P)" for everything else except Mac OSX. These
have been unified such that everything besides Mac OSX uses
"(Ctrl+Shift+P)".

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

The comment is irrelevant as this function does nothing to do
with Bytes. ResizeCustomizedDefaultWallpaper() used to take
UserImage::Bytes but that parameter was removed in crrev.com/385364

BUG=593251

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

Extracted the meaningful part of the test which checks
multiple scripts in the same html file.

BUG=none

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

As it was suggested in codereview.chromium.org/2517113005, this CL adds
FakePhysicalWebDataSource. In addition to this, it adds helper functions
for creating physical web pages for tests.

BUG=None

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

Currently GetAllChildWidgets only works for Widgets, but the API doesn't
require that. Passing a non-Widget allows the Widgets parented off a
Cocoa browser window to be easily obtained. This will help with testing
of browser dialogs.

BUG=654151

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

Allocating input buffers can be very slow. Doing it in GPU
child thread can cause gpu process watchdog timeout. Move
it to decoder thread.

BUG=chrome-os-partner:56452
TEST=Run VDA unittest and play video.
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/2530493003
Cr-Commit-Position: refs/heads/master@{#434910}

This feature has been split off from --enable-color-correct-rendering

enable-color-correct-rendering is a tweaking of the existing color
awareness to be more consistent and robust, and will only be noticeable
on non-sRGB monitor.

enable-true-color-rendering does all blending and interpolation
operations in a physically correct linear space, and has perceptually
noticeable differences on all monitors.

TBR=achuith,avi,pdr
BUG=667433
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

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

Singletons are allowed by default on joinable threads.

BUG=
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/2536823002
Cr-Commit-Position: refs/heads/master@{#434908}

Previously calculateBoundaries() were used for two different purposes:
- For InlineTextBox, this is to retrieve the frame rect (LayoutRect(x(),
  y(), width(), height()) which is a result of layout.
- For SVGInlineFlowBox and SVGInlineTextBox this is a task during layout
  to calculate the boundaries based on the positions of text fragments.

Remove InlineBox::calculateBoundaries() because we don't need it in
this abstraction level.

Rename InlineTextBox::calculateBoundaries() to frameRect().

Keep SVGInlineTextBox::calculateBoundaries() which is no longer virtual.

BUG=666416

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

BUG=668914

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

This fixes an issue where after touchscreen tapping the search icon, the
browser would return focus to the search icon, immediately closing the
search field. Using the native 'click' event instead of the simulated
'tap' event fixes this issue.

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

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

BUG=664212
TEST=covered by tests

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

BUG=668914,667644

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

BUG=none

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

This patch moves the flattenNodeList() and renames it flattenChildren() to
be more appropriate. It is also moves it to the nodes instead of the
DataGrid.

R=dgozman
BUG=None

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

After the renaming, we'll have the following terms:

- physicalLocation: physical location of a box or an inline in the
  containing block.  (0,0) is the top-left corner of the containing
  block.

  Renamed LayoutBox::topLeftLocation() and
  InlineBox::locationIncludingFlipping() to physicalLocation().

- location: location in "physical coordinates with flipped blocks
  direction". (0,0) is the top-left corner of the containing block
  for writing-mode in normal blocks direction (horizontal-tb and
  vertical-lr), and is the top-right corner of the containing block
  for writing-mode in flipped block direction (vertical-rl).

  Renamed InlineBox::topLeft() to location() to keep consistence
  with LayoutBox.

Removed InlineBox::top(), left(), right(), bottom().

BTW removed LayoutInline::logicalPositionToPhysicalPoint() which was
not properly named because the input is not "logical" position but
"physical position in flipped blocks direction". Also it was redundant.
Replaced the callsites with flipForWritingMode().
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
BUG=

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

If we have a way to leak UA shadow DOM to web authors or Chrome extension authors,
these unchecked casts would be dangerous.
This CL introduces toFooTypeOrDie() helpers, and apply it to UA shadow DOM.

BUG=668970

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

Record the time duration between data saver initialization and the first
request whose resolved porxy is a data saver proxy. Also, record the
time duration between IP address change event, and the next subsequent
request whose resolved proxy is a data saver proxy.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester

BUG=666134

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

Simplify PendingScript disposal path by removing method releaseElementAndClear.
Callers should use dispose() directly instead of repeating stopWatchingForLoad + releaseElementAndClear calls.

BUG=None

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

Don't let proguard remove WebViewDatabaseAdapter methods, since these are used
in Android cts tests.

BUG=31318603

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

This is now plumbed up in shill; update histograms.xml to match.

BUG=486182
TEST=trybots

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

clearPreviousVisualRects() is called when the object's previous visual
rects become invalid (e.g. when the object becomes composited). We
should call setMayNeedPaintInvalidationSubtree to ensure paint
invalidation checking of subtree which would be triggered by changed
location if we had valid previous location.

BUG=666267
TEST=paint/invalidation/compositing/become-composited-zero-offset.html

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

This test harness is slowing us down, so we are migrating away from it.

BUG=none

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

This CL modified code to use new wrapper types for web_bluetooth.mojom.
Also changed all instances of mojo::Array, mojo::String to std::vector,
std::string since mojo::Array, mojo::String have been deprecated.

BUG=597053

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

Wrap Cronet callback/listener classes in wrapper classes whose job it
is to enforce that callbacks added in later versions are not called
when the client API is of an older version.  For now all wrapper
classes simply pass through all the callbacks as we're still working
on the first version of the API, which we shall support indefinitly.

A side benefit is this facilitates only passing implementation, not
API, classes to JNI functions like nativeGetStatus.  This is
required to support cases where the Cronet API may be repackaged
into another class at the Java layer, but not at the JNI layer.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester
BUG=629299
R=kapishnikov

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

https://pdfium.googlesource.com/pdfium.git/+log/405ac0f09e16..05e016984447

$ git log 405ac0f09..05e016984 --date=short --no-merges --format='%ad %ae %s'
2016-11-28 tsepez Make FDF document creation return unique_ptrs

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

TBR=dsinclair@chromium.org

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

https://skia.googlesource.com/skia.git/+log/d5de01364378..99ab92b5958a

$ git log d5de01364..99ab92b59 --date=short --no-merges --format='%ad %ae %s'
2016-11-28 raftias Moved A2B0 profile parsing before XYZ
2016-11-28 mtklein Consistent naming.
2016-11-28 reed use raster-pipeline in readPixels
2016-11-28 ethannicholas added support for layout(offset=...) to skslc
2016-11-28 benjaminwagner Merge changes from internal cl/140385880.
2016-11-28 mtklein simplify
2016-11-28 liyuqian Revert "Add the missing shift to the dy"
2016-11-28 mtklein Convert blitter over to new style from_srgb, to_srgb.
2016-11-28 lsalzman use __BYTE_ORDER__ macro to detect endianness when available
2016-11-28 brianosman Narrow the SkImageGenerator interface
2016-11-28 bsalomon Remove old driver bug workaround for glTexStorage.
2016-11-28 borenet Roll recipe DEPS
2016-11-28 ethannicholas unified ASTLayout/Layout and ASTModifiers/Modifiers
2016-11-28 ethannicholas removed textureProj() and legacy texture functions from sksl
2016-11-28 reed simplify SkConfig8888 logic: just fall-through if memcpy case isn't supported
2016-11-28 mtklein Split srgb out of accum stages.
2016-11-28 raftias Fuzzer fix for overflow in some Lut8 profiles.
2016-11-28 mtklein Fix unpremul stage.
2016-11-28 liyuqian Add the missing shift to the dy
2016-11-28 brianosman GrTextureProducer cleanup, phase two: Producer, Adjuster, Maker
2016-11-22 mtklein Guard against buggy ucrt\math.h.
2016-11-22 ethannicholas baked in a few more precision modifiers

BUG=668784,668907,666707

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=brianosman@google.com

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

This CL enables CSS filter support by doing the following:

1. Now each effect node creates a render surface by default. This wasn't needed
before because cc can apply accumulated transparency on layers directly, as
long as the layers don't overlap. Filters always need render surface to apply.
This also fixes multiple overlapping paint chunks under same opacity group.

2. Ensure proper clip nesting in compositing tree. The concept of input clip
is introduced in effect node. The input clip node itself is not stored on the
effect node but only computed during property tree building. The input clip
represents the cull region for the compositing children of the effect. The
input clip must be a common ancestor of all child paint chunk's clip node and
child effect's output clip.

3. Because of 2., we no longer creates dummy clip node for effects.

4. Copy blink effect filter to cc effect, which is one line.

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

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

Because interstitials are not real navigations, the security panel
sidebar doesn't work properly for an interstitial, and also doesn't
provide that much more useful information than what's shown in the
Overview view. For this reason, we were already hiding the origins
sidebar when you navigate to an interstitial while the security panel is
open. This CL extends that behavior to when you open DevTools while an
interstitial is already showing.

As a drive-by, this CL also fixes a bug where requests that finished after
the interstitial was shown would still show up in the sidebar.

Also note that this CL only partially addresses the linked bug. This CL
removes the confusing/useless prompt to reload, but doesn't fix the fact
that refreshing on an interstitial does weird things (sends you back to
the previous page). The latter weirdness has been split into
https://crbug.com/669316.

BUG=637299
TEST=Navigate to https://expired.badssl.com. Open the DevTools security
panel. Observe that there is no prompt to reload in the sidebar.

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

This is needed to ensure some operations don't attempt to modify state
back on the underlying aura::Window when the window manager owns the
window.

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

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

LayoutSVGText inherits from LayoutBlockFlow. During layout, at first
SVG text fragments are laid out in physical coordinates in local SVG
coordinates of LayoutSVGText, then the underlying LayoutBlockFlow and
inline boxes are laid out in the coordinate space of the bounding box
of the text fragments.

The difference between HTML and SVG coordinates of LayoutSVGText causes
some compexities, such as inconsistent coordinate space of SVG inline
box calculateBoundaries(), complicated paint offset situations for
outline and text when building paint property tree and painting (about
text fragments painted in coordinates with paint offset baked in while
outline painted with explicit paint offset), etc. Unifying the two
coordinates can avoid the complexities.

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

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

The file-descriptors in NativePixmapHandle need to be dup'ed before then
can be sent over mojo IPC from InProcessCommandBuffer. Introduce a
convenience function CloneHandleForIPC() so that it can be used by both
GpuChannelHost and InProcessCommandBuffer.

BUG=643746
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/2531963002
Cr-Commit-Position: refs/heads/master@{#434884}

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

This fixes and re-enables NativeWidgetMacTest.WindowModalSheet with some
additional test expectations. It was reverted in r433028 when it started
failing.

Fundamentally, the problem is that calling orderOut: on an NSWindow with
an attached sheet results in utterly broken behavior in AppKit,
documented in http://crbug.com/667602.

AppKit's broken behaviour with orderOut and regular child windows is
already handled by BridgedNativeWidget by recreating the parent/child
relationships. However, it can't do this for sheets. It's not possible
to "reattach" a sheet once it becomes detached. And even giving a sheet
a parentWindow results in graphical glitches (http://crbug.com/605098).
Sheets use -[NSWindow sheetParent], not -[NSWindow parentWindow].

Note that -[NSApp hide:] works. It's just -[NSWindow orderOut:] that's
broken. But we need the triggers from -[NSApp hide:] to be consistent
with the different things that need to happen for sheets.

Add checks to BridgedNativeWidget to detect attempts to orderOut: a
window with an attached sheet. Different solutions need to be sought for
these, such as what Chrome already does for the certificate viewer sheet
when we make it tab-modal.

Update DCHECKs in WidgetOwnerNSWindowAdapter to properly support sheets.
This allows NativeWidgetMacTest.WindowModalSheet to be re-enabled.

Updates BridgedNativeWidget::OnVisibilityChanged() to properly fix
http://crbug.com/605098. This bug still manifests in Chrome, but only
after a call to [NSApp hide:]. Re-showing a window improperly attaches
the parent as a parentWindow (rather than only sheetParent), and this is
the cause of the graphical glitches.

BUG=666503, 605098, 667602

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

There was a TODO comment which said that having a parameter to
set memory state at renderers startup. Still we don't have the
parameter but we already call OnStateChange() immediately after
renderer is ready to communicate.
(See MemoryCoordinatorImpl::OnChildAdded()).
This is effectively the same so remove the TODO comment.

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

This enum result is recorded for verifying HW codec is used on ARC++,
or if there is any initialization error.

BUG=661864
TEST=test it on Elm and make sure the flag shows correct value in
chrome://histograms/Media.ArcGpuVideoDecodeAccelerator.InitializeResult

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

BUG=602688
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/2525393002
Cr-Commit-Position: refs/heads/master@{#434879}

BUG=669323
R=dgozman

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

Many WebGL tests use this function.

BUG=668223
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/2532543002
Cr-Commit-Position: refs/heads/master@{#434877}

Some code paths are unguarded for the case where we get events while shutting
down/detaching a Frame. With this patch we just early-out.

BUG=655306

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