GitLab

Prior to this CL, the AutocompleteTextField becomes first responder if the user
left-clicks a decoration. This is a bug that this CL fixes. This also fixes a
bug where ZeroSuggest did not disappear when the user drags the origin chip.

BUG=356887

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

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

Previously MessageReader was stopping reading after the first error,
but wasn't notifying the client about the problem. This results in some
errors (e.g. from SSL layer) being ignores while they should terminate
connection.

BUG=487451

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

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

TBR=
BUG=

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

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

TBR=oshima@chromium.org
BUG=487501

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/1ba8cc9..88c23fc

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

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

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

the PLT histograms for LoFi.

This CL adds 2 more boolean parameters to an existing IPC call
that tells us whether the page load happened with LoFi on with
bad network conditions or LoFi off with
bad network  conditions. The methods in the data reduction
proxy code currently return false and would be fixed in the
forthcoming CL.

Auto LoFi status keeps changing (on a page load basis)
depending on the network conditions (e.g., enabled only when network
quality is bad). Just because session is in a field trial does
not guarantee that LoFi would ever be used.  Using a synthetic
trial or only using the field trial will give very
noisy data in this case.

This is a temporary CL for LoFi Android experiment. Eventually,
we want to read the LoFi status using the headers of the
response instead of reading the current LoFi status (which might
be a bit stale) but that requires putting custom
HTTP headers in the response message from data saver proxy.

BUG=485633

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

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

For example:
- third_party/ffmpeg/libavcodec/arm/hpeldsp_arm.S
- third_party/ffmpeg/libavcodec/x86/xvididct.asm

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

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

When the flag or field trial is set such that non-secure origins will be
marked as dubious/non-secure, use |IsOriginSecure| to determine whether
an origin is non-secure, instead of simply treating http:// and ftp://
as non-secure. This means that http://nytimes.com will be marked as
dubious/non-secure, but not http://localhost (for example).

BUG=487499
TEST=Enable the "Mark non-secure as non-secure" flag in
chrome://flags. Visit http://nytimes.com and observe that the lock icon
is red and crossed out. Visit an http:// URL on localhost and observe
that the lock icon is neutral.

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

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

We log picture size in UMA histograms every time we
prepare to draw. In order to make that code faster,
precompute the pile size when it is constructed.

R=jbroman, enne

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

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

TBR=oshima@chromium.org
BUG=487706

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

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

R=dbeam@chromium.org
BUG=

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

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

The Lenovo Horizon device displays the wrong number of the touch pointers when all fingers released from the screen. Because HWND Message sometimes sends inconsistent number of touch pointers, we keep the IDs of touch pointers we have seen from last time, and release the ones which are not in the current message.

BUG=316085

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

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

This is to remove dependencies from test runner on content

BUG=478250
R=mkwst@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/b333144..d7eac4f

TBR=alancutter@chromium.org,jsbell@chromium.org

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

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

chrome_extensions.js: be4926041286f314d648ab5f3fcce5721693e602 -> ca37fefd29fef41fa481685c4b3398ba6ad10b8d

Also manually added networkingPrivate.onDeviceStateListChanged while it
makes its way to the github externs (to fix compile).

TBR=
BUG=

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

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

R=vabr@chromium.org
BUG=486739

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

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

BUG=429053
TEST=gpu_unittests
R=piman@chromium.org

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

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

Some of ui::WindowShowState were not supported in Linux so this CL implemented
SHOW_STATE_MINIMIZED, SHOW_STATE_MAXIMIZED, and SHOW_STATE_FULLSCREEN state.

BUG=473228

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

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

When a reload occurs (or other inert commits), we leave the history tree alone. However, if iframes are dynamically created, we end up with both the old iframes and the new iframes in the history tree, and we never prune them. Instead, if a different-document inert commit occurs, remove the committing node's children, since the corresponding frames are no longer in the frame tree.

BUG=485385

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

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

BUG=485381

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

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

always recreating was causing extra XRANR event on X11 system.

Delete WindowTreeHost asynchronously when the change can be made via input event.

BUG=484580,486190
TEST=tested manually. no flicker.

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

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

This adds the tests which are green on chromium.fyi's Chromium Mac 10.10 builder.

BUG=449316

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

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

Really minor cleanup, remove some unused code from the header.

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

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

.sh tests don't work on Windows.

BUG=486571
R=thakis@chromium.org

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

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

BUG=487800

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

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

Mainly to remove dependency from test runner on content

BUG=478250
R=enne@chromium.org

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

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

BUG=471536

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

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

MigrationSingleClientTest.AllTypesIndividually
MigrationSingleClientTest.AllTypesIndividuallyTriggerNotification

BUG=403778

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

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

Fixes the issue where an OnSetDuration call truncates the selected_range_ and resets the
next_buffer_position. kEndOfStream is now returned instead of kNeedBuffer from
GetNextBufferInternal when selected_ranges_ is NULL.

BUG=484992

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

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

It is now possible to remove extensions from the GL_EXTENSIONS string
by specifying "--disable-gl-extensions=extension1,extension2".

R=sievers@chromium.org
BUG=482067

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

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

App banners require several engagement, service worker, and manifest
checks to pass before being displayed. This allows developers to see
in the console the reasons why banners are not displayed, given the
switch --bypass-app-banner-engagement-checks on chrome startup

BUG=458866

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

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

Wires the call to Add/RemoveHeartbeatInterval through:
* GCMDriver/Desktop/Android/Fake
* GCMDriverDesktop::IOWorker
* GCMClient/Impl to MCSClient
* Adding loading of persisted interval in MCSClient

BUG=481174

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

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

Enable the BLUETOOTH, BLUETOOTH_ADMIN
permissions for use with Web Bluetooth.

BUG=471536

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

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

BUG=485435

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

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

1. Recently close tabs
2. Download cancel dialog
3. Cloud Printer discovery
4. extension: usb device selection

For #2, some strings are revised per the string review with ainslie@.
For both browser shutdown and incognito exit, the title is simply
'Download in progress' and the 'go-ahead' button is simply 'Cancel download'
(or their plural forms).

Besides, recently_closed.js is also removed because it's not used any more and removing it let us drop two strings (about closed_tabs) that has become unnecessary with this CL.

BUG=21407,455005,482092
TEST=Open a new window, open multiple tabs and close the windows. In another window, go to 'Recent tabs' menu. '# tabs' for the closed window is shown as expected
TEST=1. Go to http://www.thinkbroadband.com/download.html 2. Start downloading a single file 3. Try to quit chrome before the download is completed 4. Check the dialog popping up.
TEST=Do the above with multiple file downloads
TEST=Do the above two in the only open incognito window (close the only open incognito window)

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

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

The method can be called from Files app, and crashes if there are no
browser windows open.

BUG=None

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

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

When building a debug version of Chromium in Linux with
component=shared_library build flag, there are link errors as follows:

error: undefined reference to 'SkDebugf_FileLine'
error: undefined reference to 'SkToS32'

BUG=None

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

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

BUG=487674

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

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

This fixes the component=shared_library build on Chrome OS. Previously,
the TPM token initialization would crash the browser because libchaps.so
loads a 2nd, incompatible copy of the protobuf-lite library into the
browser.

The crash happens because by default the global scope takes precedence,
so symbols in the bundled copy shadow symbols in the system copy. This
can lead to accessing the wrong object or calling the wrong function.
The usual symptom is a crash during static initialization of libchaps.so.

RTL_DEEPBIND rearranges the scope for libchaps.so so that the system
library takes precedence instead. The scope for chrome is unaffected.

Some other possibilities were considered:

  - Unbundling the library. This would cause us to lose our local
    modifications to libprotobuf on Chrome OS.

  - Fixing the soname so that the bundled copy is used by chaps. This
    doesn't even link because the bundled code is not ABI compatible
    with upstream.

  - Statically linking libchaps.so. This is tricky because we need
    position-independent static libs for its deps, and we don't support
    building those currently. It will also cause bloat.

This hack is minimally invasive and allows use of shared library builds
on Chrome OS devices.

BUG=175508
TEST=cros chrome-sdk --board=link
  GYP_DEFINES="$GYP_DEFINES component=shared_library" gclient runhooks
  ninja -C out_link/Release chrome chrome-sandbox
  deploy_chrome --board link --build-dir out_link/Release --to $IP
  Log into the system. No crash.
  TPM-backed user certs show up in chrome://certificate-manager.

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

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

Whitespace in the form of tabs and line feeds and the like can screw
things up.

This fixes the fresh.amazon.com bug.  (I tested it interatively.)

By the way, there is no need to do a migration pass.
The data will be correctly loaded when read from the
database.  (I checked.)  While it's true the database
will be out of date until written again, given that
the actual data used is correct, I don't think that's
an issue.

TBR=rdevlin.cronin,isherman,lazyboy,pvalenzuela,kmadhusu,avi
rdevlin.cronin - this trivial template URL data API change required some changes in chrome/browser/extensions
isherman - this trivial template URL data API change required some changes in chrome/browser/importer
lazyboy - this trivial template URL data API change required some changes in chrome/browser/renderer_context_menu
pvalenzuela - this trivial template URL data API change required some changes in chrome/browser/sync/test/integration
kmadhusu - this trivial template URL data API change required some changes in chrome/browser/ui/search/
avi - this trivial template URL data API change required some changes in chrome/browser/ui/cocoa/browser/

BUG=485357

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

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