Closed Bug 4892 Opened 26 years ago Closed 26 years ago

background attribute of table element not supported, but NOVA does

Categories

(Core :: Layout: Tables, defect, P3)

Product:
Core
Component:
Layout: Tables
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: cmaximus, Assigned: karnaze)

References

(
URL
)

Details

Using background=" " in a <table> declaration is not supported by Gecko. The DTD backs this up and recommends use of CSS instead. Nova however, supports this extension perfectly. e.g. <table border="0" bgcolor="#FEFEFE" background="http://yaddayadda.com/images/pic.gif"> or some such. See testcase above. This example was enocuntered at www.t-online.com or www.t-online.de
QA Contact: 3847 → 4130
Assignee: rickg → karnaze
Given that this is not standard, does not appear to be supported in IE, and is replaceable by CSS, I'm not inclined to satisfy this feature request. However, I'll forward it to our table guy in case he *really wants to be nice to you*. (Chris -- feel free to pass). I would, however, like to know why you claim this is a parser bug.
1. Not standard. Given 2. I thought we were trying to be backwards compatible with Nova when possible? 3.* IE suports this just fine, check the test case.* 4. There are tons of things replaceable by CSS, we're not scrapping them all are we? Items 2+3 together should weigh in this item's favor.
tested with 1990408 Seamonkey builds, Nova RTM's, and IE50 on WinNT
Status: NEW → ASSIGNED
Component: Parser → HTMLTables
Target Milestone: M6
The background-color:inherit rule for a <td> in ua.css is causing this. I need to remove nav quirks from the ua.css and put them in the code per Peter's suggestions. <HTML> <BODY> <table bgcolor=orange background="raptor.jpg"> <TR><TD>XXXXXXXXXXXXXX</TD></TR></Table> </body> </html>
Moving to M8.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed with latest checkin.
Status: RESOLVED → VERIFIED
I've VERIFIED it works on Linux, WinNT(1999061108) and Mac(1999060808).
You need to log in before you can comment on or make changes to this bug.