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
Last Resolved: 20 years ago
Resolution: --- → FIXED
Target Milestone: M6
Fixed with latest checkin.
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.
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.