On Tuesday, Aug 17, 2004, at 09:38 Australia/Sydney, Seona Bellamy wrote:
I have a couple of issues with the site I'm working on. They have been
reported by the client, and I'm having trouble reliably replicating any of
them so I can't work out how to fix them.
Can someone please take a look at http://216.119.123.23/ and look for the
following errors:
* On pages like About Us and Contact Details, the centre banner apparently
stays stuck at the top of the screen (i.e., the content of the page
disappears under it as you scroll, and it's always on screen). Does anyone
else get this problem? I don't. More importantly, if anyone else does, how
do I make it stay in place?
Sounds like an issue with position: fixed. There again, if by 'centre banner' you mean the Flash file, it doesn't validate... Suggest you search the archive on this list for valid ways to include Flash files, or look for Flash Satay at A List Apart.
* If you browse the catalogue, sometimes the product listings don't come up
straight away. The page loads, finishes loading, and expands to its required
height, but the content doesn't show up until you roll your mouse over a
link. Then it magically pops into view. I only get this problem sometimes,
they apparently get it all the time, and I can't figure out why it's
happening.
Sounds like either the Peekaboo or Guillotine bug. See http://www.positioniseverything.net/ for fixes.
* In the View Details page for any of the products, there should be an
Enquire Now button. It's there on mine. It's not there on the client's. They
don't believe that it's really there at all, in spite of the fact that I can
look in the code and see it.
I presume the button is a form element. Form elements are really touchy in XHTML. Again, search the archive for clues.
Difficult to be any more precise without info on what browser you're developing/testing on, and what browsers are showing the problem. Also, step one should *always* be to validate your code. You'll be chasing your tail for days, otherwise.
If your client is seeing glitches with an old, non-compliant browser, suggest to him that he updates it. If he objects on the basis that some visitors will still get the problem show him how small the percentage is of visitors to his site who are actually using the old/bad browser - I bet it's tiny.
If that doesn't work, stop trying to use XHTML. HTML4 is perfectly valid, and can still be Standards-compliant. We don't *have* to use XHTML; design and usability should come first. See http://www.zeldman.com/daily/0804b.shtml for an interesting take on this.
HTH
Nick ___________________________ Omnivision. Websight. http://www.omnivision.com.au/
****************************************************** The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
