For reference here's FF
![Image](http://i51.tinypic.com/2jg2beg_th.png)
Now here's Chrome
![Image](http://i56.tinypic.com/ano701_th.png)
For me the text is definitely smaller than it should be. Which of the two screens in the OP resembles you screen?Deepcrush wrote:Chrome works just fine for me. I've only once had a problem with chrome since it came out.
It's broken in such a way that fixing it in Chrome will cause it to be significantly broken in every other browser. The result would be that the text on each button exceeds the space allowed for the button making it impossible to read. I'd rather you think it's a little small than make every other browser completely unusable.Primefalcon wrote:Fact is larger and larger amounts of people are using it, it is now the 3rd most popular browser behind IE and FF, so regardless of whose fault it is, it is ditl that looks the worse for it.
For reference I've fixed the issue for myself in Google Chrome by installing the stylish plugin and using this rule....
Code: Select all
$useragent = $_SERVER['HTTP_USER_AGENT'];
if (preg_match("/Chrome/", "$useragent")) { echo 'a.textlink { font-size: 20px !important; }'; }
Neither, my screen looks a little off from the GC pic. However it may not be a problem for me since my screen is 17' across.IanKennedy wrote:For me the text is definitely smaller than it should be. Which of the two screens in the OP resembles you screen?Deepcrush wrote:Chrome works just fine for me. I've only once had a problem with chrome since it came out.
If you wanted to update all html pages that could be an issue since you have the buttons across all the ship pages and such..... Now I am not trying to tell you guys what to do, this is a damm great site, I respect you both immensely as knowledgeable individuals. The thing is we're going in Chrome version 6 now and it's still an issue, and Chrome is starting to gain a larger audience (probably because they're Google, also it is far more stable and faster than FF).IanKennedy wrote:That's a really bad idea given there's 284 files to be updated. I'll just wait for them to get their act together. For <5% of users it's not worth it for now. You have a fix already.
Code: Select all
<?php header("Content-Type: text/css"); ?>
The reason IE 6 lasted so long is because it was so non-standard. That meant moving to the 'more standard' (ha, as if) IE 7 broke a lot of code. Equally, the move from 7 to 8 breaks a fair bit more, but at least it, perhaps, offers the chance that those sites that only support IE could go standard and thus get rid of the need for the IE specific nonsense altogether.Primefalcon wrote:I am not arguing with you at all.... I'm just concerned some newcomers who use Chrome will think it's DITL rather than Chrome....
Don't get me started on IE, at least version 8 has shown some nice improvements for standards... still a long way to go though. At least IE6 is dying off finally, now we'll just have to wait another 6 years for the same to happen to 7.