Closed Bug 25918 Opened 25 years ago Closed 23 years ago

[LAYER] styles in the middle of forms don't work

Categories

(Tech Evangelism Graveyard :: English US, defect, P3)

Product:
Tech Evangelism Graveyard
Component:
English US
Platform:
All
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: ec, Assigned: bc)

Details

I have a simple form with 2 buttons and a <SPAN> tag in between.  I want to 
alter the contents of the tag as the user clicks on the buttons and in IE this 
works but under NN 4.7 I get one of two problems: if the position is "absolute" 
the second button does not show up while if the position is "relative" the 
javascript to update the tag stops working!!  can anyone help?  here's the code:

<html>
<body><form action="" method="post" onSubmit="return false">
<input type="submit" value="this" onClick="show(this.value)">
<span id="stat" STYLE="position: relative; left: 10; top: 50">Status...</span>
<input type="submit" value="that" onClick="show(this.value)">
</form>
<script>function show(s) {
if (document.layers != null) {
                var o = document.layers["stat"];
                o.document.open();
                o.document.write(s);
                o.document.close();
                }
        else
                {
                stat.innerText = s;
                }
        }
</script>
</body>
</html>
ec@arix.com, you should be able to do what you want, but not the way you are 
doing it. Mozilla and Navigator 5 will support only W3C standards for DOM and 
js; document.layers[] in particular will not be supported.

See
http://sites.netscape.net/ekrock/standards.html and 
http://sites.netscape.net/ekrock/answers.html for more details.

Marking INVALID.
Status: NEW → RESOLVED
Closed: 25 years ago
Component: Javascript Engine → DOM Level 1
QA Contact: rginda → gerardok
Resolution: --- → INVALID
Summary: styles in the middle of forms don't work → [LAYER] styles in the middle of forms don't work
Ah. the best resource is http://sites.netscape.net/ekrock/fixit/layer.html

And marking VERIFIED per request from ekrock@netscape.com in bug 19500.
Status: RESOLVED → VERIFIED
thank you for the response BUT I'm not using Navigator 5.  I'm using 4.7 (your 
bug report page didn't allow me to enter the version number but I did state 
that in my message).  Your response stated I can do what I want but not the way 
I want to do it.  Can you please elaborate?
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
The bugzilla bug database is for problems with the Mozilla product, also known
as 5.0.  For bugs with the 4.x codebase, see 

http://help.netscape.com/forms/bug-client.html

Marking as INVALID for mozilla.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
and VERIFYing again.

The three links above will fill you in; I don't know any js myself.
Status: RESOLVED → VERIFIED
Additionally I didn't mention that I've tried it with <LAYER> and <DIV> with 
similar results, even causing Netscape to crash (GPF) when I press the 
buttons.  I've read a lot about CSS but I have not found a example of precisely 
what I want to do.  any suggestions greatly appreciated.
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
Ah, I'm in the wrong place.  sorry.  I've closed the case here.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
Moving all [LAYER] bugs to Evangelism component for tracking and open-source
evangelism by mozilla community members of sites that need to upgrade to support 
web standards such as HTML 4.0 (instead of LAYER/ILAYER) and the W3C DOM
(instead of Nav4 document.layers[] or IE document.all()). Sites should be
lobbied to do the upgrade using the email templates that are linked to from
http://www.mozilla.org/newlayout/bugathon.html#layerbugs . When a site's owner
has confirmed receipt of the message requesting an upgrade, the bug should be
marked with the keyword evangelized to indicate that evangelism for that bug is
complete. When the site finishes the upgrade and supports standards, the bug
should be closed.
Assignee: mccabe → nobody
Status: RESOLVED → NEW
Component: DOM Level 1 → Evangelism
Keywords: evangwanted
QA Contact: gerardok → nobody
No URL. Closing. Clearing cc:s as a courtesy to reduce spam.
Status: NEW → RESOLVED
Closed: 25 years ago → 24 years ago
QA Contact: nobody → zach
SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for 
this component.

Sorry about the spam

zach
Reassigning Evangelism bugs to me, the component's new owner.  I would like to 
take this opportunity to thank nobody@mozilla.org for all of his dedication, 
contributions, and hard work, and wish him luck at his new job.  Thanks, nobody.
Assignee: nobody → BlakeR1234
Status: RESOLVED → NEW
workaround bugzilla problem that caused a bunch of evangelism bugs to be 
NEW/INVALID, NEW/FIXED, NEW/WORKSFORME or NEW/DUPLICATE
Resolution: INVALID → ---
-> evangelism@telocity.com for my evangelism bugs.

removing the now-depreciated evangelism-related keywords.

setting platform to All.
Assignee: blakeross → evangelism
Keywords: evangwanted
Hardware: PC → All
Reassigning evangelism bugs to bclary@netscape.com.
Assignee: evangelism → bclary
doesn't need evang because there is nothing to evang!
Status: NEW → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → WORKSFORME
no url
Status: RESOLVED → VERIFIED
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.