Stylesheets - Mac Safari issue on body text

Author

Mac Safari issue on body text

sanj@paradise.net.nz

2005-05-17, 7:32 pm

Hi all,

My site is located at:

http://www.eastdayspa.com/index.html

I have use these main styles

/* main styles */

html, body {margin: 0;
padding: 0;}

body {color: #4D4D4D;
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
text-align: center;}

body {font-size: 80%;
voice-family: "\"}\"";
voice-family: inherit;
font-size: 80%;}

html>body {font-size: 80%;}

a:link, a:visited {text-decoration: none;
color: #cc6633;}

a:hover, a:active {color: #bdc0a0;}

In Safari when my mouse is over the page the text is pale grey and when
the mouse is off the page it goes black...

Also site just breaks in Mac IE5.2.

Any suggestions?

JD

Sander Tekelenburg

2005-05-17, 11:32 pm

In article <1116364791.108409.113420@g49g2000cwa.googlegroups.com>,
sanj@paradise.net.nz wrote:

[...]

> http://www.eastdayspa.com/index.html

[...]

> In Safari when my mouse is over the page the text is pale grey and when
> the mouse is off the page it goes black...

Take out <a name="top" id="top" /> and the issue is gone in Safari 2.0
under Mac OS X 10.4.1. (No idea which version you were thinking about.)

My guess is you're triggering that bloody awful invention generally
referred to as "quirks mode".

Not sure why though. Your doctype seems to claim strict, yet
<http://validator.w3.org/check?uri=h....com/index.html>
claims to have been fed "valid XHTML 1.0 Transitional". I don't know
what's up with that (I've never bothered learning XHTML - just write
decent HTML). I seem to recall that the *way* in which you serve XHTML
(ContentType="text/html") affects quirks modes triggering. That might be
the issue here. OTOH, I didn't think validators now have quirks mode
implemented too...

Others will know better, I'm sure.

> Also site just breaks in Mac IE5.2.

Because it stupidly doesn't allow the user to define a minimum font size
to protect them from idiocy like "font-size:80%".

Anyway, Mac IE has been dead (no development) for some 3 years now.
Maybe it never even heard about XHTML.

--
Sander Tekelenburg, <http://www.euronet.nl/%7Etekelenb/>

sanj@paradise.net.nz

2005-05-17, 11:32 pm

Thanks Sander - If I remove <a name="top" id="top" /> from each page ,
then my <p><a href="#top" class="top">Back to top</a></p> will not
work. Is thsi what you meant to fix the Safari problem?

Sander Tekelenburg

2005-05-18, 8:23 am

In article <1116380067.363808.17730@g44g2000cwa.googlegroups.com>,
sanj@paradise.net.nz wrote:

> Thanks Sander - If I remove <a name="top" id="top" /> from each page ,
> then my <p><a href="#top" class="top">Back to top</a></p> will not
> work. Is thsi what you meant to fix the Safari problem?

No. I just described the behaviour I saw. I mean that that is, together
with the doctype declaration issue I pointed to, an indicator of what
might be wrong at which end.

As I said, I never bothered with XHTML. From an HTML point of view I'd
say you're opening an anchor without closing it - which is consistent
with Safari's behaviour. The question is whether your XHTML is wrong, or
if Safari is.

If your XHTML is correct (which it is, according to the W3C validator)
and Safari is wrong, then you should not change your XHTML. Instead, you
should report the bug to Safari's developers. If Web developers hide
bugs from everybody, they'lll never get fixed.

Expose those bloody browser bugs. Then maybe some day the Web will be
somewhat useable.

--
Sander Tekelenburg, <http://www.euronet.nl/%7Etekelenb/>

Andreas Prilop

2005-05-18, 7:46 pm

On 17 May 2005 sanj@paradise.net.nz wrote:

> body {font-size: 80%;
>
> Any suggestions?

Remove the idiotic font-size 80% for BODY text!

--
Top-posting.
What's the most irritating thing on Usenet?