Closed
Bug 1225
Opened 26 years ago
Closed 26 years ago
incremental change to visibility causes "padding" to appear
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Tracking
()
VERIFIED
FIXED
People
(Reporter: kipp, Assigned: buster)
Details
The following html when executed in nglayout causes padding to appear. Just
click on the buttons a few times and you will see what I mean.
<HTML>
<HEAD>
<STYLE type="text/css">
#container1 {
position: absolute;
top: 2in;
left: 2in;
width: 2in
}
#container2 {
position: absolute;
top: 2in;
left: 2in;
width: 2in;
visibility: hidden;
}
</STYLE>
<SCRIPT>
function hide(name) {
var it = document.getElementById(name);
if (null != it) {
it.style.visibility = "hidden";
}
}
function show(name) {
var it = document.getElementById(name);
if (null != it) {
it.style.visibility = "visible";
}
}
</SCRIPT>
</HEAD>
<BODY>
<P>Choose a suspect:</P>
<DIV id="container1">
<IMG alt="Al Capone" width="100" height="100" src="woofer.gif">
<P>Name: Al Capone</P>
<P>Residence: Chicago</P>
</DIV>
<DIV id="container2">
<IMG alt="Lucky Luciano" width="100" height="100" src="raptor.jpg">
<P>Name: Lucky Luciano</P>
<P>Residence: New York</P>
</DIV>
<FORM method="post" action="http://www.suspect.org/process-bums">
<P>
<INPUT name="Capone" type="button" value="Capone"
onClick='show("container1");hide("container2")'>
<INPUT name="Luciano" type="button" value="Luciano"
onClick='show("container2");hide("container1")'>
</P>
</FORM>
</BODY>
</HTML>
Updated•26 years ago
|
Status: NEW → ASSIGNED
Updated•26 years ago
|
Assignee: peterl → kipp
Status: ASSIGNED → NEW
Comment 1•26 years ago
|
||
Clicking on a button causes an assert on nsBodyFrame now. Send it back to me
when that gets resolved.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 2•26 years ago
|
||
2/12/99 build.
Verified.
I am not seeing either of these problems in the current build.
Comment 3•26 years ago
|
||
oops, that should have been noted as verified in the 2/9/99 build
You need to log in
before you can comment on or make changes to this bug.
Description
•