One thing that has always impressed me is the ability of web designers to deal with browser idiosyncrasies.
For instance, knowing why this happens in firefox-17.0.1-1.fc17.x86_64 –
A bootstrap btn-primary viewed from 0.0.0.0
A bootstrap btn-primary viewed from localhost
A bootstrap btn-primary firebug computed color from 0.0.0.0 and localhost
Needless to say, the web is littered with questions about why btn-primary background color is not always white. Most have answers, some with varying degrees of complex css. Others involve changing versions of software. All the while it might just be the URL used to view the page.
Test in a production environment.
Tags: complexity, idiosyncrasies, Web design
Spinning 
January 7, 2013 at 9:22 am |
So, why does this happen then?
January 7, 2013 at 10:06 am |
I couldn’t tell you. The workaround is so simple and sane – test in an environment the closely resembles production – that it was not worth digging any deeper.
January 8, 2013 at 4:15 am |
Dear friend,
firefox identifies localhost as something local while on the other address it recognizes as an internet address so it handles like a regular internet webpage by putting links in blue (default behaviour).
January 17, 2013 at 9:16 am |
Never noticed white not being white, although i like a nice #f2f2f2 myself