GitLab

This brings in:
f650510  Fix build after previous commit.
217ecf35  Simplify PDFium by removing code that's not used in the open source repo.
2399550  m_pColorSpace can not be NULL for image object with DCTDecode filter
8695172  Do not do strict check of BitsPerComponent for RunLengthDecode filter
381b911  Lab colorspace needs to be 3 component
ca5d769  Trailer should be a dictionary object
4429eaa  Replace manual/error-prone/hard-to-verify arraysize calculations with safe FX_ArraySize macro.
b69da0b  Getting rid of more (FX_LPCWSTR) casts and fixing two bugs revealed by this.
4b87f7b  Cleanup: Remove an unused function.
df76a19  Add a missing 'using' keyword in big integer library
91dd8c7  Modify big integer library
44047c3  Remove unnecessary files in third_party/bigint
7504b3d  Initial check in of big integer library, v2010.04.30
4643533  Update to openjpeg r2944

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

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

Essentially wires up the window.print() and the basic printing path
to Android framwork's PrintManager.

The changes affect the basic printing path using
PrintingMessageFilter::OnScriptedPrint. When calling window.print() on
Android, it would now be called twice.

The first time is directly after the JS call, OnScriptedPrint is called
with a parameter telling it that it's being called from JS. It will then
end up calling PrintJobWorker::GetSettings, forwarding that information.
PrintJobWorker then takes care of calling PrintingController through JNI,
joining the same code path used when printing from chrome's menu in android:
Android framework's PrintManager is invoked, and it manages the preview, using
the tab to generate the output as the user changes his/her preferences.

Why so many changes for just that: the window.print() call is blocked until the
end of the process by message pumping. It has to be disabled when printing is
finished. It is currently done by setting a callback in the current
PrintingContext, that will be called when printing is done. PrintingController
stores the reference to it, but here we have two queries at the same time, and
only the latest PrintingContext would be stored. I added a field to store
separately the one coming from the initial call, so
that it can be used when printing is done to stop the message pumping.

TL;DR: When window.print() is called, the basic printing path is used to forward
the query to PrintManager. The PrintManager then uses almost the same path to
actually print the document (as previously implemented to power the 'Print...'
entry in the menu). The changes are mostly to ensure that JS returns when
printing is completed and not before (or never).

BUG=437338

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

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

QUIC-specific variable name change.

Changes largest_observed_acked to rtt_updated in various places to be
more accurate.

Merge internal change: 81685775
https://codereview.chromium.org/800213002/

Changing QUIC cert selection to do VIP based selection.

Used IPEndPoint as the type for server_ip in all methods ala
client_ip.

Ran "git cl format net" to fix formatting issues.

Merge internal change: 81571450
https://codereview.chromium.org/802873002/

QUIC - Added QuicConnectionPeer::GetStats while porting the following
intenal server change:

Improving rtt for QUIC for 0-rtt handshakes guarded by a flag.

Merge internal change: 81435895
https://codereview.chromium.org/798183002/

QUIC - use the correct type and fix the formatting fixes.

Changes found while merging the following change from Peter Kasting into
the internal source tree.

"pkasting CL: https://codereview.chromium.org/761863002/

Clean up type usage and fix MSVC "truncated value" warnings in
net/quic/.

The existing code is very inconsistent about whether it uses typedefs
like QuickByteCount and QuicPacketCount or whether it instead uses
fundamental types like uint32, uint64, and size_t.  This is not only
more confusing to read, in some cases it leads to MSVC warning about
"possibly truncated value" when one type is implicitly converted to
another, shorter one.

This attempts to fix at least some of these sorts of problems by using
the typedefed types more widely when possible, or else at least the same
basic types other places are already using.  It also fixes various
warnings by including explicit casts (sometimes with legality checks)."

No functionality change. Changes to keep the code similar to internal
source tree.

Merge internal change: 81428557
https://codereview.chromium.org/787253005/

Use std::cbrt instead of our own CubeRoot implementation.

Merge internal change: 81420733
https://codereview.chromium.org/798153002/

R=rch@chromium.org

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

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

Nuke "VolumeManager.isType".
Add test coverage of importer_common methods.
Make all "DCIM" dir-name matching case-insensitive.

BUG=420680
TEST=browser_test: FileManagerJsTest.*

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

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

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

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

Dedupe files while scanning against local history.
Hook up import history to media scanner in background.

BUG=420680
TEST=browser_test: FileManagerJsTest.*

jwd@ for historgrams.xml.

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

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

We should have changed this when we switched to AppCompat theme.

BUG=None
R=tedchoc@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/1f95254..ffba57d

TBR=lushnikov@chromium.org,vsevik@chromium.org,dglazkov@chromium.org,beverloo@chromium.org

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

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

BUG=442323
TBR=tsepez@chromium.org

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

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

With the NG trybots using the buildbot value, browser_tests' sharding value regressed from the original 8 to 5 shards. The bots are now seeing more delays. Bump everything up to 10.

R=maruel@chromium.org

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

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

Then we require 3 sided patches instead of 2 sided.

R=jamesr

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

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

A collection of small fixes towards getting MacViews browser to build, including:
* Modal dialogs expect a NativeView parent.
* Add BrowserNonClientFrameViewFactoryMac.
* Keyboard component not available without Aura.

BUG=425229

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

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

BUG=None

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

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

BUG=439055
TEST=In Launcher, drag app to solitary folder on second page

In the case described, AppsGridView::EndDrag()'s call to MoveItemToFolder() makes a recursive call to AppsGridView::EndDrag(), which deletes drag_view_.  Hence the dereferencing NULL when we return to the top-level call.

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

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

Previously the extensions links were used.

NOTRY=true

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

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

window resizer

BUG=437125
TEST=MultiWindowResizeController.ClickOutside

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

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

The overflow menu icons previously didn't have any images because there isn't
a theme provider for the menu's window. Allow image cells to provide a different
theme provider so these can display properly.

BUG=429810

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

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

Add a minor pause between displaying a non-persistent and a persistent
notification to ensure that the two permission usage timestamps are
different.

BUG=442407

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

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

This is part of a series:
[1] This CL
[2] https://codereview.chromium.org/795153003/
[3] https://codereview.chromium.org/802393002/

BUG=442343

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

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

WebRTC 7897:7902
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/e7280c6..e8dbbf4

Libjingle 7896:7898
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/8cc6cb0..35f09c3

TBR=kjellander@chromium.org

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

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

Reland of https://codereview.chromium.org/805593002/
TBR=chrishenry@google.com
BUG=440101

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

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

Adds new histograms that measure the network errors that requests are
completing with when using the data reduction proxy, and also measure
the network error rates for all HTTP requests for comparison. Single out
main frame resource loads because most net errors that would occur due
the network being unusable with the data reduction proxy would occur on
main frame requests.

BUG=439589

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

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

Starting on a port to Windows. As the non-legacy path was added 8 months
ago, is it ok to remove the legacy one now?

R=bratell@opera.com, andrewhayden@chromium.org
BUG=441867

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

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

Now breaks down to the line level, and shows an annotated display
of the source file with the size cost of each line, as well as all
symbols that contribute to that size (can be many in the case of
templates).

Example output here:

https://dl.dropboxusercontent.com/u/116514/chrome.dll.html
https://dl.dropboxusercontent.com/u/116514/chrome_child.dll.html

Not really intended for loading remotely as they're very large,
but might eventually finish loading.

R=jam@chromium.org, mkosiba@chromium.org
BUG=441867

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

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

Added code to DeviceStatusCollector to populate new NetworkState fields.

BUG=430908

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

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

BUG=440939
R=navabi@chromium.org

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

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

This CL introduces a command line switch "--content-shell-host-window-size" to help the developers to specify the content_shell size for windowless ozone platforms like test, egltest, dri, caca.

Prior to this CL, the developer has to change the constants(kDefaultTestWindowWidthDip, kDefaultTestWindowHeightDip) in shell.cc to increase the content_shell resolution for above mentioned ozone platforms.

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

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

This replaces core X11 XKB on Ozone, providing a platform-independent
interface mapping (DomCode, EventFlags) to (DomKey, character)
and KeyboardCode, and a layout set/property interface equivalent
to ImeKeyboard.

BUG=430194

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

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

We only pass ValueState updates via IPC if the Gpu Service has
signalled that a Valuebuffer is subscribed to the respective target.

BUG=422978

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

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

BUG=420670

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

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

After https://codereview.chromium.org/802813002/

BUG=441856
R=spang
TEST=build

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

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

BUG=366145

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/ce1c886..e05fed0

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=bensong@google.com

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/5c1af99..1f95254

TBR=lushnikov@chromium.org,vsevik@chromium.org,dglazkov@chromium.org,beverloo@chromium.org

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

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

patch from issue 802973002 at patchset 1 (http://crrev.com/802973002#ps1)

BUG=
TBR=benm@chromium.org
add tbr for android_webview owner

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

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

BUG=428729

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

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

This CL effectively disables r301384, that provisionally plumbed
ImeCompositionRangeChanged from the renderer to the browser.

However, the character bounds is not actually used yet in the
browser process. Hence we shouldn't have turned this on until everything
becomes ready.

BUG=424866
TEST=Manually made sure that the browser process doesn't receive the event.

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

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

We were using a stale proguard config which meant that Release
builds were completely broken.
Turning proguard off till we fix this for real.

BUG=442348

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

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

Snappy was disabled for the WebView build to avoid introducing a new
build dependency but snappy has been added to the WebView build for
other purposes since then; we may as well re-enable it to remove a now
unnecessary difference between the downstream webview build and regular
builds of chromium for Android.

BUG=236780

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

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

The code currently excludes paste-and-go operations.  It should probably
also exclude paste+enter operations; these are effectively equivalent.

TODO before submitting: test interactively

BUG=
TBR=bauerb@chromium.org,rogerta@chromium.org
bauerb for change to chrome/browser/android/omnibox/autocomplete_controller_android.cc
rogerta for change to chrome/browser/rlz/rlz_unittest.cc

Committed: https://crrev.com/c281fb257d2acdd247b0692380d084863e2dd462
Cr-Commit-Position: refs/heads/master@{#308233}

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

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