GitLab

By default use_ozone=false if target_os="chromeos". This causes
use_11=true and the X11 Chrome OS configuration to get built. Make
trybots that have implicit GN arg use_ozone=false specify it explicitly.

This will allow the default value for use_ozone to get changed without
changing the current trybot configurations.

BUG=671355

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

The tests in question need to be rebaselined after V8 has been rolled
with the new asm.js validator enabled. This feature is not yet enabled.

R=machenbach@chromium.org
BUG=chromium:718394
NOTRY=true

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

ImageSet context resources, namely <picture> and srcset based images,
are blockable mixed-content, yet we were sending out such requests, even
if not displaying them, due to the preloadScanner ignoring the difference
between them and `<img src>` based images

This CL fixes that, by blocking such images.

BUG=713440

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

With ARC, the order in which -dealloc is invoker is sometimes changed.
This means that some of CRWWebController delegates may end up calling
methods of CRWWebController between call to -close and -dealloc (until
the autorelease pool is cleared).

Since WebStateImpl calls CRWWebController -close just before releasing
its reference, and CRWWebController becomes unusable once -close has
been called (as -navigationManagerImpl will return nullptr), this does
not introduce an API change of CRWWebController while ensuring that
the delegate registration happens as part of WebStateImpl destruction.

Fixes the crash that caused the revert of http://crrev.com/2846233002/
with the following callstack (truncated):

  0   org.chromium.gtest.generic-unit-test  0x000000010169d83a -[CRWWebController setNavigationItemTitle:] + 266
  1   org.chromium.gtest.generic-unit-test  0x000000010169b2df -[CRWWebController nativeContent:titleDidChange:] + 47
  2   org.chromium.gtest.generic-unit-test  0x0000000101e545c3 -[StaticHtmlViewController observeValueForKeyPath:ofObject:change:context:] + 515
  3   com.apple.Foundation            0x000000010e3ee70c NSKeyValueNotifyObserver + 351
  4   com.apple.Foundation            0x000000010e3edfa7 NSKeyValueDidChange + 495
  5   com.apple.Foundation            0x000000010e3be00e -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] + 118
  6   com.apple.WebKit                0x000000010fcb356a WebKit::PageLoadState::commitChanges() + 1538
  ...

BUG=None

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

Instead of //headless/public/domains, headers under
//headless/public/devtools should now be used.

BUG=718242

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

Sanitizer stacks are supposed to be run through
tools/valgrind/asan/asan_symbolize.py anyhow, which calls llvm-symbolizer.
llvm-symbolizer can do a better job at symbolizing than google::Symbolize
if google::Symbolize doesn't throw away the data llvm-symbolizer needs.

Stack before (both with and without filtering through asan_symbolize):

BrowserTestBase received signal: Segmentation fault. Backtrace:
#0 0x0000007ea911 __interceptor_backtrace
#1 0x0000082e2afc base::debug::StackTrace::StackTrace()
#2 0x00000979d5ce content::(anonymous namespace)::DumpStackTraceSignalHandler()
#3 0x7f04d9814cb0 <unknown>
#4 0x00000fbd5624 BrowserActionsContainer::Layout()
#5 0x00000fbd3c3e BrowserActionsContainer::Redraw()
#6 0x00000f91d38e ToolbarActionsBar::UndoPopOut()

Stack after, not filtered through asan_symbolize:

BrowserTestBase received signal: Segmentation fault. Backtrace:
#0 0x0000007ea911 (/usr/local/google/home/thakis/src/chrome/src/out/asan/browser_tests+0x7ea910)
#1 0x0000082e2afc (/usr/local/google/home/thakis/src/chrome/src/out/asan/browser_tests+0x82e2afb)
#2 0x00000979d5ce (/usr/local/google/home/thakis/src/chrome/src/out/asan/browser_tests+0x979d5cd)
#3 0x7fbcf8399cb0 (/lib/x86_64-linux-gnu/libc-2.19.so+0x36caf)
#4 0x00000fbc96b4 (/usr/local/google/home/thakis/src/chrome/src/out/asan/browser_tests+0xfbc96b3)
#5 0x00000fbc7cce (/usr/local/google/home/thakis/src/chrome/src/out/asan/browser_tests+0xfbc7ccd)
#6 0x00000f91141e (/usr/local/google/home/thakis/src/chrome/src/out/asan/browser_tests+0xf91141d)

Stack after, filtered through asan_symbolize:

BrowserTestBase received signal: Segmentation fault. Backtrace:
    #0 0x0000007ea911 in __interceptor_backtrace ??:0:0
    #1 0x0000082e2afc in base::debug::StackTrace::StackTrace(unsigned long) /usr/local/google/home/thakis/src/chrome/src/out/asan/../../base/debug/stack_trace_posix.cc:745:41
    #2 0x00000979d5ce in content::(anonymous namespace)::DumpStackTraceSignalHandler(int) /usr/local/google/home/thakis/src/chrome/src/out/asan/../../content/public/test/browser_test_base.cc:80:5
    #3 0x7fda947f5cb0 in killpg ??:?
    #4 0x7fda947f5cb0 in ?? ??:0
    #5 0x00000fbc96b4 in BrowserActionsContainer::Layout() /usr/local/google/home/thakis/src/chrome/src/out/asan/../../chrome/browser/ui/views/toolbar/browser_actions_container.cc:364:13
    #6 0x00000fbc7cce in BrowserActionsContainer::Redraw(bool) /usr/local/google/home/thakis/src/chrome/src/out/asan/../../chrome/browser/ui/views/toolbar/browser_actions_container.cc:214:3
    #7 0x00000f91141e in ToolbarActionsBar::UndoPopOut() /usr/local/google/home/thakis/src/chrome/src/out/asan/../../chrome/browser/ui/toolbar/toolbar_actions_bar.cc:534:16

BUG=none

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ff8039d7..342edbef

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,vogelheim@chromium.org

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

While matching rules for elements, we mark elements as affected-by-* for
user action pseudo classes like hover. It means that when the element is
later hovered, we need to recalculate style to apply hover styles to
that element.

In general, we currently don't support pseudo classes after pseudo
elements, but for scrollbar pseudo elements we do:

  ::-webkit-scrollbar:hover {}

However, we do not want such rules to mark the element as affected-by-
hover. The hover style on scrollbar parts get their hover style updated
when hovered regardless of any flags, and making scrollbar pseudo
element rules affect hover updates on the actual elements causes
unnecessary style recalcs.

BUG=716006

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

The outcome is: if device authorization for a renderer is taking too long
it will be interupted. Page load will continue normally, some of the audio
playback on it may not work.

BUG=647498

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

Swarming has only a single Win10-10240 bot but about 30-40 Win10-10586
bots.

TBR=dpranke@chromium.org,mcgreevy@chromium.org
BUG=718379,717347
NOTRY=true

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

BUG=709042

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

Extracts a SuggestionsEventReporter out of SnippetsBridge, that is
responsible for recording backend metrics and sending events used by
the fetch scheduler.

BUG=710268

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

A test suite that depends on a test suite base that provides a
base::test::ScopedTaskEnvironment may need browser threads. Currently,
the test suite cannot use content::TestBrowserThreadBundle to get
these browser threads because base::test::ScopedTaskEnvironment and
content::TestBrowserThreadBundle both set the main MessageLoop and
the TaskScheduler. With this CL, content::TestBrowserThreadBundle
doesn't set the main MessageLoop and the TaskScheduler if they
already exist.

E.g.
Test suite: ToolbarActionViewUnitTest
            Needs BrowserThreads
Base test suite: views::ViewsTestBase
                 Provides a ScopedTaskEnvironment

BUG=

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

Parse Server-Timing response headers and make the metric name(s), value(s), and
description(s) available as PerformanceServerTiming entries on the global
performance timeline and to PerformanceObservers. This feature is behind the
"ServerTiming" experimental-features flag.

To test, turn the flag on
(chrome://flags/#enable-experimental-web-platform-features) and explore to
https://server-timing.now.sh/. Execute `performance.getEntriesByType('server')`
in DevTools to inspect the 4 entries for the base page, as per the response
header:
server-timing:db=100; "Database metric", api=200; "HTTP/API metric", cache=300; "cache metric", total=0.000297322; "Total Response Time"

To inspect the 4 entries for the favicon.ico, you will need to set up a
PerformanceObserver (I use TamperMonkey to inject a content script) like this:
new PerformanceObserver(function(list, observer) {
  console.info(list.getEntries())
  observer.disconnect()
}).observe({entryTypes: ['server']})

Spec: https://w3c.github.io/server-timing/
Intent to implement:
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/y3qwr490Fc4/boGoo41-BwAJ

BUG=702760

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

A speculative change that might help mitigate problems with
WTF::Deque::expandCapacity which sometimes takes over a second
due to heavy load on PartitionAlloc.

I'm hoping in normal operation the default_tq doesn't get more
than a handful of tasks (a quick trace of handouts on a high end
pc suggests the queue depth is <= 3) which would let us avoid
dynamic allocations entirely.

BUG=710245

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

In this CL, support is added to all unit tests targets and the Showcase
Earl Grey tests.

BUG=676034
R=sdefresne@chromium.org,marq@chromium.org,lindsayw@chromium.org

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

The origin whitelist may well be empty, so check that first
before taking on the stringification of the security origin.

R=
BUG=

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

BUG=none

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

This makes the UI consistent with the settings UI.

Screenshots:
before: http://imgur.com/cze5exI
after: http://imgur.com/1Z43yGW

BUG=602666

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

 * Adding perl (needed for CGI scripts).
 * cygwin (possibly needed?)

BUG=717347
TBR=mcgreevy@chromium.org,dpranke@chromium.org

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

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

All calls to LayoutText::AbsoluteQuadsForRange don't use use_selection_height,
so use_selection_height is removed from LayoutText::AbsoluteQuadsForRange and
its callee functions.

BUG=691198

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

This CL adds missing timeout handling functionality [1]. When user
provides timeout value for the push operation, and NFC tag is not
in proximity for the duration of timeout value, operation must be
rejected with timeout error. Unit test is added to test new
functionality.

https://w3c.github.io/web-nfc/#the-push-method (Step 14).

BUG=714037

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

local_ntp_browsertest.cc was actually part of the interactive_ui_tests
target, but most tests there don't need the "interactive" part. This CL
moves the one test that *does* need it into a separate _uitest.cc file,
and moves the _browsertest.cc file into the browser_tests target.

To do this, the uitest-specific parts of InstantTestBase were split out
into a new class InstantUITestBase.

BUG=none

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

This is in preparation for beta and stable Finch configs.

BUG=676655

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

* Adds a new DefaultSearchEngineFirstRunFragment that's
  immediately after data saver and before account sign-in.
  It was put here because the sign-in logic is scary and
  doesn't normally allow a user to back up into it, which
  a user could do if the search engine dialog came after
  it.

* Updates/adds tests to see if the search engine dialog
  appears in the correct spot and allows recording a
  search engine.

Screenshots: go/eabws

BUG=712836,712833

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

This CL prevents items or non-existent IDs from being navigated to. In
order to achieve this, we add support for 'deferred actions', which
allow actions to be created asynchronously. Deferred actions are currently
only used for selecting folders from the Router, but will be used to
simplify search in a follow-up CL.

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

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

FakeCentral allows clients to simulate events that a device
in the Central/Observer role would receive as well as monitor the operations
performed by the device in the Central/Observer role.

BUG=569709

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

Move the WebEntities class out of web/ and into platform/, since it has
no other dependencies inside web/.

BUG=712963

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/0d00147b4f72..18b10cbe616e

$ git log 0d00147b4..18b10cbe6 --date=short --no-merges --format='%ad %ae %s'
2017-05-03 dskiba symbolize_trace: support new heap dump format.

Created with:
  roll-dep src/third_party/catapult
BUG=708930


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.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I6f4ede67585683d8a723daae7684c81e123e4dde
Reviewed-on: https://chromium-review.googlesource.com/495372
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#469287}

This patch adds the fieldwise_diff macro and then uses it to generate
the diff functions on the groups that have been generated so far
(StyleSurroundData) in ComputedStyleBase.

Please note that it can only be used for memebers of those groups too
that have already been generated. This is why the diffing for
BorderData has been left to a later CL.

Diff: https://gist.github.com/nainar/04f49165c4cb5ecb30371fbde1491ddf/revisions

BUG=710938

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

https://skia.googlesource.com/skia.git/+log/0356714916c3..64dbb89efc9d

$ git log 035671491..64dbb89ef --date=short --no-merges --format='%ad %ae %s'
2017-05-03 senorblanco GrTessellator: fix for vertex coincident with enclosing edge.

Created with:
  roll-dep src/third_party/skia


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;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;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=scroggo@chromium.org

Change-Id: Ia9db0a51e7f984fcf3a36cbb81ebae5bee5d218d
Reviewed-on: https://chromium-review.googlesource.com/495591Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#469285}

Network traffic annotation is added to network request of
components/translate/core/browser/translate_url_fetcher.cc

BUG=656607

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

This CL ensures that the NOT_STARTED state is recorded separately from
the STOPPED_BEFORE_COMPLETION state in the installability menu-open
check metrics.

BUG=704369

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

A part of Project Ribbon, separating the parsing logic for CSS
properties from the parser into an API. This patch removes
CSSPropertyFontFeatureSettings from the switch statement in
parseSingleValue, and calls the API instead.

This patch:
- Adds CSSPropertyAPIFontFeatureSettings.cpp to the BUILD.gn file.
- Adds parseSingleValue to font-feature-settings in CSSProperties.json5 so that it will be added to the generated files for the api.
- Moves the parsing logic for font-feature-settings from CSSPropertyParser.cpp to
  CSSPropertyAPIFontFeatureSettings.cpp, which implements CSSPropertyAPI.h.

Diff: https://gist.github.com/jm318/db6da170e28cb7fefa0056a364f164f0/revisions

BUG=668012

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

This CL makes the context menu for bookmark items appear when an item is
clicked.

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

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

TBR=rockot@chromium.org

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

[Cleanup] Use IsStandaloneExtensionProcess in ChromeContentRendererClient::ShouldGatherSiteIsolationStats()

BUG=None

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

TBR=rockot@chromium.org

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

TBR=rockot@chromium.org

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