Enable ActivityLogApiTest.TriggerEvent and update test

Enable ActivityLogApiTest.TriggerEvent and update test

Blink rev has been rolled to r161048, which includes the innerHTML
move from HTMLElement to Element. Update and enable the test that had
to be disabled during the transition.

BUG=311080
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=232385

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=233586

[dglazkov, 2013-10-31 16:52:53]

Matt, can you look at that?

[felt, 2013-10-31 17:32:17]

https://codereview.chromium.org/54933002/diff/1/chrome/test/data/extensions/a...
File chrome/test/data/extensions/api_test/activity_log_private/test/test.js
(right):

https://codereview.chromium.org/54933002/diff/1/chrome/test/data/extensions/a...
chrome/test/data/extensions/api_test/activity_log_private/test/test.js:275:
domExpectedActivity.push('HTMLElement.' + hookNames[i]);
to double check, this ONLY impacts .innerHTML? (meaning the above test case does
not need to be changed)

[davve, 2013-10-31 19:03:10]

https://codereview.chromium.org/54933002/diff/1/chrome/test/data/extensions/a...
File chrome/test/data/extensions/api_test/activity_log_private/test/test.js
(right):

https://codereview.chromium.org/54933002/diff/1/chrome/test/data/extensions/a...
chrome/test/data/extensions/api_test/activity_log_private/test/test.js:275:
domExpectedActivity.push('HTMLElement.' + hookNames[i]);
On 2013/10/31 17:32:18, felt wrote:
> to double check, this ONLY impacts .innerHTML? (meaning the above test case
does
> not need to be changed)

It impacts innerHTML and outerHTML, neither of which is present in the hookNames
array.

[Matt Perry, 2013-10-31 19:09:38]

lgtm

[commit-bot: I haz the power, 2013-10-31 19:44:41]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/davve@opera.com/54933002/1

[commit-bot: I haz the power, 2013-10-31 23:54:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/davve@opera.com/54933002/1

[commit-bot: I haz the power, 2013-11-01 14:48:47]

Change committed as 232385

[csharp, 2013-11-01 20:13:20]

On 2013/11/01 14:48:47, I haz the power (commit-bot) wrote:
> Change committed as 232385

Reverted because TriggerEvent was failing on the Win7 test bot.
http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/buil...

[davve, 2013-11-01 21:14:36]

On 2013/11/01 20:13:20, csharp wrote:
> On 2013/11/01 14:48:47, I haz the power (commit-bot) wrote:
> > Change committed as 232385
> 
> Reverted because TriggerEvent was failing on the Win7 test bot.
>
http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/buil...

While the failure looks somehow related to the HTMLELement.innerHTML vs.
Element.innerHTML move, I don't understand why it would show on up that bot,
when it had succeeded through the CQ?  The test do seem to have a flaky history.
Is there someone with better understanding of the test that can fill me in here?

[felt, 2013-11-01 22:36:52]

On 2013/11/01 21:14:36, davve wrote:
> On 2013/11/01 20:13:20, csharp wrote:
> > On 2013/11/01 14:48:47, I haz the power (commit-bot) wrote:
> > > Change committed as 232385
> > 
> > Reverted because TriggerEvent was failing on the Win7 test bot.
> >
>
http://build.chromium.org/p/chromium.win/builders/Win7%2520Tests%2520%25281%2...
> 
> While the failure looks somehow related to the HTMLELement.innerHTML vs.
> Element.innerHTML move, I don't understand why it would show on up that bot,
> when it had succeeded through the CQ?  The test do seem to have a flaky
history.
> Is there someone with better understanding of the test that can fill me in
here?

Hi Davve, can you file a bug specific to this issue? I will take a look later
today.

[davve, 2013-11-03 12:38:27]

On 2013/11/01 22:36:52, felt wrote:
> On 2013/11/01 21:14:36, davve wrote:
> > Is there someone with better understanding of the test that can fill me in
> here?
> 
> Hi Davve, can you file a bug specific to this issue? I will take a look later
> today.

Sure: https://code.google.com/p/chromium/issues/detail?id=314466

[felt, 2013-11-05 18:47:56]

On 2013/11/03 12:38:27, David Vest wrote:
> On 2013/11/01 22:36:52, felt wrote:
> > On 2013/11/01 21:14:36, davve wrote:
> > > Is there someone with better understanding of the test that can fill me in
> > here?
> > 
> > Hi Davve, can you file a bug specific to this issue? I will take a look
later
> > today.
> 
> Sure: https://code.google.com/p/chromium/issues/detail?id=314466

Hi Davve,

I suspect the issue has been fixed, so I'm sending this through the CL again.

[commit-bot: I haz the power, 2013-11-05 18:51:18]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/davve@opera.com/54933002/1

[commit-bot: I haz the power, 2013-11-05 22:39:46]

Retried try job too often on win_rel for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2013-11-07 10:50:16]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/davve@opera.com/54933002/1

[commit-bot: I haz the power, 2013-11-07 11:59:32]

Change committed as 233586