GitLab

This reverts commit 6ee4f021.

Reason for revert: 
This breaks Chrome PFQ with error:
chromeos-chrome-59.0.3067.0_rc-r1: ../../../../../../../home/chrome-bot/chrome_root/src/third_party/binutils/Linux_x64/Release/bin/ld.gold: error: cannot find -latomic



Original change's description:
> Make transport security state generation part of the build.
> 
> This CL adds a build step to generate transport_security_state_static.h
> when required.
> 
> Bug:595493
> 
> Change-Id: I478137a40d9107cbcc6470ee544bda66823ebbff
> Reviewed-on: https://chromium-review.googlesource.com/471529
> Reviewed-by: Lucas Garron <lgarron@chromium.org>
> Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
> Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#463090}

TBR=rsleevi@chromium.org,peter@chromium.org,lgarron@chromium.org,martijn@martijnc.be,cbentzel+watch@chromium.org,net-reviews@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.

Change-Id: I84536c89c093531f1cf60cbdd4a3cfb2efbe5d80
Reviewed-on: https://chromium-review.googlesource.com/474009Reviewed-by: Yury Khmel <khmel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#463428}

BUG=652781

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

This CL follows on the steps of [1] and wires the supported
auto white balance/focus/exposure modes for the Android
implementations -- whereas on ToT only the 'current' state
of these features was collected.

Manually tested using N7 and N6P and
https://rawgit.com/Miguelao/demos/master/imagecapture.html

[1] https://codereview.chromium.org/2806743003/

BUG=700607

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

Test=manual
BUG=34847872

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

WebappInfo#isLaunchedFromHomescreen() should return false for WebAPKs
launched from an external intent.

BUG=691739

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

Also add two icons, including a custom icon.

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

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

This was regressed in crrev.com/9d09b0ae.

BUG=709855

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

This flag should have been dropped in [1] since we dropped setting
kNeedsReattachLayoutTree initially in that CL.

[1] https://codereview.chromium.org/2760233004

R=nainar@chromium.org
BUG=595137

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

Linker complains an undefined reference to
'content::MediaStreamDispatcher::GetNonScreenCaptureDevices()' when
building Cast for Android with enable_webrtc being false.

BUG=Internal b/37205701

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

Make setupConnection oneway/async. Add a ICallbackInt interface to
return the PID of the child process. The reply is then posted back to
launcher thread. Connection setup is already mostly async so only
involves moving related code to the reply callback.

One caveat is that getCallingPid no longer works and just returns 0
for oneway calls. The pid check is not strictly necessary, so dropped
the from setupConnection instead.

BUG=689758, 690118

Review-Url: https://codereview.chromium.org/2810433002
Cr-Commit-Position: refs/heads/master@{#463332}
Committed: https://chromium.googlesource.com/chromium/src/+/39c7bd71dc2f9c9f692dd346e4e4e525af25ede1

Reland contains fix for flaky test. The pid is received asynchronously
now, so wait for it after allocating a connection.

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

Due to some earlier changes to do with mapping chrome to android
permissions, this infobar incorrectly thinks there are multiple
permissions being requested for geolocation.

BUG=709206

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

For parallel download, the received slices are currently passed in the
constructor of DownloadFileImpl, which is earlier than the etag check
logic in DownloadItemImpl. This raises an issue that the
DownloadFileImpl will use the out-dated received slices data. It will
block the download to refresh the data with new strong validators, and
download won't complete.

This CL cleared the received slices in DownloadItemImpl, and pass the
received slices to DownloadFileImpl via Initialize call instead of the
ctor.

Alternatively we may do it in DownloadManagerImpl, but it's probably
better to do this kind of clean up in DownloadItemImpl.

When etag changes, currently for a normal download, we update the etag
in DownloadItemImpl::UpdateValidatorsOnResumption, and
DownloadSaveInfo::offset is set to 0 in
DownloadRequestCore::HandleSuccessfulServerResponse, where we pass this
0 offset to BaseFile::Initialize to truncate the file size to 0.

BUG=706182, 644352

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

BUG=689992

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

This test has been flaky on devices because Earl Grey fails to
synchronize with omnibox text.

This CL first fixes the flakiness by adding a wait to wait for omnibox
text, and then this test seems to be more related to form submission,
so moving it to FormsTestCase.

BUG=

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

Notify BrowserGpuMemoryBufferManager from GpuProcessHost the reason for
failure to allocate gpu memory buffer. The gmb-manager then uses that
information to decide whether it can try again. This allows simplifying
the relevant code in BrowserGpuMemoryBufferManager.

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

Before this CL, logic to wait for a WorkCallback to run or be
abandoned was duplicated in multiple
ModelSafeWorker::DoWorkAndWaitUntilDoneImpl() implementations.

With this CL, ModelSafeWorker::DoWorkAndWaitUntilDoneImpl() is
replaced with ModelSafeWorker::ScheduleWork(). Implementations
are merely responsible for scheduling the callback that they
receive; they don't have to wait for it to run or be abandoned.

The logic to wait for the callback to run or be abandoned is moved
into ModelSafeWorker::DoWorkAndWaitUntilDone().
ModelSafeWorker::DoWorkAndWaitUntilDone() calls
ModelSafeWorker::ScheduleWork(). Then, it waits until either the
callback that it passed to ModelSafeWorker::ScheduleWork() is deleted
(may or may not have run) or ModelSafeWorker::RequestStop() is called
before the callback has started to run. Additionnaly, calling
ModelSafeWorker::RequestStop() transforms into no-op further
invocations of callbacks passed to ModelSafeWorker::ScheduleWork().

Unblocking ModelSafeWorker::DoWorkAndWaitUntilDone() when
ModelSafeWorker::RequestStop() is called is important to
prevent deadlocks in workers that schedule work on the UI
thread. Indeed, in Chrome, no tasks are scheduled on the UI
thread after ModelSafeWorker::RequestStop() is called and
pending UI tasks are not scheduled until after the sync thread
is joined.

BUG=663600

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

BUG=661810

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

This generalizes the fall-back to using base::debug::StackTrace to
capture stack traces in builds which lack frame pointers, allowing
native heap profiling to generate useful data, albeit with a more
significant performance penalty.

Changes made in the earlier patch for native heap profiling stack
capture under Windows are un-done in favour of the following:
1. MemoryDumpManager always allows native heap profiling[1].
2. HeapProfilerAllocationContextTracker chooses whether to use
   base::debug::StackTrace or TraceStackFramePointers() based on
   the value of BUILDFLAG(CAN_UNWIND_WITH_FRAME_POINTERS).
3. BUILDFLAG(CAN_UNWIND_WITH_FRAME_POINTERS) is no longer defined in
   configurations which we cannot use frame pointers for unwinding[2].

[1] Though note that only certain build configs actually support
    the necessary allocator shims; this will be addressed later.
[2] Frame pointers are only available in profiling & Debug builds on
    some platforms, and are available but unsuitable for us to use for
    stack unwinding, on others.

BUG=686208

Review-Url: https://codereview.chromium.org/2757123002
Cr-Original-Commit-Position: refs/heads/master@{#460311}
Committed: https://chromium.googlesource.com/chromium/src/+/22b017b9b241c47db8cf25c57c89c0b0d7fcfbe2
Review-Url: https://codereview.chromium.org/2757123002
Cr-Commit-Position: refs/heads/master@{#463411}

Change dest_language to target_language in the logistic regression model for consistency with google3 proto and translate_event_protos.

BUG=646711

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

Plugin (WebPluginContainerImpl) does not keep its own state about
visibility of parent, and once it is no longer inheriting from
FrameViewBase, it will not implement any ParentVisible methods.
If required, it could always call parent_.IsVisible.

BUG=637460

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

Fixing checkbox resizing, making them disabled and a bit transparent
when blocking overall is disabled, enabling blocking when adding a new
pattern.

BUG=709943

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

The intent of this change is to add some signal data to the bottom of
a MHTML file when generating an offline file if the new OfflinePagesLoadSignalCollecting flag is set.  The signal data
will be analyzed to find a better time to take snapshots, and will eventually be used to decide at runtime when to take snapshots.  Design docs here:
https://docs.google.com/document/d/1AcoZOIb81V68_KDSOCatFSYYMLOTSYj6resg-VAxLgo

BUG=706628

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

BUG=709571
TEST=browser_tests
TBR=mahmadi

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

Currently, we show keyboard on window focus gain only when we previously
lost window visibility, which we introduced to fix crbug.com/168288.

Extending the current logic to resume keyboard input when regaining
focus from a pop-up window such as voice input window.

BUG=344235

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

WillDrawSurface is no longer being used on the client side. Removing it would
reduce the number of IPCs we send.

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

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

[Media Capabilities] Rename query() to decodingInfo() and MediaDecodingAbility to MediaCapabilitiesInfo

This is matching recent spec changes:
https://github.com/WICG/media-capabilities/pull/31

The MediaConfiguration changes are not reflected in this CL.

BUG=690380
R=mcasas@chromium.org,sandersd@chromium.org

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

Revert of Only create sticky position constraints for constrained sticky position. (patchset #4 id:60001 of https://codereview.chromium.org/2769353002/ )

Reason for revert:
It causes telemetry_perf_unittests failing on chromium.android/Android N5X Swarm Builder.

crbug.com/710142.

Original issue's description:
> Only create sticky position constraints for constrained sticky position.
>
> If sticky position is unconstrained we don't need to create constraints for it,
> or add it to viewport constrained objects (causing scroll on main), or repaint
> on scroll.
>
> BUG=704817
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
>
> Review-Url: https://codereview.chromium.org/2769353002
> Cr-Commit-Position: refs/heads/master@{#463316}
> Committed: https://chromium.googlesource.com/chromium/src/+/06e9b5a6a5649e4d842f40ad667554c58dc26c29

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

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

Replace ASSERT, RELEASE_ASSERT, and ASSERT_NOT_REACHED
with DCHECK_op, CHECK_op, and NOTREACHED respectively in
third_party/WebKit/Source/core/fileapi

BUG=707641

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

This CL fixes/refactors two layout tests that used to depend on ability
to find the opener via window.open, even in case of ctrl-click or
shift-click.  This dependency is incorrect and will be broken once
https://crbug.com/658386 is fixed.

The tests had to be refactored so that they don't depend on ability to
communicate back with the main test window.  After this CL the tests
report their results via testRunner.setCustomTextOutput (rather than
sending the results back to the main window using window.postMessage).

In the 2 tests here, the custom text dump is being set from a secondary
test window - the CL also needs to relax the condition that limited
propagation of LayoutTestRuntimeFlags to the main test window.  The
intent of the original condition should have covered both secondary
and main windows (i.e. the intent was to just check if the renderer
has received a LayoutTestRuntimeFlags).  It seems desirable overall
to also propagate LayoutTestRuntimeFlags changes originating from
secondary test windows.

BUG=658386

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

Revert of Followup comments from r460581. (patchset #1 id:1 of https://codereview.chromium.org/2781383002/ )

Reason for revert:
Exposed races with FrameHostMsg_DidStopLoading

BUG=710062

Original issue's description:
> Followup comments from r460581.
>
> BUG=365039, 705559
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
>
> Review-Url: https://codereview.chromium.org/2781383002
> Cr-Commit-Position: refs/heads/master@{#461012}
> Committed: https://chromium.googlesource.com/chromium/src/+/8393de464114cb0a3d5e82a93a491728aa49e043

TBR=nasko@chromium.org,dcheng@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=365039, 705559
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

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

Revert of Improve unit tests for OnQueueNextWakeUpChanged (patchset #1 id:1 of https://codereview.chromium.org/2810663002/ )

Reason for revert:
Revert of https://codereview.chromium.org/2798563003 will invalidate this patchset.

Original issue's description:
> Improve unit tests for OnQueueNextWakeUpChanged
>
> BUG=
>
> Review-Url: https://codereview.chromium.org/2810663002
> Cr-Commit-Position: refs/heads/master@{#463247}
> Committed: https://chromium.googlesource.com/chromium/src/+/e206dbe248c7727f81424d6b89274a52def52e6a

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

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

Things like kInvalid and kCreated are too generic to end up in the
top-level Blink namespace. Changing this to be a scoped enum revealed
some difficulties with using/testing scoped enums in Blink which will be
addressed in followup CLs.

Bug: 709817
Change-Id: Ied242566e204fb3ad6cbf7e703727eada698b57e
Reviewed-on: https://chromium-review.googlesource.com/473469Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#463397}

The JumpListIcons delete task deletes the existing icons in JumpListIcons,
while the update task creates the new icons, writes them into JumpListIcons
and notifies the shell. It is better to separate them so we can track
the individual cost. Since a base::SingleThreadTaskRunner is used for
posting these tasks, the tasks are always running in the correct order.

This CL also adds a base::SequencedTaskRunner for JumpListIconsOld
delete tasks as they are not required to run on a single thread.

BUG=40407, 179576

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

If the browser has started shutting down, then do not attempt to relaunch
the gpu process.

BUG=709890

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

This CL replaces uses of ScriptState::GetExecutionContext with ExecutionContext::From in the bindings generator code.

BUG=682322

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

This is a follow up to issue 2795603002.

BUG=691108

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

Manually converted tests to use new Audit.

BUG=704967
TEST=
ChannelMerger/audiochannelmerger-basic.html
ChannelMerger/audiochannelmerger-cycle.html
ChannelMerger/audiochannelmerger-disconnect.html
ChannelMerger/audiochannelmerger-input-non-default.html
ChannelMerger/audiochannelmerger-input.html

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

After the CL: https://codereview.chromium.org/2235283003 which implemented composition
range information tracking on the browser side for Mac, the method TIM::GetCompositionRangeInfo
was changed to take the RenderWidgetHostView for which the information is required. However,
the view pointer is not actually used and the method returns the stored information for |active_view_|
instead.

BUG=NONE

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

This ensure that when an activity loses input focus (OnWindowFocusChanged), that the web page is blurred and not considered to be focused.

BUG=686232

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

I'm not actually sure why this was on the list of conflicting method
names, but it doesn't appear to be necessary.

Bug: 709987
Change-Id: Ib2841a19243f485b9191dd933b92fdd3223470d2
Reviewed-on: https://chromium-review.googlesource.com/473367
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#463389}