GitLab

HTML5FS (PPAPI) does not provide an INO so it is impossible to determine
a files uniqueness.  In addition, node information does not persist in
memory since nodes could be transparently destroyed from JavaScript, thus
creating leaks.  Because of this the current stack based INO allocation
causes sequentially accesed file handles to report the same INO.

HTML5FS (including media galleries) does not traverse links.  This implies
that all paths normalized to the mount are unique.  We use this property
to generate a 64 bit hash.

R=binji@chromium.org
BUG=414938

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

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

Revert of Changes NineImagePainter to snap to (enclosed) pixel boundaries (patchset #2 id:20001 of https://codereview.chromium.org/604463003/)

Reason for revert:
I'm reverting this as there are two issues:
1. Translate isn't being set correctly.
2. Even with 1 fixed there are problems with scrollbars. I'll investigate after the revert.

Original issue's description:
> Changes NineImagePainter to snap to (enclosed) pixel boundaries
>
> Otherwise the sides may be clipped out.
>
> BUG=417493
> TEST=see bug
> R=ananta@chromium.org
>
> Committed: https://crrev.com/d1ab0241ee29c70bd08531d1f038964664b124b6
> Cr-Commit-Position: refs/heads/master@{#296608}

TBR=ananta@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=417493

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

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

To support CDM_6, make the following changes:
- add SetServerCertificate
- add GetUsableKeyIds
- rename ReleaseSession to CloseSession
- add RemoveSession
- add SessionKeysChange event
- add SessionExpirationChange event

This gets the new functionality up to the blink boundary. Changes to
use these new interfaces in blink in a future CL.

For backwards compatibility with existing prefixed EME code, calls
to CancelKeyRequest() call RemoveSession() instead of CloseSession().

BUG=358271,417481
TEST=existing EME tests still pass + manual testing

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

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

R=darin@chromium.org

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

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

BUG=417888
R=keescook@google.com
TBR=rsesek

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

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

I broke the uiautomator tests with my change to instrumentation test
running in https://codereview.chromium.org/558883003/. The revised
implementation never called _RunTest, which the uiautomator test runner
overrides to run its tests. As a result, we were trying to run the
uiautomator tests with 'am instrument', which (obviously) doesn't work.

This patch revises the implementation of the instrumentation test runner
s.t. it does call _RunTest again.

BUG=417492

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

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

BUG=

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

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

Split off from cl 490443002 because for some reason this test seems to
fail with a NaCl error on one of the trybots. Let's try to land it
separately.

BUG=404470

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

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

- In Canonical Fullscreen, the toolbar/tabstrip now slide over the content when
the AppKit menu bar is revealed. This prevents a series of fast resizes of the
content view, which is janky.
- Adjust the z-ordering of the infobar so that it shows in front of the
bookmark bar and toolbar in Canonical Fullscreen.
- Removed method -isInFullscreenWithOmniboxSliding, as it has the same behavior
as -isInAnyFullscreenMode.

BUG=413210

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

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

Revert of Restored disable print preview policy. (patchset #8 id:140001 of https://codereview.chromium.org/597933002/)

Reason for revert:
Noticed a bug in render_view_context_menu.cc change

Original issue's description:
> Restored disable print preview policy.
> Not exact revert of https://codereview.chromium.org/488853002
>
> BUG=374321,416396
>
> Committed: https://crrev.com/15daa893f50daebf33ccf06ba67d74788700e495
> Cr-Commit-Position: refs/heads/master@{#296751}

TBR=thestig@chromium.org,joaodasilva@chromium.org,pastarmovj@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=374321,416396

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

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

BUG=415166

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

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

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/7214955..f1db071

TBR=ager@chromium.org,zmo@chromium.org

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

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

BUG=chromedriver:908

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

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

The problem is that calling hide/cancel on a popup is async.

With two popups, you would get

Previously:
SHOW A
HIDE A
SHOW B
NOTIFY SELECTION A
HIDE B
NOTIFY SELECTION B

When notifying the selection of A in the above scenario, it was
clearing the frame pointer (and actually updating the wrong popup).
Then when hiding the second popup, it's reference was actually gone
already.

Fix this by making the call to hide sync instead of async.

BUG=416354

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

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

We won't launch this feature for M39, so disable public opt-in flag.

BUG=416664

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

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

I missed this one when I was reformatting the controlled settings.

BUG=417624

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

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

It is impossible to whitelist an extension which is note a component, when the
api is restricted to components. Since we need to whitelist such regular
extension, this patch removes the location restriction and whitelists all
clients of this API.

Along the way, id testing extensions using this api has been changed to a new
one, since it was reused with other tests not related to the api.

TEST=browser_tests: *FileBrowser*, *FileManager*
BUG=None

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

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

Move initializeChildFrame from RenderFrameImpl to RenderFrameProxy.  Replace RenderFrameImpl::OnSwapOut's call to setIsRemote with WebRemoteFrame::initializeFromFrame that was introduced in part 1 of this change (https://codereview.chromium.org/591413004/)

This will be followed by another CL that will remove setIsRemote on the blink side.

BUG=416102

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

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

The "snionly" tag only applies to preloaded values and only affects
people who are forcing SSLv3 on the command line. (We no longer have the
option in the preferences to disable TLS and the preference has been
renamed so even those who might have set it in the past shouldn't have
it now).

It also complicates pending work to reduce the size of the preload data.

BUG=102779
R=eroman@chromium.org, rsleevi@chromium.org

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

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

It doesn't work, and it is no longer used.

BUG=416208
R=cpu@chromium.org, jam@chromium.org

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

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

BUG=416722
R=gab@chromium.org, robertshield@chromium.org

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

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

It's possible to get a copy of an answer from previous matches and get the
same answer attached to a similar server-provided answer.  In the future,
we may decide that we want to have different answers attached to multiple
suggestions, but the current assumption is that there should only ever be
one suggestion with an answer.

BUG=

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

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

BUG=

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

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

BUG=325045

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

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

Exclude more targets from openssl build.

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

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

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

Brings in the following changes:

commit 87b96db4268293187d7cf741907a6d5d1d8080e0
Author: agl@chromium.org <agl@chromium.org>
Date:   Thu Sep 25 20:28:09 2014 +0000

    Update to NSS 3.16.7.

    This contains a fix for the RSA signature forgery bug (CVE-2014-1568):
    https://www.mozilla.org/security/announce/2014/mfsa2014-73.html

    Chrome and ChromeOS have already released updates containing this fix:
      http://googlechromereleases.blogspot.com/2014/09/stable-channel-update_24.html
      http://googlechromereleases.blogspot.com/2014/09/stable-channel-update-for-chrome-os_24.html

    https://codereview.appspot.com/142600043/

    (This the SVN version of the git change, referenced above. It seems that the
    NSS git is still a mirror from this SVN repo and thus one cannot commit to it
    directly.)

    git-svn-id: http://src.chromium.org/svn/trunk/deps/third_party/nss@292145 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

BUG=414124

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

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

This brings in the following changes to the addin:
r1578 Add default compiler include paths to visual studio
r1577 Cleanup create_package.py
r1576 Fix several issues with debugging PPAPI plugins
r1575 Update versions used for testing the addin
r1574 Only skip uploading of addin if the file already exists on google storage.

BUG= https://code.google.com/p/chromium/issues/detail?id=179121
R=binji@chromium.org

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

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

BUG=417892
TBR=fsamuel@chromium.org

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

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

Without this, Chromecast apps will not have time to handle
window.unload events when user switches to a new app.

R=lcwu@chromium.org,byungchul@chromium.org
BUG=400876

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

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

This reverts commit 3d148e7d.

BUG=417597
TBR=bauerb@chromium.org,dhnishi@chromium.org,cpu@chromium.org

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

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

Use it at appropriate places.
Also add corresponding UMA histogram value.

BUG=416233

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

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

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

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

Blocking renderer->plugin messages can be interrupted by any message
from the plugin->renderer (even async ones). So while handline a blocking
message, such as HandleInputEvent or HandleBlockingMessage, it's currently
possible to re-enter JavaScript. This patch makes that impossible by
queueing up Plugin->Renderer messages sent via PPB_Messaging::PostMessage
while any renderer->plugin sync message is on the stack.

BUG=384528

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

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

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

Bunch of includes are actually unnecessary, simply removed them.

For the fullscreen state, I believe FullscreenNotificationBlocker
can handle it correctly. MessageCenterNotificationManager doesn't
have to handle it anymore.

BUG=None
R=dewittj@chromium.org
TEST=manually

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

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

Previously 4096 bytes write buffer was used for XMPP socket. Problem is
that ChromeAsyncSocket stops writing when the buffer is full and
talk::XmppClient ignores this error, as result random chunks of data may
be lost. This CL increses buffer size to 64k - same value that's used in
notifier::XmppConnection.
This is essentially a temporary workaround until the problem is fixed
in jingle::ChromeAsyncSocket or talk::XmppClient

BUG=417336

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

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

Adding tracking to verify the theory that jankiness of ExtensionMessageFilter::OnExtensionAddListener is because of the observer invocation.

BUG=401560, 417106

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

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

We still need to finish updating the extensions to use these translations.

BUG=416983
TBR=plundblad

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

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

The common string descriptors: iManufacturer, iProduct and iSerialNumber
should be accessible without opening the device. On Linux these can be
read out of sysfs without having access to the usbfs device node. This
is critical on Chrome OS because otherwise the permission broker needs
to be asked for permission to access the device. On other platforms we
fall back to opening the device temporarily. This will stop being the
case on OS X when libusb is no longer used and on Windows this will be
part of the initial enumeration process.

BUG=
TBR=dgozman@chromium.org

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

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

+ Correct the layout and size of the offline icon when getting a DNS_PROBE_FINISHED_NO_INTERNET error
+ Delay AudioContext initialising until required to reduce CPU usage.

BUG=417614

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

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