Firefoxy!
where to begin... well, so, long ago, i had posted that i didnt like 1.5, preferring 1.0.7 as it correctly rendered text across everypage i visited. i uninstalled, and went back, only to return to 1.5 some weeks later with the original issue still persistent.
since safari registered pages correct (unlike this blog in firefox, as compared to news.google.com, which correctly rendered exactly the same in both safari and firefox), i assumed this was a firefox issue. quite simply heres what happened: composing html would make my cursor get further and further ahead of where i was really typing, so if i had to backspace or move the cursor, is was impossible to tell where it really was (so if you had it blinking inbetween the T and W of inbetween, it would really be somewhere near the I). it would also give this extra spacing to paragraph text, and overlap text that had, say, a bold or italics tag on it, with adjacent, plain text. very annoying, not to mention hard to read.
finally, some research found the solution: somehow, during upgrades (of specifically 10.3 to 10.4), the system duplicates seemingly random fonts, which need to be "resolved" in order for BOTH safari and firefox to render correctly. this can be done by opening Font Book, command selecting all the bulleted fonts (that means there are duplications somewhere within) and going Edit > Resolve Duplicates.
the bbs seem to say this is a rare problem, but documented enough that this solution is known. now, i am happy, and i can correctly finetune the css for the blog (and site) to what is REALLY going on...
since safari registered pages correct (unlike this blog in firefox, as compared to news.google.com, which correctly rendered exactly the same in both safari and firefox), i assumed this was a firefox issue. quite simply heres what happened: composing html would make my cursor get further and further ahead of where i was really typing, so if i had to backspace or move the cursor, is was impossible to tell where it really was (so if you had it blinking inbetween the T and W of inbetween, it would really be somewhere near the I). it would also give this extra spacing to paragraph text, and overlap text that had, say, a bold or italics tag on it, with adjacent, plain text. very annoying, not to mention hard to read.
finally, some research found the solution: somehow, during upgrades (of specifically 10.3 to 10.4), the system duplicates seemingly random fonts, which need to be "resolved" in order for BOTH safari and firefox to render correctly. this can be done by opening Font Book, command selecting all the bulleted fonts (that means there are duplications somewhere within) and going Edit > Resolve Duplicates.
the bbs seem to say this is a rare problem, but documented enough that this solution is known. now, i am happy, and i can correctly finetune the css for the blog (and site) to what is REALLY going on...
Post a Comment
<< Home