DevTools: Click on console tab header should bring focus on console prompt.

R=pfeldman

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161076 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Mark tests that need to be rebaselined after http://crrev.com/24090003 lands

This marks virtual/softwarecompositing/culling/filter-occlusion* as
NeedsManualRebaseline. These tests will needed to be rebaselined after
Chromium CL http://crrev.com/24090003 lands.

TBR=senorblanco@chromium.org
BUG=160302

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161077 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: make device select a popup-based select.

TBR=vsevik

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161078 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Bindings: Remove special cases for DOMStringList

When DOMStringList was added, special cases were also added so that it
could masquerade as sequence<DOMString> and DOMString[] as well, since
those Web IDL types were not supported. Now that Blink IDL understands
sequence<T> and T[] we can remove the special cases.

R=haraken@chromium.org,nbarth@chromium.org
BUG=239771

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161079 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Making OwnPtr's operator== guards const.

OwnPtr defines operator== to stop people from comparing two OwnPtr objects with
== (this makes sense as if two OwnPtr's pointed at the same thing then their
would be two owners of the same memory!).

However, these operator==s where not defined as const, so if one of your OwnPtr
objects was const then the guards where not matched. To make things worse,
OwnPtr defines a (const) conversion to bool and operator== does know compare two
bools!

The following example compiles and then doesn't do what you expect.

    const OwnPtr<MyClass> a = getOwnPtrA();
    OwnPtr<MyClass> b = getOwnPtrB();
    if (a == b) {
      // Body
    }

 1) a gets implicitly converted to a bool, which is true if ptr is not NULL.
 2) b gets implicitly converted to a bool, which is true if ptr is not NULL.
 3) true == true is true
 4) Even though a and b point at totally different things, the body of the if
    statement gets executed!

(Don't look like anyone has been silly enough to actually be hurt by this yet.)

R=abarth@chromium.org, enne@google.com
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161080 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove dead code from HTMLViewSourceDocument

There's no reason to call lazyAttach() anymore after calling parserAppendChild.
This patch also removes some code that doesn't compile behind an ifdef which
uses an API that no longer exists (ContainerNode::addChild?) which was also
calling lazyAttach.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161081 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: check for canForceCompositingMode before trying to emulate device metrics.

BUG=288959,308422

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161082 bbb929c8-8fbe-4397-9dbb-9b2b20218538