GitLab

The in-browser thumbnailing does not work if
--force-compositing-mode is supplied. I don't know what would be the right way
to fix this. For now, we should just disable the in-browser thumbnailing,
until we have the right fix.

BUG=chromium-os:19731

The last valgrind error was fixed by r87590.

BUG=65936
TEST=confirm that thumbnails in the new tab page are updated properly

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

TBR=satorux@chromium.org

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

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

Apparently WebKit sends the update for every layout, even if nothing has changed.
Review URL: http://codereview.chromium.org/7761005

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

RenderWidgetHostViewWin::ReparentWindow should call RemovePropW if kNativeWindowClassFilterProp is set.

BUG=94402
TEST=None.
Review URL: http://codereview.chromium.org/7757004

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

BUG=88954


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

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

This involves introducing the following macros:

  PPAPI_PROXY_EXPORT   - for symbols exported from ppapi/proxy
  PPAPI_SHARED_EXPORT  - for symbols exported from ppapi/shared_impl
  PPAPI_THUNK_EXPORT   - for symbols exported from ppapi/thunk

NOTE: shared_impl and thunk are still linked together, but I thought
it was cleaner to give thunk its own macro.

R=brettw@chromium.org
Review URL: http://codereview.chromium.org/7687005

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

NaCl PPAPI Proxy: wrap up with crash detection. Clean-up handling code to skip remote shutdown calls when the nexe is known to be dead. Add a test for crashing on other than the main thread, which depending on thread timing might happen when the main thread is servicing a PPP call or waiting for the next one. Add another test that will fail on a CHECK for an unsupported Pepper call off the main thread. 

BUG= http://code.google.com/p/nativeclient/issues/detail?id=1780, http://code.google.com/p/nativeclient/issues/detail?id=2105, http://code.google.com/p/nativeclient/issues/detail?id=1682 
TEST=scons run_ppapi_crash_browser_test
Review URL: http://codereview.chromium.org/7741036

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

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

```---------------------------------------------------------------------
r828 | mark@chromium.org | 2011-08-26 18:29:33 -0400 (Fri, 26 Aug 2011) | 8 lines

Fix a Breakpad crash during teardown when USE_PROTECTED_ALLOCATIONS is in
effect.

BUG=none
TEST=Apple Crash Reporter logs from processes in which Breakpad handles the
     crash should point the finger at the actual crash source, not the
     Breakpad thread's attempt to write to unwritable memory.
Review URL: http://breakpad.appspot.com/301001
```

---------------------------------------------------------------------
r827 | mark@chromium.org | 2011-08-26 17:37:59 -0400 (Fri, 26 Aug 2011) | 5 lines

Add missing (parentehses.)

BUG=247, chromium:94107
TEST=Minidump file sizes should be manageable
Review URL: http://breakpad.appspot.com/300002
------------------------------------------------------------------------

This also enables USE_PROTECTED_ALLOCATIONS. This should have been on all
along because we're using Breakpad through the Framework/Breakpad.mm
interface, which requires it. Note that if we ought not have been using
USE_PROTECTED_ALLOCATIONS, the build would fail.

BUG=94107
TEST=Breakpad should upload reasonably-sized minidump files.
     Apple Crash Reporter logs from processes in which Breakpad handles the
     crash should point the finger at the actual crash source, not the
     Breakpad thread's attempt to write to unwritable memory.
Review URL: http://codereview.chromium.org/7761007

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

in the language pack and the other resources like dialogs in the dll. The latter part is done
automatically by ATL.

BUG=94362
TEST=No change in behavior. The resources should continue to load as before.
Review URL: http://codereview.chromium.org/7763006

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

Landing on behalf of Chris Palmer.

BUG=93554
R=wtc,agl,kevers
Review URL: http://codereview.chromium.org/7766004

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

we're using.

BUG=None
TEST=None
R=noelallen@google.com
Review URL: http://codereview.chromium.org/7771001

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

file. This makes the Native Client authors file a subset of the Chromium one
so that we can update the copyright notices of the code we recently moved into
the Chrome repo to be "Copyright the Chromium Authors."

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

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

BUG=chromium-os:19500,chromium-os:19568
TEST=None


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

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

the OS writes less than expected (for POSIX).

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

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

The libevent gyp target is used by both #host and #target
gyp targets, which are present even when not cross-compiling.
Mark the system libevent as providing both.

This is upstreaming a Gentoo Linux patch.

BUG=none

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

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

BUG=none
TEST=none


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

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

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

ChromeEventProcessingWindow expects the window's controller to implement BrowserCommandExecutor. Oops. Added.

BUG=None
TEST=PanelBrowserWindowCocoaTest.KeyEvent

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

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

BUG=http://code.google.com/p/chromium-os/issues/detail?id=19719
TEST=None
R=noelallen@google.com,zelidrag@google.com
Review URL: http://codereview.chromium.org/7761004

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

This removes MessageWithTuple and MessageWithReply since it
is not easy to export a class that inherits from a template
specialization.  The functionality of those classes are split
now between new classes, MessageSchema and SyncMessageSchema,
and being declared inline via macros.

The key point is that we want to avoid inlining the constructor
and Read functions for messages.  That avoids code bloat since
those functions contain all of the parameter serialization and
deserialization code.  Those are the functions that we really
want to have contained with component DLLs.

To export IPC messages from a DLL, it is necessary to #define
IPC_MESSAGE_EXPORT above message declarations.  You can see this
in action here:
http://codereview.chromium.org/7687005/diff/41012/ppapi/proxy/ppapi_messages.h
Review URL: http://codereview.chromium.org/7768001

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

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

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

BUG=none
TEST=none


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

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

Update defaults so that we pull IDL files from api/dev
Update the interface string gereration to replace
interfaces ending with '_Dev' with (Dev) instead.
Allow for overfide of interface string using 'iname' Property
By default assume range=M13,M14 for multi-version chrome.
(NOTE: A new CL will clean this up and sport =min,max)

BUG= http://code.google.com/p/chromium/issues/detail?id=89969
TEST= ./generator.py
R= brettw@chromium.org
Review URL: http://codereview.chromium.org/7753042

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

This is now possible because there's no core thread to contend with -- the SCM is only used from the sync thread.

BUG=19757,93829
TEST=sync_unit_tests


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

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

BUG=41776
TEST=Unittests

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

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

Also don't include the Remoting Host plugin within the main Chrome archive.

BUG=87632
TEST=Check Offical Mac build

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

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

Our previous PreRead experiment involved flipping a coin on every launch, but we wish to persist the coin-toss between launches. Additionally, this version of the field trial includes an expiry date and limits it to the canary and dev channels.

We are unable to use the FieldTrial mechanism due to PreRead occuring prior to chrome.dll being loaded. As such, we use the registry for persisting the coin-toss and environment variables for communicating between chrome.exe and chrome.dll.

Initially Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=98319

Reverted: http://src.chromium.org/viewvc/chrome?view=rev&revision=98388

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

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

TBR=glider@chromium.org
BUG=51716
TEST=none

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

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

Move the mouse wheel utils from views to ui\base\win, to get rid of some views dependencies in content.
Review URL: http://codereview.chromium.org/7753025

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

as the resource dll issues affecting these tests have now been fixed.

BUG=94362
TBR=grt
Review URL: http://codereview.chromium.org/7767003

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

BUG=87632
TEST=File archived in Official Linux build

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

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

TooltipWidgetGtk is a gtk based helper class that replaces a widget's default tooltip with a RGBA friendly version. It's not closely coupled with views and ui/base/gtk seems to be a better home for it.

This move gets rid of RenderWidgetHostViewGtk's dependency on views.

BUG=none.
TEST=Expect no change. ChromeOS's tooltip should still have rounded corners.

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

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

and added a few more checks for 85408.

BUG=85408


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

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

BUG=none
TEST=none


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

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

 Clicking keyboard (and any popup like menu) was activating the widget, which
 hides VirtualKeyboard as it was stealing focus from browser window.

 This also moves the code that handles window activation to WindowManaer.

 Removed desktop_window_root_view.cc|h as it's no longer necesssary.

BUG=none
TEST=VirtualKeyboard on views desktop should work.

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

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

TBR=sky@chromium.org
BUG=none
TEST=manually

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

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

BUG=59672
TEST=none


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

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

BUG=
TEST=

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

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

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

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

BUG=none
TEST=Verified basic functionality using views_examples.

Review URL: http://codereview.chromium.org/7669028
Patch from Daniel Nicoara <dnicoara@chromium.org>.

TBR=backer@chromium.org,dnicoara@chromium.org
Review URL: http://codereview.chromium.org/7767002

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