Re: Safari/Firefox compatibility

visitme@xxxxxxxx wrote:

I have now done everything possible I can think of to get the site
working but the navigation bar on http://www.stoykova.eu/ still does not work under Firefox.

One thing that's always possible to think of is validation, through which you can often remove syntactic errors which keep your page from working the way you expect. A valid page might still not work the way you *want*, but that's a different problem.)

(X)HTML: http://validator.w3.org/(15 Errors, 1 warning)
CSS: http://jigsaw.w3.org/css-validator/ (1 error, 10 warnings)

If it's any help, here is the style.css file:

Well, we've got the page URL, so we can get the CSS. But what's below is not all of the styling, because some of it is duplicated in CSS embedded in the page. So when you try tweaking the navigation styling, what happens?

------------------------------------------
/*
Author : Christopher Robinson
Email : christopher@xxxxxxxxxx
Website : http://www.edg3.co.uk/

If you're having trouble with somebody else's CSS, why not ask *him*?

#header_inside h3 {
margin:-20px 0 0 -5px;
position:absolute; <- Do you really need this?
width:122px;
}
/* navigation */
#navigation {
left:50%;
margin:0 0 0 -61px;
position:absolute; <- Do you really need this?
width:122px;
}


/*content */
#content {
left:50%;
margin:0 0 0 -400px;
position:absolute; <- Do you really need this?
width:800px; <- This is stretching across and over your nav
}


In general, I don't see the need for all the absolute positioning. One argument against it is the way the page breaks when the user resizes the fonts. The other argument against is that problems crop up so easily (you know, like the ones you're having).


----------------------------------------------------------------
The W3C Markup validator does still show a few errors, although it is
not entirely clear to me why they are classed as errors. Any further
suggestions would be very much appreciated!

Ah, so you *have* thought of validation! ;-)

Well, most should be obvious, I'd have thought, although the messages can be a bit terse. First of all, I would point to the fact that you're attempting to use XHTML (see your doctype), but then serving it as text/html, and using upper-case elements and non-existent attributes.

One oft-heard reasoning for using XHTML is because "it's modern", but you're also using <font> (or, no better, <FONT>), which isn't valid in HTML 4.01, much less XHTML. And if you're using CSS already anyway, let it do the work of your misplaced <font> elements.

Summary: Change to HTML 4.01 strict, and work through the remaining validation errors one by one. See also http://tekrider.net/html/doctype.php and follow the links.

As for why markup errors are errors, you can peruse the source definitions, if you haven't already:
http://www.w3.org/TR/xhtml1/ for XHTML
http://www.w3.org/TR/html401/ for HTML

If you still have questions about a specific error message, bring it on back here.

One last unrelated item I noticed:
Apart from demanding a font-size that's smaller than your users' preferences, your font stack is a bit messed up in the line

font:0.9em Arial, Helvetica, sans-serif, "bitstream vera sans";

If the visitor's UA doesn't have Arial, or Helvetica, or *any* sans-serif font, what good will "bitstream vera sans" do?

HTH. GL.

--
John (Hosking)
Pondering the value of the UIP: http://improve-usenet.org/
.

Relevant Pages

  • Re: Opera guesses encoding for "application/xml"
    ... Do you dispute the fact that XML Schema validation is more powerful than ... powerful" than HTML DTD validation? ... how to change non DTD constraints, ... extra constraints that XHTML requires, ...
    (comp.infosystems.www.authoring.html)
  • Re: problem with validated site
    ... However, while I'm by no means an expert or professional website designer, I know enough about XHTML 1.0 to know that the best way to guarantee interoperability on all, or at least most browsers, including lynx is to make sure my site complies with the w3 standards. ... I'm not sure why the different paragraphs all have different fonts, when I can't even see a tag. ... They shouldn't appear in a normal POSH (Plain Old Semantic HTML or XHTML) and are the mark of CSS designer whose target is a specific visual presentation, ...
    (comp.infosystems.www.authoring.html)
  • Re: XHTML validation
    ... You seem to have gotten rid of the validation errors at the moment as ... even if your code is perfect xhtml, it is only being served as html, ... To serve as true xhtml, you would need to associate some ... work on most recent browser as they will handle true xhtml. ...
    (alt.html)
  • open email to the W3C
    ... Rendering could start long before the ... The binary format would be so designed to give you ... downloaded from the font foundries and cached. ... used interchangably with the markup XHTML. ...
    (comp.lang.java.advocacy)
  • Re: Javascript Best Practices Document v1.0
    ... that document.formsis a bad practice when it is a DOM 2 HTML valid practice in XHTML ... client-side form validation), then use an id attribute, or pass references directly and omit an identifier entirely. ... There is no general rule for returning false in a script, ...
    (comp.lang.javascript)
Loading