Move navigatorcontentutils directory to top of LayoutTests

Move navigatorcontentutils directory to top of LayoutTests

Modules tests have been placed in top of LayoutTests. So, this cl moves navigatorcontentutils
to top of LayoutTests.

BUG=none

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

[gyuyoung-inactive, 2014-06-13 03:52:04]

Add haraken.

[haraken, 2014-06-13 04:05:01]

LGTM, but I'd like to have ojan@ confirm.

[ojan, 2014-06-13 04:20:41]

On 2014/06/13 04:05:01, haraken wrote:
> LGTM, but I'd like to have ojan@ confirm.

I'm not opposed to this. It doesn't seem terribly useful to me though. The
layout test tree structure was never intended to match the C++ code tree
structure.

This patch does have one minor downside, which is that looking at the blame
history for this file requires an extra hop now.

If there's a benefit other than matching the C++ tree structure, then I'm fine
with this patch. If there isn't, I probably wouldn't bother, but I also won't be
upset if this lands. :)

[gyuyoung-inactive, 2014-06-13 04:38:47]

On 2014/06/13 04:20:41, ojan wrote:
> On 2014/06/13 04:05:01, haraken wrote:
> > LGTM, but I'd like to have ojan@ confirm.
> 
> I'm not opposed to this. It doesn't seem terribly useful to me though. The
> layout test tree structure was never intended to match the C++ code tree
> structure.
> 
> This patch does have one minor downside, which is that looking at the blame
> history for this file requires an extra hop now.

> If there's a benefit other than matching the C++ tree structure, then I'm fine
> with this patch. If there isn't, I probably wouldn't bother, but I also won't
be
> upset if this lands. :)

Yes, this cl will make an extra effort to find the blame history. However, the
"navigatorcontentutil" directory was made by me.
So, current blame list only includes me !

I'm planning to add more tests and support "content handlers" in below spec.
(http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers)

So, I would like to extract "navigatorcontentutils" to top place so that I
improve the tests a little more easily.

[ojan, 2014-06-13 04:54:55]

I don't feel strongly about this. Go ahead and commit.

[gyuyoung-inactive, 2014-06-13 05:00:39]

The CQ bit was checked by gyuyoung.kim@samsung.com

[gyuyoung-inactive, 2014-06-13 05:00:47]

On 2014/06/13 04:54:55, ojan wrote:
> I don't feel strongly about this. Go ahead and commit.

Thanks ojan !

[commit-bot: I haz the power, 2014-06-13 05:01:06]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/gyuyoung.kim@samsung.com/335783003/1

[commit-bot: I haz the power, 2014-06-13 06:07:30]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/11865)

[gyuyoung-inactive, 2014-06-13 06:56:47]

The CQ bit was unchecked by gyuyoung.kim@samsung.com

[gyuyoung-inactive, 2014-06-13 07:41:04]

The CQ bit was checked by gyuyoung.kim@samsung.com

[commit-bot: I haz the power, 2014-06-13 07:41:53]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/gyuyoung.kim@samsung.com/335783003/20001

[gyuyoung-inactive, 2014-06-13 07:42:10]

On 2014/06/13 06:56:47, gyuyoung wrote:
> The CQ bit was unchecked by mailto:gyuyoung.kim@samsung.com

I missed to change an include path of resources/js-test.js in test cases. Sorry
about that. Fixed.

[commit-bot: I haz the power, 2014-06-13 08:43:52]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/11887)

[commit-bot: I haz the power, 2014-06-13 09:44:28]

Change committed as 176105