I'm not sure why that happened in Chrome, though I'm willing to bet it has something to do with the apache mod I turned on. I also think that's why the front page sometimes doesn't validate: it looks like the mod is flattening the CSS file into the HTML. The original source validates just fine. Jon On Thu, Dec 16, 2010 at 8:40 PM, xhtmlcoder <xhtmlcoder@xxxxxxxxx> wrote: > I cannot see a logical explanation for something like that to happen to > you. Have you tried tabbing through the links then hitting return rather > than use the mouse to see if you get the same result? Obviously clear your > browser cache and history first, etc. > > All I could possible guess (other than a software bug) is the CSS is > somehow rendering strangely for that specific browser version on your > machine - even then it makes little sense why you'd get this weird result. > > I know the page syntax is slightly malformed; as the STYLE should have a > type=”text/css” attribute but that should not affect things too much. > > The only other thing is now; it’s got the 'Google pagespeed' code inserted > on some pages, which is adding strings and there is obviously base64 going > on but that shouldn’t really effect presentational rendering either. > > > ~~~~~~ > Manage your subscription at //www.freelists.org/list/projectaon > > >