Avoid sending WINDOW_CONTENT_CHANGED more than once when frame info changes.

Avoid sending WINDOW_CONTENT_CHANGED more than once when frame info changes.

Use a boolean to only send WINDOW_CONTENT_CHANGED the first time
notifyFrameInfoInitialized is called. See bug for longer discussion of
issue.

BUG=419541
Committed: https://crrev.com/b2298d533e44537313c2d071064e024af2eba70d
Cr-Commit-Position: refs/heads/master@{#297824}

[dmazzoni, 2014-10-01 21:31:16]

dmazzoni@chromium.org changed reviewers:
+ plundblad@chromium.org

[Peter Lundblad, 2014-10-02 09:22:44]

Hi,

This makes total sense if any following call wouldn't imply any change to the
node tree.  In addition, I think we should do what the Android framework does
and
rate-limit these events. I've seen actual slowdowns when many of this event are
sent
over a short time.  Separate issue, though.

[Peter Lundblad, 2014-10-02 09:23:44]

The CQ bit was checked by plundblad@chromium.org

[Peter Lundblad, 2014-10-02 09:23:45]

lgtm

[commit-bot: I haz the power, 2014-10-02 09:24:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/624503002/1

[commit-bot: I haz the power, 2014-10-02 09:33:15]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-02 09:33:16]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[dmazzoni, 2014-10-02 13:30:15]

The CQ bit was checked by dmazzoni@chromium.org

[commit-bot: I haz the power, 2014-10-02 13:30:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/624503002/1

[commit-bot: I haz the power, 2014-10-02 13:39:59]

Committed patchset #1 (id:1) as b10d4e5ddee839230ce1f3159216bef1c2fdff72

[commit-bot: I haz the power, 2014-10-02 13:40:44]

Patchset 1 (id:??) landed as
https://crrev.com/b2298d533e44537313c2d071064e024af2eba70d
Cr-Commit-Position: refs/heads/master@{#297824}