Some style nits

[Janpot]

Some suggestions I've been collecting over the few weeks I've been using this library (really loving it so far):

1. Use a nicer icon for close button like: ✕ (U+2715).
   

2. Use pointer cursor for the rows to indicate they're clickable
   
   Also, the tabs "General", "Request",... don't have a pointer cursor.

3. make the <h3> in the details view an anchor tag, so it's easier to navigate to it directly and easier to copy with "Copy Link Address"

4. Sometimes the contrast between text color and background color make tab titles hard to read
   

[Janpot]

@micmro adding another one here about the 'Raw Data' tab.

It would look better with a width: 100%
also, the white margins would look better if they had the same color as the <pre>:

[micmro]

Thanks for the feedback. Some really good ideas.

Only 4. looks like an issue with your local CSS. It seems you give your buttons a colour in a very specific CSS selector. I've given it a higher specificity as part of the link anyway so perhaps it'll be fix this way.

[soulgalore]

Wow great changes! One thing about the raw tab: The HAR file can contain HTML in the text element (I can add a link to an example later today) and that HTML will run in the raw tab as it is now and if it is inline CSS, it can change the look and feel of the page.

[soulgalore]

Let me create a separate issue for that :)

[Janpot]

@micmro Strange, my page only has a handful other style rules. Could it be that on the demo page there's a css reset that sets button color to inherit and cursor to pointer?

[micmro]

Right, I use CSS normalizer in both the preview and the demo page - was not aware that buttons do not inherit the colour by default (learn something new every day :)). Should be fixed with this PR then.

[Janpot]

Not sure you want to go that route, but it should be possible with a preprocessor to scope normalize.css to .water-fall-chart and add the result to perf-cascade.css. seems like they do a similar thing here: https://github.com/dperrymorrow/markdown-css/blob/master/src/scoped-normalize.less

[micmro]

I had thought about this in the beginning of the project, but decided that most project use some reset anyway - I also wanted to keep the styles as simple and easily over-writable as possible.
So I don't fancy adding a scoped reset too much. However I tried the current PR without the normalizer in chrome and FF and it looks fine - I might remove it for the dev-version to ensure we stay (relatively) reset-safe.

[Janpot]

👍 totally reasonable

[micmro]

released with v0.5.0