Using 3/31 build on Win 95, Win 98, Win NT, Mac8.5 and Linux. Open the URL using Viewer.exe. There are 3 tables, each containing an image. The first table's image is 300px wide and aligned left (table width is the same). The second table's image is 300px wide and aligned right (table width is the same). The third table's image is 306px wide and has no alignment value assigned to it (table width is the same). The third table is for comparison purposes. Per Kipp, left and right aligned images are hardcoded with a 3px per side margin for navigator compatibility. Expected results: In Nav Quirks mode, you should see the Nav compatibility behavior - the image will push the the first two tables' widths to 306 pixels. In Standard mode the image should NOT push the first two tables' widths to 306 pixels and therefore, the bottom table should extend 6 pixels beyond the first two tables. Actual results: Behavior in Nav Quirks and Standard modes are identical. All three tables extend to 306 pixels in width. Not sure where to categorize this bug - assigned to Layout.

Kipp, this sounds like your bug based on the description, but I can't verify that right now since I can't access slip from home. Please reassign it to me if this is not correct.

ChrisD: Could you attach http://slip/projects/marvin/bugs/image_margin_bug.html ...to this bug so that it can be examined from outside Netscape's intranet? [changed summary line to be more descriptive]

This is a style bug, fixable once the two ua.css files come into being. The STRICT ua.css file should contain nothing special. The COMPAT ua.css file should contain the following: IMG[ALIGN=LEFT], IMG[ALIGN=RIGHT] { margin-left: 3px; margin-right: 3px; } This will solve all problems. [Note: This bug has nothing to do with HTML tables. Reassigning to Layout. This should probably be actually reassigned to Style System.]

See also bug 5146.

The good news: I've removed the hardcode and now the margins are defined in the ua.css. This means that a style-sheet author can override the behavior. There is no such thing as a "strict" ua.css so I'm closing this bug (after all the, style sheet in the spec is informative not mandatory).

Verified fixed.