search

mcauer / browserscope

Automatically exported from code.google.com/p/browserscope
Apache License 2.0
0 stars 0 forks source link

Browser-Scope UI and CSS #280

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. View this page: http://jsperf.com/jquery-css3-not-vs-not
2. Check out the number formatting and column spacing in the browser-scope 
iframe.
3. Stab out your eyeballs with a pencil in order to cope with the agony.

What is the expected output? What do you see instead?
The results should be readable by humans. There should be some space between 
the column's titles (They currently read as: "CSS3 SelectorNot Method# Tests") 
and other UI tweaks.

What version of the product are you using? On what operating system?
Chrome 9 dev on win XP SP 3.

Please provide any additional information below.
What Browserscope is trying to accomplish is fantastic; however, your UI sucks. 
Please get someone on this so my eyes won't bleed next time I view these 
results. Thanks.

screenshot showing the layout here: http://bit.ly/d4ixlI

Original issue reported on code.google.com by da...@vervestudios.co on 8 Nov 2010 at 4:22

Attachments:

GoogleCodeExporter commented 8 years ago 
Looks like our CSS is not loading properly here.
I'll figure this out and commit a fix this morning, thanks for the excellently 
phrased bug report.

Original comment by els...@gmail.com on 8 Nov 2010 at 4:29

GoogleCodeExporter commented 8 years ago 
Are you viewing the page without CSS enabled by chance? Any other details you 
can provide would be very helpful. Can you send me the full url you're looking 
at there?
I just went to both of the URLs you should be seeing and they look right to me.

Original comment by els...@gmail.com on 8 Nov 2010 at 4:43

Attachments:

GoogleCodeExporter commented 8 years ago 
Wow, that looks great!

It looks as though this is a bug in the dev channel of Chrome where Chrome 
thinks it has a cached version of a resource and doesn't bother querying the 
server for it (even with cache-busting query-strings); so, it looks like I've 
got a corrupt cache. Manually visiting the CSS resource's url and doing a hard 
refresh fixes the issue.

I take what I said about the UI back. It certainly does NOT suck!

Thanks for the great work.

Original comment by musicisair on 8 Nov 2010 at 5:47

GoogleCodeExporter commented 8 years ago 
Whew, glad that's all it was then ;)

Original comment by els...@gmail.com on 8 Nov 2010 at 5:50