233433 - DIV seems to display one line below the proper location in layout

Status: RESOLVED DUPLICATE of bug 94468

(Core :: DOM: HTML Parser, defect)

Description

[Bill Davis]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007

In the layout, the "State" falls on the form, not above it.  It works properly
in NetScape 7 and IE6.  I have the same problem with Mozilla 1.4.  It appears to
be related to the display of a DIV command.  The specifics for DIV are not clear
at w3 and it appears that is should work - but seems to insert a break in error.
 I use it anyway, but thought a report was appropriate.  I will try with M1.6
after I get it downloaded.

Reproducible: Always
Steps to Reproduce:
1.  Simply open http://www.familysearch.org/Eng/Search/frameset_search.asp.
2.  Look at lower rigth of form
3.  "State" is in form field and should be above (in fact it should probably be
missing since the USA has not been highlighted.

Actual Results:  
The display error appears.  If I change the country to Canada, the display
should become Provinces, but does not.  I have reveiwed the code carefully and
can not find any error.  The LDS unfortunately uses FrontPage for much of their
web work and ends up with a lot of errors as a result.  The main reason to
report is that it works fine in both N7 and IE6, but not any of my Mozilla versions.

Expected Results:  
The lower right form field should have nothing or "State" or "Province" above
the field.  Instead, "State" is displayed in the field on top of the actual
field data.

Comment 1

[Boris Zbarsky [:bzbarsky]]

> I have reveiwed the code carefully and can not find any error.

document.all is an IE-specific object.

document.layers is an NS4-specific object.

Your page assumes that one or the other exists.  That's not the case in Mozilla.

You really want to use document.getElementById instead...  There's no way the
visibility-switching code on that page can possibly work with NS7; does the
server send different source for NS7?

All that said, this looks like bug 94468.  Marking duplicate, but please do
reopen if this is a problem in 1.6... (I can't reproduce the div positioning
problem in a current build).

*** This bug has been marked as a duplicate of 94468 ***