Why are fonts very rough in Chrome but fine in the other browsers?

Question

I just started using BrowserLab about an hour ago (5/5/2011 2030 CST).
I am not using the Dreamweaver integration, I'm just going to the BrowserLab site and using the facilities.
The page, on one of my sites, I choose to look at first (http://www.sugarcatsimon.com) looks just about the same in all browsers except for Chrome. In Chrome, with both releases available in BrowserLab - 9.0 and 10.0), the fonts are very rough.
I used to do some screen printing (posters, T-shirts, etc) and in that industry, this lettering would be said to be badly saw-toothed, that is, the edges of the letters are quite rough like the teeth of a saw.
The Chrome representations of the page is just about identical whether I'm using Firefox (3.6.16) or IE (8) when using BrowserLab. I have both running and if I switch back and forth between the two apps, very little on the page display changes. The fonts are quite rough.
Is this something caused by BrowserLab or is it inherent in Chrome and something I will need to take steps to correct?
I'm wondering if it might not be better to simply install all of the various browsers on one or more of my systems and actually use them to check web pages.
Oh yes, does anyone know why Opera is not one of the browsers supported by BrowserLab?
Another question - is there a way to turn off the right click menu for this forum - the one with "Insert Link, Alignment,etc entries? It really is a pain when I go to use Firefox's normal right click menu. It is a pain.
Bob
EDIT -- forgot to say that I am looking at the pages in BrowserLab at the default setting of 100%
Message was edited by: All I tried were in use

Answer 1

Mark,
Thanks for the reply.
I'll see what I can find out about getting the text to look better in
Chrome. I may have to detect it and do something CSS wise. If I find
something, I'll let you know and post a message on the forum.
SIDETRACK - I love it when someone posts a question in a forum "Help,
how do I......?" No one comes up with a solution and then the original
person posts "I found a way to do it, thanks anyway" -- AND THEY DON'T
TAKE THE TIME TO TELL EVERYONE JUST HOW THEY DID IT!!!!!!
Back to BrowserLab -- I found BrowserLab while searching to see if
anyone had any warnings about browsers which will not peacefully
co-habit the same system at the same time. I don't have access to a MAC
but my wife has a friend who is a MAC junky and I should be able to
double check things on her system.
I am still thinking that it might be best, as you say, to install as
many browsers as possible (on multiple machines if necessary) for testing.
As to the right click menu, I wasn't clear about what I was talking
about, sorry. It is when I right click in the "edit box" that the forum
right click menu gets in my face. I use Firefox and use its spell
checker and so, most of the time, when I'm in a forum posting something,
I'm using the context menu to get at the spell checker or to copy or
paste something.
This is a bit of a weird coincident, but I came across something last
night, after I posted the message here, about Firefox and context menus
(right click menus). I happened upon a site where they were trying to
override the context menu to prevent "theft" of images. It worked in
I.E. but not in Firefox. In Firefox I was still seeing the contextual menu.
Doing some research I found that there is an option in Firefox
"dom.event.contextmenu.enabled" which, when set to false, is supposed to
prevent a web site from disabling the context menu (right click menu).
In my Firefox installation, that setting is set to false. That is why
the forum right click menu and Firefox's are getting in each other's way.
I did not look into the forum page in detail but there is obviously some
Javascript (actually I see "JQuery" being used) to try and disable the
context menu within the edit box.
If  I change the "dom.event.contextmenu.enabled" setting to true and
then right click in an edit box on Adobe, Firefox's contextual menu is
not displayed.
In Firefox, go to the address bar and type about:config
There is a colon ( between about and config.
A message will be displayed saying that making changes may void the
warranty - ha, ha - click the "I'll be careful" button.
In the search box at the top of the displayed page, type in context
A few entries will be shown with context in their names. One is
dom.event.contextmenu.enabled. According to the documentation, if the
value is false, Firefox's contextual menu cannot be disabled. If the
value is true, the contextual menu can be disabled.
Whoever coded the attempt at disabling the contextual menu so that only
the Adobe menu is displayed, is not aware of, or does not have a way to
get around, the dom.event.contextmenu.enabled setting.
Go read the thread at
http://forums.mozillazine.org/viewtopic.php?f=8&t=2191055 for details, I
post as Olhanzilla. I seem to have found a way to disable the contextual
menu regardless of the dom.event.contextmenu.enabled setting
Again, thanks for the reply.