Make sure profile types are created before handling console.profile/profileEnd

Moved profile type creation into ProfileTypeRegistry which is instantiated on module load.

This fixes an exception in console when console.profile()/profileEnd() is called before Profiles panel has been shown. This is a regression from r165552:

[4737:4737:0127/120553:ERROR:CONSOLE(79)] "Uncaught TypeError: Cannot call method 'consoleProfileStarted' of null", source: chrome-devtools://devtools/bundled/CPUProfilerModel.js (79)

BUG=None
R=loislo@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165837 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove unnecessary maybeDOMWrapper from indexed/named property getters

The following call is unnecessary:
ASSERT(V8DOMWrapper::maybeDOMWrapper(info.Holder()));
...since info.Holder() is guaranteed to return a DOMWrapper.

...per request of haraken:
https://codereview.chromium.org/148083004/#msg3

TBR=haraken

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165838 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: remove unused images.

R=apavlov, lushnikov, pfeldman

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165839 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make event retargeting algorithms work for multiple shadow trees.

The relevant spec issue is: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23769

So far, event retargeting for multiple shadow trees does't work nicely. 
Event listeners registered on nodes in the younger shadow tree can't see the
original event target in the older shadow tree.

This issue is one of the missing pieces that we have to resolve to make the
event section in the Shadow DOM spec complete.

To resolve the issue, I've updated the spec so that the current event retargeting 
algorithm will work without any modifications. What has changed is the definition 
of tree of trees. By this new definition of trees of trees, we can apply the 
current event retargeting algorithms "as-is" to achieve the desired behavior.

In the implementation, I no longer use a stack-based approach to track adjusted
targets. That's no longer an effective solution. Instead of that, I introduced a 
carefully designed recursive algorithm, which is defined in 
EventPath::ensureTreeScopeEventContext. Because we visit each ancestor TreeScope 
only once (or twice), we can still achieve O(N) (N is the number of ancestor
TreeScopes),  instead of O(N^2), to calculate adjusted targets.

BUG=337089

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165840 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename m_layoutRoot to m_layoutSubtreeRoot.

The layoutRoot is set when we're doing a layout of a subtree. Rename the
variable to make it more explicit that it points to a subtree.

This also adds is isASubtreeLayout() method to FrameView to replace the various
places we use if (m_layoutRoot) with if (isASubtreeLayout()) to make things
a bit clearer.

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165841 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Auto-rebaseline for r165834

http://src.chromium.org/viewvc/blink?view=revision&revision=165834

BUG=308818
TBR=kouhei@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165842 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix spacing style for anonymous special operations

Anonymous special operations should be spaced like this:
getter DOMString (unsigned long index);
...not like this:
getter DOMString(unsigned long index);
...b/c this looks like a function called "DOMString"!
(This follows spec.)

Fixed and documented:
https://sites.google.com/a/chromium.org/dev/blink/webidl#TOC-Style

TBR=haraken

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165843 bbb929c8-8fbe-4397-9dbb-9b2b20218538
IDL compiler: put constructor contents together

Minor refactoring: in generate_interface, it's clearer to put the
constructor contents together, which helps group the code more
clear IMO.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165844 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove support for panel per profile type

The experiment was removed some time ago but there are some leftovers.

BUG=None
R=loislo@chromium.org

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

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