GitLab

This updates actions.xml to account for the new extended reporting option.

BUG=383866
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277803 0039d316-1c4b-4281-b951-d872f2087c98

Generated using
src/tools/metrics/histograms/update_use_counter_feature_enum.py

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277802 0039d316-1c4b-4281-b951-d872f2087c98

Previously, we would use the X-coordinate of the left edge of the dragged tabs,
and check whether it fell within the left or right half of each tab in the
strip.

This had a couple problems.  First, because tabs are wider than they appear (due
to a significant portion of the tab being the outside pieces that are flush or
nearly-flush with the top of the toolbar), the true left edge of the dragged
region is "to the left of" where the user thinks the drag point ought to be, and
this discrepancy becomes noticeable as tabs get narrow, with the insertion
sometimes seeming to happen a tab to the left of where it "ought to".  Instead,
we now use a (hardcoded) 16-px offset into the drag region, which is much closer
to where the user perceives the "start" of the region to be.

Second, again because tabs are wider than they appear, the right half of one tab
can overlap with the next tab, indeed sometimes even overlapping with the right
half of that next tab, so the insertion point can be calculated in a way that
appears to be off by a tab or so.  Instead, we now simply use the regions
between successive tab midpoints to calculate the desired insertion index.

The result of this is that the apparent "slop zone" between tabs gets slightly
larger, and it takes a slightly further drag to drag to the very beginning of
the tabstrip; but most noticeably, when dragging tabs that are very narrow (e.g.
in tabstrip overflow), dragging feels much more predictable and less like the
instant you grab a set of tabs, they get moved to somewhere strange.

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277801 0039d316-1c4b-4281-b951-d872f2087c98

BUG=384575

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277800 0039d316-1c4b-4281-b951-d872f2087c98

BUG=372306

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277799 0039d316-1c4b-4281-b951-d872f2087c98

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277798 0039d316-1c4b-4281-b951-d872f2087c98

The tool-bar is being phased out as part of the apps v2 work, but as
part of the transition, the functionality it provides needs to be shared
between it and the window frame. Step one is to disentangle some of the
event handling code from client_session.js and toolbar.js.

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277797 0039d316-1c4b-4281-b951-d872f2087c98

This class isn't used in multithreaded fashion anymore.

BUG=NONE

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277796 0039d316-1c4b-4281-b951-d872f2087c98

Histogram names are case-sensitive. Histograms.xml have the prerender source as "instant" instead of "Instant".

BUG=none
TEST=none
R=asvitkine@chromium.org
TBR=tburkard@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277795 0039d316-1c4b-4281-b951-d872f2087c98

BUG=375155
TEST=WebRTC and WebSpeech demos

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277794 0039d316-1c4b-4281-b951-d872f2087c98

BUG=288859

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277793 0039d316-1c4b-4281-b951-d872f2087c98

This CL makes 'Disconnect from Google account' dialog show the correct message in all usage scenarios. Further, the cancel button is made the default in the dialog.

BUG=374715,374723

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277792 0039d316-1c4b-4281-b951-d872f2087c98

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277791 0039d316-1c4b-4281-b951-d872f2087c98

BUG=385318
TEST=test manually that new finch groups behave as expected.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277790 0039d316-1c4b-4281-b951-d872f2087c98

This is the 1st step towards removing sign-in enforcement for GCM.

We also remove the logic to pass account IDs to check-in request
since it seems to work fine without them and TokenService::GetAccounts
returns the empty list.

BUG=384041
TEST=existing and new tests
R=bartfab@chromium.org, fgorski@chromium.org, zea@chromium.org
TBR=jochen@chromium.org, rogerta@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277789 0039d316-1c4b-4281-b951-d872f2087c98

Make the base class QuadSink concrete instead of pure virtual, and
remove QuadCuller class. Testing class MockQuadCuller is still derived
from QuadSink, which also manipulates its own MockOcclusionTracker.

This CL is part of clean up QuadSink. Next step would to plum LayerImpl
through so QuadSink will no longer need to hold that variable, in order
to split up QuadSink into just RenderPass and OcclusionTracker.

This CL follows 302603006 and 306683002.

BUG=344962
TEST=cc_unittests

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277788 0039d316-1c4b-4281-b951-d872f2087c98

The three tests being flaky (testContentUrlAccessWithTwoViews, testFileUrlAccessWithTwoViews and testCacheModeWithTwoViews) are all implicitly rely on the fact that when a page load error happens, onPageFinished is only called once. This behaviour had been broken since about M33, but due to happy timing, it just didn't cause the tests to fail.

The solution is to filter onPageFinished callbacks on AwContentsClient side, since the flow of passing the URL of the error page appears perfectly normal in the context of Chrome.

Other changes:

  -- testContentUrlAccessWithTwoViews was in fact incorrect, as it wasn't expecting an error in case when access to content: URLs is blocked;

  -- modified ClientOnPageFinishedTest.testOnPageFinishedCalledAfterError to catch situations when onPageFinished / onReceivedError is called twice, to avoid future regressions;

  -- added ClientOnPageStartedTest to catch similar problems with onPageStarted.

BUG=370950,371983

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277787 0039d316-1c4b-4281-b951-d872f2087c98

This change ensures that the extension that generated a key with enterprise.platformKeys can use that key at most once for signing data. Any attempt to sign data afterwards with the same key will fail.

BUG=382983

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277784 0039d316-1c4b-4281-b951-d872f2087c98

This patch adds trace links to chrome://inspect if you add the
"tracing" parameter to chrome://inspect. Clicking on the trace link
opens up chrome://tracing.

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277781 0039d316-1c4b-4281-b951-d872f2087c98

To ease failure diagnosis.

BUG=385421
R=gab@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277780 0039d316-1c4b-4281-b951-d872f2087c98

We'll want this to be able to implement efficient, base/logging.h-like
macros (with the similar behavior -- i.e., don't evaluate the stream if
it's not going to be logged).

R=darin@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277779 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277777 0039d316-1c4b-4281-b951-d872f2087c98

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=176255:176311&mode=html
TBR=schenney@chromium.org,jamesr@chromium.org
BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277776 0039d316-1c4b-4281-b951-d872f2087c98

ViewTreeNode*->Node*
ViewManagerSynchcronizer->ViewManagerClientImpl

R=sky@chromium.org
TBR=sky@chromium.org
http://crbug.com/384443

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277775 0039d316-1c4b-4281-b951-d872f2087c98

When BeginFrame scheduling is enabled, the browser compositor
automatically adjusts the deadline it passes down to the renderer to
account for its own draw time. Make sure we don't also subtract the
estimated draw time in the renderer.

BUG=359566

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277774 0039d316-1c4b-4281-b951-d872f2087c98

According to crbug.com/307827 - the code that used media_galleries_handlers has been removed.

BUG=NONE
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277773 0039d316-1c4b-4281-b951-d872f2087c98

JSONReader produces base::Value objects that share a string buffer. See comment at the JSON_DETACHABLE_CHILDREN option.
Since Remove on a child node was used, this potentially lead to use-after-free. 

BUG=NONE

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277772 0039d316-1c4b-4281-b951-d872f2087c98

Should be below accounts list, but above list of other profiles.

BUG=372812,372381

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277771 0039d316-1c4b-4281-b951-d872f2087c98

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277770 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277762 0039d316-1c4b-4281-b951-d872f2087c98

R=jam@chromium.org, jochen@chromium.org, jschuh@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277761 0039d316-1c4b-4281-b951-d872f2087c98

BUG=162827

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277759 0039d316-1c4b-4281-b951-d872f2087c98

BUG=367221

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277757 0039d316-1c4b-4281-b951-d872f2087c98

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277756 0039d316-1c4b-4281-b951-d872f2087c98

The messages will now go trough RF/RFH.
This is in order to make screen orientation lock Frame specific
instead of global to Chromium. The next step is to change the provider
accordingly.

BUG=162827

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=277321

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277755 0039d316-1c4b-4281-b951-d872f2087c98

Failed test:
http://build.chromium.org/p/chromium.mac/builders/Mac%2010.6%20Tests%20%28dbg%29%283%29/builds/50667/steps/interactive_ui_tests/logs/stdio

The new test appears to be timing out on the bots.

> [Mac] Add interactive App Shim test.
> 
> This test creates shims in the user data dir and actually starts them up and
> expects them to connect to the IPC socket.
> 
> BUG=168080
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276368
> 
> Review URL: https://codereview.chromium.org/316493002

TBR=jackhou@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277754 0039d316-1c4b-4281-b951-d872f2087c98

BUG=372388
TEST=N/A
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277753 0039d316-1c4b-4281-b951-d872f2087c98

Looks like a 2x multiplier might not be enough for browser_tests. Let's try 3x.
We'll probably want to do the same for TSan once we start running browser_tests
under TSan.

BUG=178409
TBR=phajdan.jr@chromium.org
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277751 0039d316-1c4b-4281-b951-d872f2087c98

Followup to https://codereview.chromium.org/316863002/

This CL changes:
- c/b/managed_mode/ to c/b/supervised_user/
- "ManagedMode"/"ManagedUser" to "SupervisedUser" in c/b/supervised_user/

Still missing:
- Some stuff outside of c/b/supervised_user/, mostly (but not only) c/b/chromeos/login/managed/
- JavaScript
- Resource names

The remaining things will come in followup CLs.

TBR=nkostylev@chromium.org (c/b/chromeos)
TBR=noms@chromium.org (c/b/profiles)
TBR=thakis@chromium.org (rest of c/)

All the TBRs are just trivial renames.

BUG=385113

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277750 0039d316-1c4b-4281-b951-d872f2087c98

This makes the Safe Browsing interstitial unit & browser tests work for both the V2 and V3 versions. For the unit tests, I did this by using typed tests. Typed tests aren't supported for browser tests, so for the browser tests I moved the tests into methods that could be invoked twice.

Also includes a small bugfix in a string that was causing a failure.

BUG=381260

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277749 0039d316-1c4b-4281-b951-d872f2087c98