Have DOMDataStore::current() return a reference

Have DOMDataStore::current() return a reference instead of a pointer as
it can never return null. This makes the calling code look safer.

R=adamk

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161981 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove DeferredImageDecoder::createResizedLazyDecodingBitmap

Motivation:
    This code is not used.  Removing it will make it easier to make
    changes to Lazy SkPixelRefs in the future.

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161982 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Never look for the focused elment under nodes which are not in a document.

This makes http://jsperf.com/parse-html-type 10% faster.
78k ops/s vs. 70k ops/s on the "tags" test on my machine.

This is kinda a hack for this microbenchmark, but the change
is also simply correct.  Hayato is working on a more generic
fix to make EventPath faster (which we'll still hit
when the node is actually in a document and could have a
focused child).

I also fixed FullScreenElementStack's copy-pasta version
of this function to also check.  I suspect if we full-screened
and element on the page of this microbenchmark we'd find it
was another 10% slower due to FSES's version of this
"search for a possibly removed child" function.

R=esprehn
BUG=318251,318448

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161984 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Web Animations: Use legacy cascade behaviour and the MatchedPropertiesCache

This patch changes the behaviour of the Web Animations backed animations
and transitions implementation to apply animations / transitions at the
last step of the cascade. This is the same behaviour as the legacy code
but not correct according to the spec[1]. The current behaviour is a bit
strange, it attempts to follow the spec but property dependencies (such
as using ems) do not work correctly as low priority properties will only
be re-applied if they are !important and we are running animations on a
low priority property.

As a result of moving animations / transitions to the end of the cascade
we can easily use the MatchedPropertiesCache for all running animations
and transitions. Once we correct the cascade order we'll need to disable
the cache in several cases.

[1] http://www.w3.org/TR/css3-cascade/#cascading

BUG=232273,314952

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161985 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Web Animations: In ActiveAnimations, track players with animations targeting the corresponding element

This will support implementing compositor animations and later
Element.getCurrentPlayers.

This subtly changes the behavior of Element::activeAnimations to return an
ActiveAnimations instance once it has been initialized rather than only when
it contains active animations.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161987 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add WebPublicSuffixList interface.

The public suffix list specifies the set of top-level domains.  For example, it tells us that for google.co.uk,
co.uk is the top-level domain, not just uk.

This will be used shortly to prevent setting document.domain to top-level domains.

BUG=307407

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

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