Remove importing CSS for results details page.

Remove importing CSS for results details page.

Removing this for a few reasons. (1) We don't use much CSS from
the file we import. (2) It couples our results details page with
the waterfall CSS file (things like classnames info/interface were
used in that CSS but don't seem to do anything special just looking
at results detail page) and (3) we might want local result detail
pages eventually.

Review-Url: https://codereview.chromium.org/2886323003
Cr-Commit-Position: refs/heads/master@{#472903}
Committed: https://chromium.googlesource.com/chromium/src/+/e99ade7b40d361233acfad8d735dc66a34799de6

[mikecase (-- gone --), 2017-05-18 02:02:44]

mikecase@chromium.org changed reviewers:
+ hzl@chromium.org, jbudorick@chromium.org, yolandyan@chromium.org

[mikecase (-- gone --), 2017-05-18 02:02:44]

I'll double check before committing, but the result detail page looks identical
(and I even went thru all the css properties of various elements in dev-tools)

[mikecase (-- gone --), 2017-05-18 02:04:29]

Description was changed from

==========
Remove importing CSS from results details.

Removing this for a few reasons. (1) We don't use much CSS from
the file we import. (2) It couples our results details page with
the waterfall CSS file (things like classnames info/interface were
used in that CSS but don't seem to do anything special just looking
at results detail page) and (3) we might want local result detail
pages eventually.
==========

to

==========
Remove importing CSS for results details page.

Removing this for a few reasons. (1) We don't use much CSS from
the file we import. (2) It couples our results details page with
the waterfall CSS file (things like classnames info/interface were
used in that CSS but don't seem to do anything special just looking
at results detail page) and (3) we might want local result detail
pages eventually.
==========

[jbudorick, 2017-05-18 03:13:43]

Fired a couple of trybots to make sure this looks ok. Code looks fine. Will
revisit in the morning.

[jbudorick, 2017-05-18 13:30:37]

On 2017/05/18 03:13:43, jbudorick wrote:
> Fired a couple of trybots to make sure this looks ok. Code looks fine. Will
> revisit in the morning.

The one difference I'm noticing is that the links on the test page are blue,
whereas links on the suite page are black. Currently, links in both cases are
black.

[mikecase (-- gone --), 2017-05-18 14:50:41]

On 2017/05/18 at 13:30:37, jbudorick wrote:
> On 2017/05/18 03:13:43, jbudorick wrote:
> > Fired a couple of trybots to make sure this looks ok. Code looks fine. Will
> > revisit in the morning.
> 
> The one difference I'm noticing is that the links on the test page are blue,
whereas links on the suite page are black. Currently, links in both cases are
black.

a yes, I missed grabbing...

a:link,a:visited,a:active {
        color: #444;
}

Just need to add that back and its all good.

[mikecase (-- gone --), 2017-05-18 15:22:44]

fixed

[jbudorick, 2017-05-18 15:24:42]

lgtm

[mikecase (-- gone --), 2017-05-18 15:28:47]

The CQ bit was checked by mikecase@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-18 15:29:44]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-18 19:04:50]

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

[commit-bot: I haz the power, 2017-05-18 19:04:51]

Dry run: This issue passed the CQ dry run.

[mikecase (-- gone --), 2017-05-18 19:28:41]

The CQ bit was checked by mikecase@chromium.org

[commit-bot: I haz the power, 2017-05-18 19:30:12]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-18 19:36:20]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1495135721278710,
"parent_rev": "74008fbe10dff1e03e4d5a9c941d6700705231df", "commit_rev":
"e99ade7b40d361233acfad8d735dc66a34799de6"}

[commit-bot: I haz the power, 2017-05-18 19:36:31]

Description was changed from

==========
Remove importing CSS for results details page.

Removing this for a few reasons. (1) We don't use much CSS from
the file we import. (2) It couples our results details page with
the waterfall CSS file (things like classnames info/interface were
used in that CSS but don't seem to do anything special just looking
at results detail page) and (3) we might want local result detail
pages eventually.
==========

to

==========
Remove importing CSS for results details page.

Removing this for a few reasons. (1) We don't use much CSS from
the file we import. (2) It couples our results details page with
the waterfall CSS file (things like classnames info/interface were
used in that CSS but don't seem to do anything special just looking
at results detail page) and (3) we might want local result detail
pages eventually.

Review-Url: https://codereview.chromium.org/2886323003
Cr-Commit-Position: refs/heads/master@{#472903}
Committed:
https://chromium.googlesource.com/chromium/src/+/e99ade7b40d361233acfad8d735d...
==========

[commit-bot: I haz the power, 2017-05-18 19:36:32]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/e99ade7b40d361233acfad8d735d...