Forums | MacLife
You are not logged in.
#1 2008-06-18 3:24 pm
- Rik
- Unemployed Guy
- Administrator
- From: San Francisco CA USA
- Registered: 2001-08-06
- Posts: 517
Firefox 3.0 problems
I'm finding a host of character-rendering and line-spacing problems with the new Firefox 3.0.
For example, MacLife.com's headlines and other display type are shown in Times, and not the site's standard sans serif font.
Macworld.com's headlines do not appear in Times, but all the characters are piling up upon one another, making the headlines unreadable.
Also, my personal resume site and blog (www.myslewski.com) experiences multiple character-rendering problems (mostly too-wide kerning), and line breaks that now appear where they're clearly not in the code.
It appears as if Firefox 3.0 is misinterpreting CSS data. Possibly. Maybe.
However, when I installed Firefox 3.0 on a couple of other Macs running 10.5.3 here at Chez Polonaise, none of them exhibit the same problems as does Firefox on my dual 2.7GHz Power Mac G5 running OS 10.5.3.
Yes, I've dumped and rebuilt all the appropriate plist and other support files, cleared all caches (including System-font caches), but I'm still experiencing what appear to be CSS problems.
Any suggestions from anyone?
Offline
#2 2008-06-18 3:34 pm
- sturner
- Royal High Poobah
- Moderator
- From: Carrollton, TX USA
- Registered: 2000-01-31
- Posts: 13779
Re: Firefox 3.0 problems
At least it's running. On my IBM Thinkpad it won't load a single page.
I'm not dead yet.
There are 3 types of people, those who can count and those who can't.
"There are few things graven in stone, excepting your date of death."
Offline
#3 2008-06-18 4:00 pm
- D'Eyncourt
- OMGDICTATOR
- Registered: 2001-12-27
- Posts: 8807
- Website
Re: Firefox 3.0 problems
I'm not having any kerning or line-break problems on your site using Firefox 3.0 with Windows XP here.
BOYCOTT SONY
"I think the question now is not whether you went to Vietnam or whether you didn't, whether you fought in the war or fought against the war. I think the only question is whether we can find a president smart enough never to make a mistake like that again"--Molly Ivins, way back in 1992
Offline
#4 2008-06-18 4:12 pm
- kamizuno
- Poking you with a stick
- From: Smileytown
- Registered: 1999-07-13
- Posts: 1987
Re: Firefox 3.0 problems
D'Eyncourt wrote:
I'm not having any kerning or line-break problems on your site using Firefox 3.0 with Windows XP here.
Yeah, your website looks OK on my Intel Mac with FF 3.0, no problems that I can see 
Last edited by kamizuno (2008-06-18 4:15 pm)
Offline
#5 2008-06-18 5:35 pm
Re: Firefox 3.0 problems
kamizuno wrote:
D'Eyncourt wrote:
I'm not having any kerning or line-break problems on your site using Firefox 3.0 with Windows XP here.
Yeah, your website looks OK on my Intel Mac with FF 3.0, no problems that I can see
Ditto.
Offline
#6 2008-06-18 7:18 pm
- Rik
- Unemployed Guy
- Administrator
- From: San Francisco CA USA
- Registered: 2001-08-06
- Posts: 517
Re: Firefox 3.0 problems
Following a suggestion from someone at MacInTouch, I installed Firefox 3.0 on another user area of my Power Mac G5, and -- presto! -- it works just fine.
So, of course, there's something in my home user area that's screwing up Firefox 3.0 -- but what could it be? And why doesn't whatever the culprit is also screw up Firefox 2.0.0.14, which runs like a champ?
More investigation is needed -- all suggestions are welcome.
Offline
#7 2008-06-18 8:34 pm
- kamizuno
- Poking you with a stick
- From: Smileytown
- Registered: 1999-07-13
- Posts: 1987
Re: Firefox 3.0 problems
Corrupt font? actually, the user Library folder has like a zillion files in it, so I have no real idea what's causing your problem, just throwing ideas out there 
Offline
#8 2008-06-18 8:49 pm
Re: Firefox 3.0 problems
Here is a possible fix:
In a terminal window enter all in one line (copy paste):
For Leopard
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
For Tiger
/System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
Hit return, wait for the normal prompt and restart.
Caveat= many apps after the kill think you are starting them for the first time.
Computers never do what you want them to do; only what you tell them to do.
Offline
#9 2008-06-18 9:04 pm
Re: Firefox 3.0 problems
It's also possible that the display problems have something to do with the 209 errors in the xhtml on the maclife.com home page. (For reference, jslint stops attempting to validate the document's javascript before it's finished validating 1% of the document).
Your own site has 24 xhtml errors. That's not uncommon, but I would correct the xhtml before blaming Firefox.
The javascript on your site also does not validate using jslint.
Offline
Get it
Stack it!
#12 2008-06-18 11:57 pm
- Rik
- Unemployed Guy
- Administrator
- From: San Francisco CA USA
- Registered: 2001-08-06
- Posts: 517
Re: Firefox 3.0 problems
matt wrote:
Your own site has 24 xhtml errors. That's not uncommon, but I would correct the xhtml before blaming Firefox.
Dy-no-mite! I'll clear those errors and check again -- but the question still remains as to what changed between Firefox 2.0.0.14 and 3.0 that caused the screw-ups to surface, and why do they appear on Firefox 3.0 launched from my user area, and not from other user areas on the same Power Mac? And why don't they appear on other Macs running Firefox 3.0? It still seems more likely that there's some Badness™ in my user Library that I need to track down -- too bad that I have 52,348 files in that Library...
But I'll try the XHTML fixes (most are pretty minor) and see if that helps.
Thanks.
Offline
#13 2008-06-19 12:09 am
- Rik
- Unemployed Guy
- Administrator
- From: San Francisco CA USA
- Registered: 2001-08-06
- Posts: 517
Re: Firefox 3.0 problems
Basil wrote:
Here is a possible fix:
In a terminal window enter all in one line (copy paste):
For Leopard
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
For Tiger
/System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
Hit return, wait for the normal prompt and restart.
Caveat= many apps after the kill think you are starting them for the first time.
I'd feel a bit more comfortable doing this if you'd explain what it actually does -- and although I'm used to using kill with a PID as an argument, what's with the -domain local -domain system -domain user argument? I don't see those processes when I run top.
(Yeah, okay, so I'm advertising my ignorance...)
Offline
