266963 - Webpage designed in Frontpage 2003 does not display properly (Photogallery)

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Robert Thomson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

My webpage is created in MS Frontpage 2003.  The photogallery does not display
properly.  Scroll arrows are missing. Browse the page and see for yourself.

Keep up the good work on Firefox!

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Hermann Schwab]

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041029

I don´t see the arrows, but I´ve got scrollbars, see 10 images in a row, and the
one clicked gets displayed in normal size below.
Frontpage generated code isn´t valid HTML, see http://validator.w3.org/

http://validator.w3.org/check?uri=http%3A%2F%2Fpersonal.nbnet.nb.ca%2Fthomsonr%2Fphoto.htm

excerpt from the source code:
<picture file-href="photogallery/photo00000085/real_p.htm" />
<picture file-href="photogallery/photo00000085/real_x.htm" />
<div align="center">
<center>

<layer visibility="hide">
<div style="display:none;" id="fpGalleryCaptions_7799">

http://personal.nbnet.nb.ca/thomsonr/photogallery/photo00000085/real_p.htm
is showing the arrows, but it isn´t loaded, as the lines above are not valid HTML.

testing with Opera 7.54:
masked as IE6.0: somehow working
masked as Opera: Arrows shown, not working
masked as Mozilla: no Arrows seen

Comment 2

[Ben Fowler]

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041031
Firefox/0.9.1+

It is kind of you to mention that you used MS Frontpage to create
your HTML-like document.

I think that I am seeing the same as the other commenter, and it is probably
the best that can be done with a standards-conforming browser.

Have you tried the photo gallery features of Drupal http://www.drupal.org/  
though I have to admit that the learning curve for that CMS is quite long?

Comment 3

[Boris Zbarsky [:bzbarsky]]

Given that the same browser with different user-agent strings set renders the
page differently, it seems the page itself does different things depending on
what it thinks the browser is.

Marking invalid, based on that. We can't do much about a page that purposefully
doesn't show content in our browser...