Closed
Bug 5629
Opened 25 years ago
Closed 23 years ago
[LAYER] can't access style elements via document.ELEMENTNAME
Categories
(Tech Evangelism Graveyard :: English US, defect, P2)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: desale, Assigned: bc)
References
Details
Can not access style elements.
Product: Seamonkey [Apprunner/Viewer]
Build: 04-27-13.
Platform: PC.
OS: Windows-95.
Steps to Reproduce Bug:
1] Please copy HTML code I'm providing, and save as HTML file.
2] Open this HTML file in apprunner as well as viewer.
3] You'll see one division on upperleft corner called "I'm mover.."
4] You'll see some othe div's also. Then there is one Text box called "Result
Text Box".
5] Then there are three buttons "Check Div top", "Check Div Left", and "Reset".
6] Click first two buttons one by one, click as many times you want.
7] Reset button is for resetting the text box.
Expected Results: After clicking button "Check Div top", the "Result Text Box"
should show the top of div which is set to "9" in style "mover".
Again after clicking button "Check Div Left", the "Result Text Box" should show
the left of div which is set to "20" in style "mover".
Actual Results: "Result Text Box" does not show ant values.
Code:
<html>
<head>
<title>Test Page</title>
</head>
<SCRIPT LANGUAGE="JavaScript1.1">
function report(text)
{
var value=document.workform.result.value;
var msg= value+ " " +text;
document.workform.result.value=msg;
}
</SCRIPT>
<SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript">
<!--
if (navigator.platform)
{
if (navigator.platform.substring(0,3) == "Mac")
{
if (navigator.appName == "Microsoft Internet Explorer")
{
document.writeln('<LINK TYPE="text/css">');
document.writeln('#mover {position: absolute; left: 20; top: 9;
font-size:36pt;}');
document.writeln('</LINK>');
}
else if (navigator.appName == "Netscape")
{
document.writeln('<LINK TYPE="text/css">');
document.writeln('#mover {position: absolute; left: 20; top: 9;
font-size:36pt;}');
document.writeln('</LINK>');
}
}
else if (navigator.platform.substring(0,3) == "Win")
{
if (navigator.appName == "Microsoft Internet Explorer")
{
document.writeln('<STYLE TYPE="text/css" >');
document.writeln('#mover {position: absolute; left: 20; top: 9;
font-size:36pt;}');
document.writeln('</STYLE>');
}
else if (navigator.appName == "Netscape")
{
document.writeln('<STYLE TYPE="text/css" >');
document.writeln('#mover {position: absolute; left: 20; top: 9;
font-size:36pt;}');
document.writeln('</STYLE>');
}
}
}
//-->
</SCRIPT>
<body >
<Div ID="mover">I'm mover...</Div>
<Div ID="mover1">I'm mover1...</Div>
<Div ID="mover2">I'm mover2...</Div>
<Div ID="mover3">I'm mover3...</Div>
<Div ID="mover4">I'm mover4...</Div>
<form name="workform">
Result Text Box:<INPUT TYPE=text name="result" size=60><br><br>
<input type="button" name"b1" value="Check Div Top"
onClick="report(document.mover.top);">
<input type="button" name"b1" value="Check Div Left"
onClick="report(document.mover.left);">
<input type="reset" value="Reset">
</form>
</body>
</html>
|
Reporter | |
Updated•25 years ago
|
QA Contact: 4015 → 4616
|
||
Comment 1•25 years ago
|
||
Well...this probably works in 4.x for a couple of reasons:
1) Positioned elements in 4.x were reflected as Layers. Currently, we don't have
complete support for layers (and may not for 5.0).
2) I believe the ID attribute could be used to reference an element directly by
name off the document only for layers. For backwards compatibility we do support
the referencing of forms, images, layers, embeds and applets by their NAME
attribute value.
Either way, this goes along with the rest of the layers bugs that may or may not
be fixed for 5.0.
Status: NEW → ASSIGNED
Summary: Can not access style elements. → [LAYER]Can not access style elements.
Target Milestone: M9
|
|
||
Updated•25 years ago
|
Assignee: vidur → ekrock
Status: ASSIGNED → NEW
|
|
||
Comment 2•25 years ago
|
||
Assigning all layers bugs to ekrock.
|
||
Updated•25 years ago
|
Status: NEW → ASSIGNED
|
|
||
Updated•25 years ago
|
Target Milestone: M9 → M15
|
|
||
Comment 3•25 years ago
|
||
Setting all LAYER bugs to M15 for as-time-allows evangelism.
|
|
||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → LATER
Summary: [LAYER]Can not access style elements. → [LAYER] can't access style elements via document.ELEMENTNAME
|
|
||
Comment 4•25 years ago
|
||
Interesting question of whether we should expose named elements as
document.ELEMENTNAME as a DOM extension for a bit of backward compatibility.
Marking LATER for possible later consideration but we probably won't have time
to implement nonstandard access convention extensions for FCS.
LATER. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav5. Closed.
Notified reporter and site owner via template at
http://sites.netscape.net/ekrock/fixit/layer.html
In the future, if possible, please INVALID, notify, and close such bugs directly
using that template without assigning to me. Thanks!
|
|
Reporter | |
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
|
|
Reporter | |
Comment 5•25 years ago
|
||
[LAYER] Bug. Marking Verified.
|
|
||
Comment 6•24 years ago
|
||
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: ekrock → nobody
Status: VERIFIED → NEW
Component: DOM Level 1 → Evangelism
Keywords: evangwanted
QA Contact: desale → nobody
Target Milestone: M15 → ---
|
|
||
Updated•24 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: LATER → INVALID
|
|
||
Comment 7•24 years ago
|
||
Closing all Evangelism bugs where no evangelism is needed because page has been
fixed, site is internal to Netscape, report is a DUP, or bug report is no longer
appropriate for evangelism for any other reason.
|
||
Comment 8•24 years ago
|
||
SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for
this component.
Sorry about the spam
zach
QA Contact: nobody → zach
|
||
Comment 9•24 years ago
|
||
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
|
|
||
Comment 10•24 years ago
|
||
workaround bugzilla problem that caused a bunch of evangelism bugs to be
NEW/INVALID, NEW/FIXED, NEW/WORKSFORME or NEW/DUPLICATE
Resolution: INVALID → ---
|
|
||
Updated•24 years ago
|
Severity: normal → major
Status: NEW → ASSIGNED
OS: Windows 95 → All
Priority: P3 → P2
Hardware: PC → All
Target Milestone: --- → mozilla0.6
|
|
||
Comment 11•24 years ago
|
||
-> evangelism@telocity.com for my evangelism bugs.
removing the now-depreciated evangelism-related keywords.
setting platform to All.
|
||
Updated•24 years ago
|
Target Milestone: mozilla0.6 → Future
|
|
||
Comment 12•23 years ago
|
||
Reassigning evangelism bugs to bclary@netscape.com.
Assignee: evangelism → bclary
|
|
||
Comment 13•23 years ago
|
||
This is notabug
Status: NEW → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → INVALID
|
Assignee | |
Comment 15•23 years ago
|
||
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Target Milestone: Future → ---
Version: other → unspecified
|
||
Updated•9 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•