Remove some dead code in ChromeRenderViewObserver related to a method on WebPermissionClient that doesn't exist anymore.

BUG=304341
R=nasko@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240215 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 240215
Update the Public Suffix List to the latest version

This updates the effective-TLD data file to:
e5ca4a98aa68 2013-12-02 13:07 -0500

It includes changes from a number of Mozilla bugs, listed on
http://hg.mozilla.org/mozilla-central/filelog/e5ca4a98aa68/netwerk/dns/effective_tld_names.dat
between 06c405ba54b3 (2013-09-17 17:54 +0100) and e5ca4a98aa68
(2013-12-02 13:07 -0500)

One Chromium-specific modification is to carve out csiro.au (from "csiro.au" to "!csiro.au"). This is temporary while it's being worked out upstream on the appropriate long-term solution.

BUG=37436, 324085
R=wtc@chromium.org, pkasting@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240216 0039d316-1c4b-4281-b951-d872f2087c98
Init LatencyInfo for TouchEvent only when constructing from NativeEvent

I am guessing that manually constructing TouchEvent with provided timestamp
can result in a wrong LatencyInfo that can contribute a huge amount of wrong
UMA data.

So lets not init the LatencyInfo if the TouchEvent is not constructed from
NateiveEvent and see if we can bring the UMA stats of
Event.Latency.RendererImpl.GestureScrollUpdate back to be reasonable.

BUG=326954
TEST=Event.Latency.RendererImpl.GestureScrollUpdate still shows when testing
     scroll on Pixel.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240217 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 240216
SVN changes up to revision 240217