GitLab

Not DefProc'ing the NCActivate seems to cause the process not to be shown as activate when originally shown.

BUG=4513
TEST=Start Chrome, the Chrome entry in the task bar should be shown as active.
R=ben
Review URL: http://codereview.chromium.org/28240

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

BUG=5549
R=sky
Review URL: http://codereview.chromium.org/27229

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

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

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

The browser process now keeps a queue of the last keyboard
events that it sent to the renderer in a queue and pops them
on ACK. If a key is unhandled, we use the copy in the browser
process; we don't even send the key back in the ACK anymore.
Review URL: http://codereview.chromium.org/27244

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

APIs custom.

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

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

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

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

Additionally, wire in a bit of setup for the --single-process case,
because it cannot be done by the renderer thread because that thread
is not the main thread.

Fair warning: --single-process often seems to be broken by various
unrelated changes, which may-or-may-not make assumptions about the
process architecture.  I will try to stay on top of these.

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

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

Original patch by Kim Christensen (see http://codereview.chromium.org/28150 ), r=me,brettw, tweaked slightly.

BUG=7227

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

platform.

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


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

Reviewed in issue 27186.

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

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

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

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

LGTMed by Elliot Glaysher.
See http://codereview.chromium.org/27079



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

don't post a dummy task to ProcessPendingQueue (with a
writer).

BUG=4731
TEST=unittest.

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

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

renderer trees look different because of our forked changes to
RenderTextControlMultiLine, specifcally the call to setOverflowX,
which results in creating the different layers.

BUG=none
TEST=none

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

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

Rebaseline an SVG layout test. The border lines of the top box are drawn in a slightly different shade of red compared to the baseline, and as always, the vertical edge lines of the entire image is in a very slight different shade.
Review URL: http://codereview.chromium.org/27239

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

Fix toolbar keyboard focus (shift-alt-t), which was broken by me, and toolbar button context menus on VK_APPS, which was broken by Jonas.

The overall focus issue was caused by my change that made View::RequestFocus() sanity-check that the View was focusable.  The toolbar uses a crazy hack where it purposefully wants to get focus even though it's not focusable.  :P

The context menu issue was caused by Jonas changing the name of a virtual function, presumably not realizing it was a virtual, not just a simple accessor.  I changed the name back and marked this function (and several others) as virtual.  In order to avoid blowing up the source in toolbar_view.cc, I reverted users of the accessor to just using the member variable name.

Also reordered a couple functions to match the order they were originally declared in View.h.
Review URL: http://codereview.chromium.org/27175

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

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

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

* Clarify some comments.
* Simplify some redundant boolean logic.
* Add a helper function for something a lot of callers were checking manually.
* Fix lint.
Review URL: http://codereview.chromium.org/27247

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

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


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

The controlling code in filter.cc doesn't significantly distinguish
FILTER_OK and FILTER_NEEDS_MORE_DATA, but we *should* transition
to a semantic where FILTER_OK becomes instead "FILTER_NEEDS_OUTPUT_SPACE"
and then we'd need to do this uniformly for all filter code.
We *could* then improve the driving filter code (for example, not have
to sniff output buffer usage to deduce that the filter wanted to be 
called again to emit more data).

r=huanr
Review URL: http://codereview.chromium.org/28193

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

Now that the buildbots have cycled, it looks like two tests
that I recently rebaselined are now passing on Linux. Update
the testlist to reflect that.

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

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

TBR=aa
Review URL: http://codereview.chromium.org/27248

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

TBR to get the tree green.

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


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

TBR=evan

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

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

TBR=tony

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

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

TBR=avi

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

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

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

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

Fix a DCHECK in certain cases when coming out of fullscreen mode.  The frame gets to layout before the browser view, but it needs to know what the browser view's tabstrip layout is going to look like, or it will lay out wrong.
Review URL: http://codereview.chromium.org/27231

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

port third-party code that reports memory allocation
failures.

R=darin,eroman
Review URL: http://codereview.chromium.org/28216

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

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


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

R=dglazkov

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

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

Defer new tests.

Fix wdiff to have deletes be red and new lines be green (it was reversed).

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

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

it wasn't that the bookmark bar was all black, rather that BrowserView
thought the bookmark bar was parented when in fact it wasn't. The
black was the result of BrowserView reserving the space for the
bookmark bar and not painting anything in it's space.

BUG=7922
TEST=see bug

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

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

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

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

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

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

This corresponds with <http://codereview.chromium.org/28049>.

BUG=2764
Review URL: http://codereview.chromium.org/28220

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

included in data pack files.

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


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

While I'm at it, remove references to .dll in comments in the file.

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

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

VNC servers don't support Xrender. For this use case, we implement a
slow fallback which byte-fiddles the Skia bitmaps as needed to support
32 and 24 bit visuals.

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


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