GitLab

BUG=673583
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

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

Add histograms for the duration between the obtaining of location and the use of
location for omnibox queries. One set of histograms records the time since the
location was first obtained. There is a histogram for each combination of
Location Source and whether a location was sent. A second set of histograms
records the time since the location was most recently obtained. There is a
histogram for each of the Location Sources.

BUG=668923

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

BUG=676974

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

PointerWatcherEventRouter2 is now PointerWatcherEventRouter and
aura_mus has been renamed to just mus.

BUG=671363
TEST=none
R=erg@chromium.org

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

BUG=579229

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

Root cause was due to a shutdown race condition. Rather than resolve
that, it was easier to simply remove some mostly-dead code paths that
are no longer needed (https://codereview.chromium.org/2605973002/).

Original review: https://codereview.chromium.org/2603533002/

BUG=643964
CQ-DEPEND=CL:2605973002

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

Instead of keeping a queue of IPC messages in GpuChildThread for the
deferred log messages that are sent to the browser, maintain a queue of
structs describing the log messages. This makes it easier to follow the
code, and easier to replace the chrome IPC with mojo IPC in subsequent
patches.

BUG=643746

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

BUG=655971

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

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

Does Not Block (default):
  Tasks without the MayBlock() and WithBaseSyncPrimitives() traits
  may not block.

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

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

None of the fragment shader sub-classes actually need to exist.

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

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

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

This patch rejects setting invalid values for registered properties via
the CSSStyleDeclaration::setProperty function. The behaviour which we
decided on is that we will retain any values set prior to registration
and compute them as if they were the unset keyword if they are invalid
after registration, but disallow setting such values after registration.

CSS Typed OM is not yet hooked up aside from the filtered computed map
for custom paint, so we don't yet make any changes there.

BUG=641877

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

BUG=

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

- CSSSelectorWatch is used to implement a Blink public API that supports
  the chrome.declarativeContent [1] extension API. This is an internal
  implementation detail of Chrome, and has been moved to the unspecced
  timer task source.
- The presentation attribute [2] cache cleaner remains as-is, since it's
  a static cleaner shared among different frames.

[1] https://developer.chrome.com/extensions/declarativeContent
[2] e.g. bgcolor, topmargin, etc attributes on a body element

BUG=624694

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

BUG=612542
TEST=gl_tests
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/2602563002
Cr-Commit-Position: refs/heads/master@{#441310}

This adds some basic java tests for the new disclosure UI.

BUG=675858

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

BUG=660907
TEST=ScrollingCoordinatorTest.StyleRelatedMainThreadScrollingReasonTest
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

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

Revert of Fix TabCaptureApiTest.FullscreenEvents flakiness (patchset #2 id:20001 of https://codereview.chromium.org/2604133002/ )

Reason for revert:
TabCaptureApiTest.FullscreenEvents is now timing out consistently on the Win7 Tests (dbg)(1) bot (build #56178 and later) so I don't think we're ready to re-enable it yet: https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29

Original issue's description:
> Fix TabCaptureApiTest.FullscreenEvents flakiness
>
> Fixes flakiness caused by a subtle distinction in document fullscreen
> state change: The tabCapture.onStatusChanged API can sometimes report a
> fullscreen state change before the document itself is aware the change
> occurred. This is because the tabCapture API's listener reports on the
> browser's fullscreen state, whereas the document is only aware of its
> own internal fullscreen state (which is updated only after the browser
> notifies it of a change).
>
> The flakiness was due to the C++ side of the test being notified that
> the page had entered fullscreen before the page itself was aware of it.
> This caused the simulated mouse click (to toggle fullscreen mode) to be
> made early, and then both the C++ and JS sides of the test became
> out-of-sync and froze, each waiting on the other to do something.
>
> This change fixes the issue by always using the document's fullscreen
> change listeners, to ensure the out-of-sync condition cannot occur.
> This change also "freshens up" the JavaScript code in this test, using
> newer ES6 syntax.
>
> BUG=675851
>
> Committed: https://crrev.com/c52ce18fd8f6db97c62737f0924bd61a2727c5d3
> Cr-Commit-Position: refs/heads/master@{#441252}

TBR=xjz@chromium.org,miu@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=675851

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

Some animation events are dispatched on the DOM manipulation task
source. However, the spec [1] doesn't seem to say much about timelines
and their animations, so dispatch them on the unspeced timer source.

[1] https://w3c.github.io/web-animations/#document-timelines

BUG=624694

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

Create BaseSafeBrowsingService in the components layer and derive
SafeBrowsingService from that.

BUG=488675

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

Add setter and getter methods for accessing m_didSetLooping so that we
can access it atomically. The audio thread was reading this while the
main thread could be writing it.

Manually verified the test case from the bug that this fix works. (Need to reload the page a few times to trigger the original bug.)

BUG=676874
TEST=

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

https://skia.googlesource.com/skia.git/+log/7551898f8eba..9ea894b4d030

$ git log 7551898f8..9ea894b4d --date=short --no-merges --format='%ad %ae %s'
2017-01-03 mtklein Revert "trim another instruction off SkRasterPipeline overhead"
2017-01-03 bungeman Specify "/utf-8" with Visual C++.
2017-01-03 senorblanco Quality and performance fixes for AA tessellating path renderer.
2017-01-03 senorblanco Revert "Quality and performance fixes for AA tessellating path renderer."
2017-01-03 senorblanco Quality and performance fixes for AA tessellating path renderer.
2017-01-03 ethannicholas fixed a divide-by-zero bug in skslc
2017-01-03 ethannicholas switched GrVkPipelineStateCache over to use SkLRUCache
2017-01-03 herb Fix: when pos is not finite, text pointer not advanced.
2017-01-03 reed validate deserialized path verbs
2016-12-22 scroggo GIF: Better check for frame dependency
2017-01-03 ethannicholas Force classic locale when parsing floats in skslc.
2016-12-29 ethannicholas fix for Vulkan SPIR-V crash on some systems
2016-12-29 mtklein trim another instruction off SkRasterPipeline overhead

BUG=660893,660893,676755

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

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

committed.

BUG=668342

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

Previously, we had two SurfaceInfo objects:

ui/aura/mus/surface_id_handler.h's SurfaceInfo

and cc/surfaces/surface_info.h

This CL switches to using cc::SurfaceInfo instead, transmitting it over
mojo and replaces all call sites where the fields are passed
individually.

SurfaceInfo becomes part of the Mus API: It is the bundle of state
necessary to embed a Surface across processes.

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

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

BUG=567770
R=eroman@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
NO_DEPENDENCY_CHECKS=true

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

BUG=677885

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

BUG=673820

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

These are some reasons to do this:
1. Code can be shared between ES2 and ES3 tests.
2. We don't always create GL_TEXTURE_2D textures in test.
3. We may create textures many times in a single test. In such case,
  it's ugly to delete the textures created in Setup at the beginning of
  each test round.

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

https://pdfium.googlesource.com/pdfium.git/+log/d654d7854951..4741b291f462

$ git log d654d7854..4741b291f --date=short --no-merges --format='%ad %ae %s'
2017-01-03 tsepez Add CFX_RetainPtr Leak() and Unleak() methods

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/2615553002
Cr-Commit-Position: refs/heads/master@{#441296}

ChooserContentView[Cocoa] class name is too generic for //chrome/browser/ui/views/
and //chrome/browser/ui/cocoa directories. So change them to
DeviceChooserContentView[Cocoa] to be more specific.

BUG=651568

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

This test is timing dependent. We now allow more time.

BUG=248938

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

It's no longer used. There is a more cleanup to be done around
renaming files. I'll do that after this.

This also removes what was views_mus_unittests and renames what was views_aura_mus_unittests to views_mus_unittests.

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

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

I'm starting to run clang-format on things, and it's miraculously
not blowing up on <if> or <include> in .js files.  It IS, however,
changing " to ', as JavaScript generally prefers '.

This helps handle that.

R=thakis@chromium.org
BUG=567770

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

Changes:
Because now ui_test_utils::BringBrowserWindowToFront now supports activation waiter, let us reopen these tests for Linux_aura.

BUG=163931
TEST=automated tests

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

This CL-
  - Adds support for multi-line text selection to RenderTextHarfBuzz. To do this
    RenderTextHarfBuzz::FindCursorPosition and
    RenderTextHarfBuzz::GetSubstringBounds are reimplemented.
  - RenderTextHarfBuzz::FindCursorPosition now returns valid grapheme boundaries
    hence fixing issue 673986.
  - RenderTextHarfBuzz::GetSubstringBounds did already support multiline but the
    implementation was flawed. It relied on the text space bounds intersection
    computed from LineSegment's x_range paramater and from TextRunHarfBuzz.
    However these were not in sync if some newline segments were popped or if
    some text was truncated.
  - Enables multi-line text selection for views::Labels.
  - Corrects the behavior for RTL when mouse is dragged above/below the text
    bounds on MacViews.
  - Adds lots of tests.

BUG=650120, 630365, 600166, 673986
TEST= Open views_examples_with_content_exe. Select Labels from the dropdown.
Enter a large string in the "Content" textfield. Enable the Multiline and Text
Selection checkboxes. Ensure text selection works correctly on the Label.

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

Currently, the Form-Not-Secure warning shows up in the autofill dropdown
when the autofill suggestions are shown, but it should also show up on page
load when a password form is autofilled.

This CL adds a ShowNotSecureWarning method that roughly mirrors the
Fill-On-Account-Select flow. When a password form is autofilled on page load,
and when the PasswordFormFillData indicates that the warning should be shown,
the renderer calls ShowNotSecureWarning() to tell the browser to show the
autofill popup with the form-not-secure warning (and no autofill suggestions).

BUG=672668
TEST=Save a password on http://rsolomakhin.github.io/autofill/ in the
Name/Password form. Load the page again and observe that the field
is autofilled with a "Login not secure" autofill dropdown.

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

Removes a bunch of dead code that was relevant years ago before Chromium
even had a compositor, including a capture from the "backing store" and
a separate "render thread" for scaling and YUV conversion. Also,
gutted-out and simplified the unit tests.

In addition, BUILD files were modified so that only the platforms that
have implementation build/link the relevant modules.

BUG=159234

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

When double tapping on Forward navigation button the following happens:
- loadRequest: is called for the first Forward Tap (WKNavigation #1)
- loadRequest: is called for the second Forward Tap (WKNavigation #2)
- didStartProvisionalNavigation: is called for WKNavigation #1
- didFailProvisionalNavigation: is called for WKNavigation #1

CRWWebController used to record WKNavigation #1 as latest navigation
in didStartProvisionalNavigation: overriding WKNavigation #2.

Later inside didFailProvisionalNavigation: CRWWebController cancelled
the load because WKNavigation #1 was determined as latest.

This CL replaces _latestWKNavigation object with CRWWKNavigationStates
object which allows better tracking of latest WKNavigation object.

BUG=677327

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

Layout tests and blink perf tests will run with SlimmingPaintInvalidation
enabled.

BUG=646176

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

Note also the change made to CustomFrameView. Seems odd that this issue exists there after all these years. Maybe I should be making that change somewhere else?

R=sky@chromium.org

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