GitLab

BUG=103483,104413
TEST=BrowserInitTest.OpenAppShortcutPanel, PanelAppBrowserTest.OpenAppInPanel

Review URL: http://codereview.chromium.org/8572022

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

Landed at r109114, Reverted at r109142

Make it possible to enable/disable specific ppapi tests. Migrate PostMessage tests.

The testcase attribute now can include a 'filter'. If it's omitted, everything works the same as before. This way we can migrate tests over bit-by-bit if we want to. We can also still run the tests manually the same way as before.

This only runs PostMessage testss the new way, and re-enables all oop PostMessage tests that pass on Windows. I can do the other tests in this CL if desired, but it might be easier to land in a few pieces.

BUG=102885
TEST=N/A
TBR=dmichael@chromium.org

Review URL: http://codereview.chromium.org/8536031

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

BUG=97261
TEST=Manual


Review URL: http://codereview.chromium.org/8572002

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

BUG=None
TEST=ran 'python watchlists.py chrome/browser/chromeos/xinput_hierarchy_changed_event_listener.cc'


Review URL: http://codereview.chromium.org/8460012

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

BUG=104380
TEST=n/a
TBR=jam@chromium.org


Review URL: http://codereview.chromium.org/8572033

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

BUG=104419
TEST=none
Review URL: http://codereview.chromium.org/8573032

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

Passes with both the browser and WebKit compositor.

BUG=None
TEST=compositor_unittests

Review URL: http://codereview.chromium.org/8538018

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

Also fix wrong sandbox options for broker process on Windows and Mac.

BUG=none
TEST=none


Review URL: http://codereview.chromium.org/8400024

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

TBR=pkasting
BUG=104307,104124


Review URL: http://codereview.chromium.org/8572027

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

This is a workaround for crbug.com/93530; caused by crrev.com/84823.
Windows creates a WM_PAINT storm without validation; even on empty regions.

BUG=93530
TEST=Issue does not repro; no regressions.

Review URL: http://codereview.chromium.org/8568016

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

BUG=101600, 94925
TEST=none
TBR=mnissler

Review URL: http://codereview.chromium.org/8573021

TBR=thakis@chromium.org
Review URL: http://codereview.chromium.org/8568039

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

Rebaseline expectations for perf improvements.  I had been updating for these as I saw them on the console, but didn't look at the waterfall until now, thus missed a bunch.  Here they all are for your enjoyment.

vista-release-dual-core/intl1:
http://build.chromium.org/f/chromium/perf/vista-release-dual-core/intl1/report.html?history=150&rev=110217

vista-release-dual-core/intl2:
http://build.chromium.org/f/chromium/perf/vista-release-dual-core/intl2/report.html?history=150&rev=110217

vista-release-dual-core/dom_perf:
http://build.chromium.org/f/chromium/perf/vista-release-dual-core/dom_perf/report.html?history=150&rev=110217

xp-release-dual-core/dom_perf:
http://build.chromium.org/f/chromium/perf/xp-release-dual-core/dom_perf/report.html?history=150&rev=110217

xp-release-single-core/intl1:
http://build.chromium.org/f/chromium/perf/xp-release-single-core/intl1/report.html?history=150&rev=110217

vista-release-single-core/intl1:
http://build.chromium.org/f/chromium/perf/vista-release-single-core/intl1/report.html?history=150&rev=110217

vista-release-single-core/intl2:
http://build.chromium.org/f/chromium/perf/vista-release-single-core/intl2/report.html?history=150&rev=110217

mac-release-10.5/v8_benchmark:
http://build.chromium.org/f/chromium/perf/mac-release-10.5/v8_benchmark/report.html?history=150&rev=110217

mac-release-10.5/dom_perf:
http://build.chromium.org/f/chromium/perf/mac-release-10.5/dom_perf/report.html?history=150&rev=110217

mac-release-10.6/intl1:
http://build.chromium.org/f/chromium/perf/mac-release-10.6/intl1/report.html?history=150&rev=110217

mac-release-10.6/intl2:
http://build.chromium.org/f/chromium/perf/mac-release-10.6/intl2/report.html?history=150&rev=110217

TBR=cmp@chromium.org
Review URL: http://codereview.chromium.org/8571021

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

class contains almost all chrome specific details from TabContentsViewGtk,
leaving TabContentsViewGtk as a pure content/ class (soon to be moved out of
chrome/).

Why subclass instead of composing? First, because the X vs ChromeX is fairly
common already, but mostly because large chunks of the gtk ui code assume
there's a single widget that can be switched in and out on tab showing and that
this is TabContentsViewGtk::GetNativeView(). (This also means it is easy to
address the other join points, like sad tabs or menus.)

BUG=none
TEST=none


Review URL: http://codereview.chromium.org/8344061

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

BUG=101600, 94925
TEST=none
TBR=mnissler

Review URL: http://codereview.chromium.org/8573021

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

BUG=100879

Review URL: http://codereview.chromium.org/8567019

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

BUG=None
TEST=None

Review URL: http://codereview.chromium.org/8568010

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

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

BUG=104314

Review URL: http://codereview.chromium.org/8568021

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

BUG=94103
TEST=unittest
Review URL: http://codereview.chromium.org/8568032

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

This fixes a bug where a client needed to guarantee a message filter was in
place before any messages were received.
It also follows the style of not having constructors that do complex
initialization.
BUG=102894
TEST=none


Review URL: http://codereview.chromium.org/8417054

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

likely more cleanup that can be done here, but this is a start.


TBR=phajdan.jr@chromium.org
R=phajdan.jr@chromium.org
BUG=104360
TEST=none


Review URL: http://codereview.chromium.org/8520025

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

BUG=None
TEST=PanelBrowserTest.AutoResize, CreateWithExistingContents, OnBeforeUnloadOnClose

Review URL: http://codereview.chromium.org/8568034

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

BUG=none
TEST=none

Review URL: http://codereview.chromium.org/8533030

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

BUG=
TEST=


Review URL: http://codereview.chromium.org/8568012

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

This is needed to fix some issues in tests exposed by the WebKit compositor. The
problem is that sometimes during the teardown paths, some layers have stale a
pointer to the compositor that has already been destroyed. The WebKit layer
(rightfully) calls ScheduleDraw when the layer hierarchy is changed, exposing
the issue.

We now always walk back to the root layer to find the compositor, and reset the
pointer when the compositor's root changes (or it gets destroyed).

BUG=99524
TEST=views_unittest, aura_unittest, compositor_unittests with (and without) use_webkit_compositor=1


Review URL: http://codereview.chromium.org/8510076

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

BUG=none
TEST=none
TBR=thestig

Review URL: http://codereview.chromium.org/8468030

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

Copy server pieces to build output dir.
Update ppapi_uitests.cc to run server from output dir.
Add test to ppapi_uitests, update dependecies.
Update test_sever to support a fully qualified path.

BUG= http://code.google.com/p/chromium/issues/detail?id=96782
BUG= http://code.google.com/p/chromium/issues/detail?id=103690
TEST= try (ui_tests --gtest_filter="PPAPI*.*")
Review URL: http://codereview.chromium.org/8539019

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

BUG=104403
TEST=none
Review URL: http://codereview.chromium.org/8574028

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

version_extension_ in MetricsLogBase was only used in the MetricsLog
subclass, so move it to there.

BUG=101600,94925
TEST=none


Review URL: http://codereview.chromium.org/8468018

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

BUG=104314
TEST=no change

Review URL: http://codereview.chromium.org/8520018

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

than needed.

BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8540027

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

This will mean that when things like cancel are done on downloads resulting
from a Save Page As ..., chrome will not crash.  They also won't do anything,
but that's the previous (broken :-{) behavior.

BUG=103590
R=cbentzel@chromium.org


Review URL: http://codereview.chromium.org/8519008

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

Null time values can appear if the profiler is
not ACTIVE, and the Now() function returns a Null
value (to avoid wasting time and calling the OS Time).

r=rtenneti
Review URL: http://codereview.chromium.org/8573017

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

BUG=None
TEST=Manual

Review URL: http://codereview.chromium.org/8568023

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

BUG=104031


Review URL: http://codereview.chromium.org/8533015

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

Fix a breakage to about:profiler from r110207. This change was actually part of my original codereview that was approved, but I lost it while synching my svn client :(

TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/8520029

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

Don't pollute the namespace with defines from C header files and forward
declare WaylandEvent.

BUG=102903
TEST=compiles

Change-Id: I5cd50c04361d4d053bdf8c193071a4c7808c51d7

R=oshima@chromium.org,dnicoara@chromium.org,mark@chromium.org


Review URL: http://codereview.chromium.org/8572030

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

BUG=104314
TEST=


Review URL: http://codereview.chromium.org/8468021

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

Also get rid of flushed_metahandles since it serves exactly zero purpose :)

BUG=87122
TEST=none

Review URL: http://codereview.chromium.org/8565035

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

Complete the rename from about:tracking2 --> about:profiler by changing the implementation code to always reference "profiler" rather than "tracking".

BUG=100992
Review URL: http://codereview.chromium.org/8520016

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