GitLab

NPEvent::lParam is defined as uintptr_t which has same width with ULONG on Win32, but they are of different sizes on WIN64. uintptr_t is 8-byte long, while ULONG is still 4-byte long, so it corrupts a 64-bit pointer if casting it to a 32-bit type.

BUG=413535
TEST=square.html (attached in the bug), http://pbskids.org/video (it uses wmode="opaque")
R=ananta@chromium.org, bauerb@chromium.org

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

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

If RendererFreezer::SuspendImminent was called multiple times before it
had a chance to report readiness, it would post multiple tasks to do so
on the current message loop.  However the callback to report readiness
would be cleared after the first task ran and would cause a crash when
the next task tried to run it.  Fix this by not posting new tasks while
a callback is pending and just update the callback instead.

BUG=414396
Signed-off-by: Chirantan Ekbote <chirantan@chromium.org>

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

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

With the current sharding strategy (random), having smaller suites will reduce cycle time.
The Android bots will automatically pick up this config change. If we want to do the desktop bots too, that'd require a master restart.

BUG=396001
TEST=None.
R=tonyg

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

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

R=jam@chromium.org
BUG=406457

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

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

This pulls in the following Native Client changes:

r13747: (dschuff) Fix toolchain build and sandboxed translation tests on FYI bots
r13748: (thakis) Pass -std=gnu++0x in build_nexe.py.

BUG=none
TEST=browser_tests and nacl_integration
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_rel_precise32,linux_arm_cross_compile,linux_nacl_sdk,linux_chromium_dbg

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

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

which prevent grouping mechanism in MergeNetworkList from working.

The end result is that each Network after MergeNetworkList contains only 1 ip address. With this change, the grouping will happen correctly. WebRTC has logic to only retrieve single IP from each network for connectivity check already.

This CL is a dup of https://codereview.chromium.org/536133003/ which was created under the wrong identity.
BUG=

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

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

Remove stale ChromiumAsyncUrlRequest.java as it is replaced by CronetUrlRequest.java as of https://codereview.chromium.org/520093002/.

BUG=409926
TBR=mmenke@chromium.org

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

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

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg

BUG=

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

When changing from software mirroring mode to sinlge display mode, it
is possible there is no need to update |displays_| and we early out
UpdateDisplays(). But we still want to run the PostDisplayConfigurationChange()
cause there are some clients need to act on this, e.g.
TouchTransformerController needs to adjust the TouchTransformer when
switching from dual displays to single display.

BUG=chrome-os-partner:31868
TEST=tested on Big, after existing software mirroring mode, the touch location
     transformation is still correct.

TBR=oshima@chromium.org

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

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

Previously, mojo_variables.gypi hard-coded a DEPTH of 1, which meant that only
GYP files that were directly in folders in the root could use it. After this
CL, GYP files at any depth of the tree can use it.

R=jamesr@chromium.org

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

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

https://chromium.googlesource.com/chromium/blink/+log/01025b523bac1a59fa91a10d5d49f969ed24000d..1d4eb25ceba65e3e78786bce1251dc248d20af19
TBR=loislo@chromium.org,dpranke@chromium.org

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

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

https://skia.googlesource.com/skia/+log/595aa05efcb504e85358b8d328ac4a9fa1c46e2e..f0ddf33f1954489d45e4f2d9c8712eac60539c65

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

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This parameter is not used with impl-side painting, and blink is the
only embedder of blink that sets this value.

Since blink is always impl-side painting now, we can just remove it.

R=nduca, vmpstr
BUG=413479

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

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

- Add code to add/remove/get cryptohome keys for Easy sign-in;
- Add an EasyUnlockKeyManager to wrap the operations and provide an API;
- Re-create crypthome keys with pairing data in user prefs on user sign-in;

BUG=394640,394641

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

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

Updates https://codereview.chromium.org/543493002 for latest version
if internet_detail.js

BUG=393873
R=vitalyp@chromium.org

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

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

https://codereview.chromium.org/117933003/

The speculative resource prefetching code was experimental code developed by
shishir@. He found that it has little improvement on desktop Chrome (win). We
though this should be beneficial to mobile browsers. After discussing with
tburkard@ and kenjibaheux@, we decided to bring the code back and do more
analysis on mobile devices. Reverting the patchset to re-add the code is the
first step.

The following design doc has discussed all related approaches and action items.
https://docs.google.com/a/google.com/document/d/1ie3hu-zNNXvmTXm3aJAtKUGOh6nZfbNjA0aZE1bzzIg/edit?usp=sharing

BUG=408399, 405690

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

- Fixed AutoConnect, which is stored in each network type's subdictionary.
- Added a Cellular.AutoConnect property to ONC.
- Fixed VPN username for L2TP-IPsec, which is stored in 'L2TP'.
- Removed reading Wimax properties from ONC, as these are not yet supported.

BUG=412807

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

GpuCommandBufferMsg_SetLatencyInfo is used to send current frame's latencyinfo
to gpu. We can piggyback the latencyinfo in GpuCommandBufferMsg_AsyncFlush so
eliminate the extra IPC.

BUG=404650
TEST=check trace that now GLRenderer::SwapBuffers only sends 2 IPC messages,
     i.e. AsyncFlush and Echo. And LatencyInfo tracking is still working.

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

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

BUG=None
TBR=jochen@chromium.org

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

This patch was generated by running the rewrite_scoped_refptr clang tool
on a ChromeOS build.

BUG=110610

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

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

Cleanup: Reorganize extensions renderer build files so we only have to list each file once, rather than two if they are excluded on Android.

Remove all native handlers from the Android build while we are at it.

BUG=402728

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

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

net: another batch of HSTS preloads.
Cr-Commit-Position: refs/heads/master@{#294886}

This change removes the signalling of a new media segment when an audio
frame is partially front-trimmed. This allows other muxed streams, like
video, to not necessarily continue with a keyframe as the next frame
processed (unless new media segment has otherwise been signalled).

BUG=408216
R=dalecurtis@chromium.org
TEST=no media_unittest or mediasource layout test regression

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

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

This prepares for the landing of
  https://codereview.chromium.org/522783002/

which now requires a three-sided change due to changes in how Blink accesses
private script resources.

Part 1: https://codereview.chromium.org/570863002/

BUG=364716

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

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

This change refactors the existing support for cross-process iframe
accessibility and extends it to make guest browser plugins, for example
the <webview> element in apps, accessible too.

In this change, a new class, FrameAccessibility, manages all links
from one frame's accessibility tree to either a child iframe's tree,
or a guest web contents' tree. This is cleaner than storing ids in
BrowserAccessibility nodes - now the accessibility tree just needs a
single bit indicating which nodes in one tree are acting as a host of
another tree.

FrameAccessibility doesn't try to be efficient yet, it scans its list
for every operation - the goal is for it to be simple and safe first.
Hash maps could make it much faster later if needed.

None of the APIs needed to test this are available outside of content
yet. Once http://crbug.com/396137 is finished we'll have a clean way
to test this. In the meantime, this can be tested by visiting
chrome://accessibility on Windows or Mac, and observing that the
accessibility tree for an app includes all nodes within <webview>
elements now. Also tested with VoiceOver on Mac; there are some bugs
but the <webview> is definitely part of the accessibility tree now.

BUG=330307,368298

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

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

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

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

https://skia.googlesource.com/skia/+log/a63d5df455e5fb32ac995f753709893221de6147..595aa05efcb504e85358b8d328ac4a9fa1c46e2e

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

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

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

The authentication is attempted when establishing a secure connection with the
remote device.

BUG=411043
TEST=none
NOTRY=true
R=jwd@chromium.org

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

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

Datatype is responsible for writing attachments to AttachmentStore.
GenericChangeProcessor doesn't need attachment data in SyncData, only
list of attachment ids.

This change removes AttachmentList from SyncData and fixes corresponding
dependencies.

BUG=
R=maniscalco@chromium.org

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

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

If a view has a ton of children (say > 5000) with the majority hidden
then we spend a lot of unecessary time in View::UpdateRootBounds on
every paint.

BUG=409126
TEST=none, see bug
R=luken@chromium.org

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

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