GitLab

This behavior was used to either force IPv4 resolution on dual-stack devices (using the --disable-ipv6 command-line flag) or to force IPv6 resolution.

Now that the flags have gone away, this behavior is no longer needed in the HostResolver.

BUG=344685

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

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

Call LeakSanitizer before RenderViewTest::TearDown(), as the latter may
leak WebKit objects when it shuts down V8.

BUG=328552,463143
TBR=jochen@chromium.org

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

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

BUG=457697

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

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

Add the ability to create a CronetUrlRequest with a priority.
BUG=

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

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

BUG=

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

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

Switch to using the definitions from src/public/ where possible.

Change DEPS to remove blanket allowances of src/trusted/desc/, and
only whitelist some remaining required headers.

BUG=https://code.google.com/p/nativeclient/issues/detail?id=2832
TEST=build

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

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

This is a re-land of https://codereview.chromium.org/1126383005, fixed
not to cause a crash when 'WebView.loadUrl' is called from inside the
onReceivedTitle callback, added a regression test. Also, the document
title is now cached to minimize the amount of callback calls.

Original patch description:

The usual channel for delivering onReceivedTitle (via updating title for
a NavigationEntry) doesn't work in the case of history navigations, because
WebContentsImpl silences no-op updates of entries titles.

Chrome Browser uses another event for updating the title in this case --
via WebContentsDelegate::LoadingStateChanged. This patch enables WebView to
use it as well.

Note that WebChromeClient.onReceivedIcon doesn't need to be re-sent, as
nobody seems to bother checking whether the icon update is a "no-op", so
updates on history navigations just work.

BUG=481570,495234

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

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

R=jlklein@chromium.org
BUG=none

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

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

SequencedSocketData is a bit cleaner and easier to use than the
alternatives, which we may want to get rid of, long term.

HttpStreamParser.AsyncChunkAndAsyncSocketWithMultipleChunks did rely on
DeterministicSocketData's behavior to get in a state where the previous
chunked upload body write was pending when data was appended to the
chunked upload data stream, but the updated test uses a new method to
ensure that happens.

BUG=492696

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

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

Noticed this was hanging around after the NavigationTransitions cleanup, was originally used in a test but now nothing calls it.

BUG=370696

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/89d5988..cb67414

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=caryclark@google.com

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

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

In order making testing more convenient, this CL does the following
refactoring:

- Creates a new virtual CreateCharacteristicsFinder in
BluetoothLowEnergyConnection;
- Starts the connection on BluetoothLowEnergyConnection after a call to
Connect() (this was already suggested by tengs@ in a previous CL);
- Creates a new protected constructor in BluetoothCharacteristicsFinder;
- Mocks for BluetoothCharacteristicsFinder and
BluetoothLowEnergyConnection;

The unit tests covers the Connect() and Disconnect() execution paths. A
second part will cover receiving bytes and Send().

This CL also fixes some small bugs on BluetoothLowEnergyConnection.

BUG=

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

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

There are actually two changes here:
. Convert HTMLViewerApplication to use an ApplicationImpl rather than
  be an Application.
. Make HTMLDocument use services from the application it was created
  for rather than HTMLViewer's application.

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

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

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

Previously OverscrollWindowDelegate sometimes would call OnOverscrollModeChange on its delegate even if the overscroll mode didn't change. Specifically this happened for OVERSCROLL_NONE when an overscroll-cancelling condition such as a mouse move would occur.

This could confuse OverscrollWindowAnimation and make it cancel the overscroll animation which shouldn't have been cancelled. On Windows there is currently a mouse event dispatched after each swipe on the touch screen, so this caused crbug.com/493672.

BUG=493672

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

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

TEST=FocusControllerApiTest.DuplicateActivationEvents
TEST=FocusControllerApiTest.ActivationEvents
TEST=FocusControllerMouseEventTest.DuplicateActivationEvents
TEST=FocusControllerMouseEventTest.ActivationEvents
TEST=FocusControllerGestureEventTest.DuplicateActivationEvents
TEST=FocusControllerGestureEventTest.ActivationEvents
TEST=FocusControllerHideTest.ActivationEvents
TEST=FocusControllerDestructionTest.ActivationEvents
TEST=FocusControllerRemovalTest.ActivationEvents

BUG=489813, 489814

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

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

This reverts commit 5d18b249.

Reason: Broke iOS build: http://build.chromium.org/p/chromium.mac/builders/iOS_Simulator_%28dbg%29/builds/27843

NOTRY=true
NOTREECHECKS=true
BUG=465354
TBR=sievers@chromium.org,nick@chromium.org

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

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

Several bots occasionally fail commands immediately following calls to
DeviceUtils.EnableRoot with "device not found" errors. I think this may
be because adb wait-for-device can come back before the device is
completely available. Switching to WaitUntilFullyBooted should ensure
that the device has returned to a usable state (or is actually gone).

BUG=493900

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

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

As |GaiaAuthFetcher::CreateAndStartGaiaFetcher| can already be
specialized by a subclass, |GaiaAuthFetcher::CancelRequest| should as
well, to allow specialized fetchers to be cancelled.

BUG=495597

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

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

The results of this test will improve dramatically when
crbug.com/317007 is fixed.

BUG=317007

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

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

This patch was mostly autogenerated with
https://codereview.chromium.org/1010073002/.

BUG=465354
TBR=nick@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/f54e04d..ea9a19d

TBR=leviw@chromium.org

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

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

WebRTC 9381:9384
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/020eb8a..b125ba2

Libjingle 9381:9384
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/34e6126..78b410b

TBR=
BUG=

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

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

Link map's l_addr field should contain the load bias:
- https://android-review.googlesource.com/#/c/46470/2/linker/linker.cpp

It currently contains the load address.  Where the min vaddr of LOAD
segments is zero, the load address and load bias are the same, and the
problem remains hidden.  Android's relocation packer generates a
non-zero min vaddr, and this exposes the problem on arm64 platforms.

The symptom is abort in uw_init_context_1, where uw_frame_state_for
returns _URC_END_OF_STACK rather than (expected) _URC_NO_REASON.
gcc's stack unwinding code does not find correct unwinding information
after an incorrect l_addr has been used to convert from virtual to
physical addresses.  Arm32 does not show the problem because it uses
dl_unwind_find_exidx in place of _Unwind_IteratePhdrCallback.

See also line 196 of:
- https://android.googlesource.com/platform/bionic/+/
      lollipop-mr1-release/linker/linker.cpp

BUG=385553

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/b1cb1e9..f54e04d

TBR=leviw@chromium.org

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

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

BUG=481955

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

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

This replaces the only "onUserNavigation" callback with
"onUserNavigationStarted" and "onUserNavigationFinished", and delivers
it.

Note: this change modifies the Service AIDL file, so this is an
incompatible change for the client applications.

BUG=484639

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

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

This CL adds GetInstalledExtension() method to ExtensionRegistry and
uses it instead of deprecated ExtensionService::GetInstalledExtension()
in chrome/browser/ui/app_list/.

Part of removing the deprecated GetInstalledExtension() call
from the ExtensionService.

BUG=489687

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

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

They both are totally same and TimeSource is removed.

BUG=494892
R=skyostil@chromium.org, mithro@mithis.com

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

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

BUG=483467
TBR=ccameron@chromium.org,primiano@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/454514b..b1cb1e9

TBR=leviw@chromium.org

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

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

WebRTC 9354:9381
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/13eda41..020eb8a

Libjingle 9354:9381
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/9329d80..34e6126

TBR=tommi,pbos

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

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

For updates, don't write the main script to disk until a change with the
incumbent script is detected. The incumbent script is progressively
compared with as the new script is read from network. Once a change is
detected, copy everything matched up until now to disk, and from then on
write to disk as the script continues to be read from network.

BUG=457013

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/83034c6..454514b

TBR=leviw@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/45f16061..607696b0

Please follow these instructions for assigning/CC'ing issues:
https://code.google.com/p/v8-wiki/wiki/TriagingIssues

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

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

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

This was supposed to land in https://codereview.chromium.org/1142153002/ but I forgot to commit and upload the last change set :(

This removes two fields no one uses anymore from the navigation details struct.  It also eliminates some using statements from infobar_service.cc and inlines a helper into its now-lone caller.

BUG=none

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

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

- "Hit rate": Whether the application predicted correctly.
- "Lead time": How much time between the prediction and the actual launch.

BUG=493170

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

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

Swiffy updates animations based on the current time (Date.now()), so we
shouldn't override that function to return dummy values.

BUG=493357

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

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

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/9766f7e..83034c6

TBR=leviw@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/ce5a5df..9766f7e

TBR=leviw@chromium.org

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

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