Revert "Move innerHTML and outerHTML to Element"

Revert "Move innerHTML and outerHTML to Element"

This reverts commit 160869 as it broke ActivityLogApiTest.TriggerEvent browser test: 
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20Blink&testType=browser_tests&tests=ActivityLogApiTest.TriggerEvent

I'm not sure how severe the problem is so I'd rather revert the offending change than disable the test on Blink roll. 

BUG=311080
TBR=davve@opera.com

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=160914

[yurys, 2013-10-30 09:03:07]

Committed patchset #1 manually as r160914 (presubmit successful).

[mvrable, 2013-10-30 17:03:14]

Adding karenlees to the CC list to keep her informed as she is most familiar
with this test, but she is on vacation this week so I'll respond for her.

I think in this case the failure in ActivityLogApiTest.TriggerEvent is
fine--we'll need to update the test for the IDL changes made but it isn't
indicative of a bigger problem.

If you want you can temporarily mark the TriggerEvent test as disabled and
un-revert the blink changes.  I can work on updating the ActivityLogApiTest test
after the new blink roll lands and re-enable when that is done.  (Or I think I
could disable our test if you aren't easily able to that.)

--Michael Vrable

[davve, 2013-10-30 21:20:31]

On 2013/10/30 17:03:14, mvrable wrote:
> Adding karenlees to the CC list to keep her informed as she is most familiar
> with this test, but she is on vacation this week so I'll respond for her.

Thanks!

> If you want you can temporarily mark the TriggerEvent test as disabled and
> un-revert the blink changes.

The test is disabled in https://codereview.chromium.org/45733012/

The re-land is https://codereview.chromium.org/52443003/

> I can work on updating the ActivityLogApiTest test
> after the new blink roll lands and re-enable when that is done.  (Or I think I
> could disable our test if you aren't easily able to that.)

I wouldn't say easily, 7 hours and 32 minutes and counting... :)

[felt, 2013-10-30 21:23:09]

On 2013/10/30 21:20:31, davve wrote:
> On 2013/10/30 17:03:14, mvrable wrote:
> > Adding karenlees to the CC list to keep her informed as she is most familiar
> > with this test, but she is on vacation this week so I'll respond for her.
> 
> Thanks!
> 
> > If you want you can temporarily mark the TriggerEvent test as disabled and
> > un-revert the blink changes.
> 
> The test is disabled in https://codereview.chromium.org/45733012/
> 
> The re-land is https://codereview.chromium.org/52443003/
> 
> > I can work on updating the ActivityLogApiTest test
> > after the new blink roll lands and re-enable when that is done.  (Or I think
I
> > could disable our test if you aren't easily able to that.)
> 
> I wouldn't say easily, 7 hours and 32 minutes and counting... :)

Do you mean it isn't easy because of how long the CQ is taking?

Since the CL is just a disable, it would be fine to dcommit it. Are you a
committer? If not, let me know and I will land it to let the blink roll through.

[davve, 2013-10-30 21:30:06]

On 2013/10/30 21:23:09, felt wrote:
> On 2013/10/30 21:20:31, davve wrote:
> > On 2013/10/30 17:03:14, mvrable wrote:
> > > I can work on updating the ActivityLogApiTest test
> > > after the new blink roll lands and re-enable when that is done.  (Or I
think
> I
> > > could disable our test if you aren't easily able to that.)
> > 
> > I wouldn't say easily, 7 hours and 32 minutes and counting... :)
> 
> Do you mean it isn't easy because of how long the CQ is taking?

Basically. It did feel odd to tie up a bunch of resources for a disable...

> Since the CL is just a disable, it would be fine to dcommit it. Are you a
> committer? If not, let me know and I will land it to let the blink roll
through.

I am not a committer, no and would appreciate the help! :)

[davve, 2013-10-30 21:32:16]

On 2013/10/30 21:30:06, davve wrote:
> On 2013/10/30 21:23:09, felt wrote:
> > On 2013/10/30 21:20:31, davve wrote:
> > > On 2013/10/30 17:03:14, mvrable wrote:
> > > > I can work on updating the ActivityLogApiTest test
> > > > after the new blink roll lands and re-enable when that is done.  (Or I
> think
> > I
> > > > could disable our test if you aren't easily able to that.)
> > > 
> > > I wouldn't say easily, 7 hours and 32 minutes and counting... :)
> > 
> > Do you mean it isn't easy because of how long the CQ is taking?
> 
> Basically. It did feel odd to tie up a bunch of resources for a disable...
> 
> > Since the CL is just a disable, it would be fine to dcommit it. Are you a
> > committer? If not, let me know and I will land it to let the blink roll
> through.
> 
> I am not a committer, no and would appreciate the help! :)

But I don't think there is a blink roll waiting on this though. I haven't
checked commit on the re-land in blink.

[davve, 2013-10-30 21:42:18]

> But I don't think there is a blink roll waiting on this though. I haven't
> checked commit on the re-land in blink.

Since you're helping me with getting the test disabled, I've now added the
re-land to CQ. Thanks again for your help!