Closed Bug 6161 Opened 22 years ago Closed 22 years ago

<frame>-tag: marginheight/marginwidth-properties are ignored

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect, P3)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: kairo, Assigned: karnaze)

References

()

Details

I tried "start.at/kairo" and some local pages, everywhere the same problem
occurred with M5:
All those frameset-documents used "marginheight=0" and "marginwidth=0" in
<frame> tags but Gecko ignored those properties and showed the documents with
margins in those frames.
(I think it should be a "all OS" and "all platforms" bug but i could only test
it with Win95.)
Severity: minor → normal
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Target Milestone: M6
Fixed with latest checkin.
Status: RESOLVED → REOPENED
The behavior really depends on how you have your frameset defined. Looking at
the referenced site, it looks as if the margins are now altered. In a test case
that I put together:

<frameset rows="100, *, 75">
	<frame src=fsa.html name=fsa scrolling=yes marginwidth=0 marginheight=0>
	<frameset cols="100, *">
		<frame src=fsb.html name=fsb scrolling=yes marginwidth=0
marginheight=0>
		<frame src=fsc.html name=fsc scrolling=yes marginwidth=0
marginheight=0>
	</frameset>
	<frame src=fsd.html name=fsd scrolling=yes marginwidth=0 marginheight=0>
</frameset>
</html>

the left margins altered, but the top, right and bottom margins were not. The
content of each frame reference contains dummy text. SHouldn't the top margin be
altered?
I checked this with M6 and saw it work the right way with my own files.
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.