From 2c77a0edc34a6e87ff8d207997d3abc1246f5f8a Mon Sep 17 00:00:00 2001 From: "dbaron%dbaron.org" Date: Tue, 30 Nov 2004 05:52:59 +0000 Subject: [PATCH] Fix col/colspan confusion (regression). b=107453 r+sr=bzbarsky git-svn-id: svn://10.0.0.236/trunk@165931 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/content/html/content/src/nsHTMLTableColElement.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/mozilla/content/html/content/src/nsHTMLTableColElement.cpp b/mozilla/content/html/content/src/nsHTMLTableColElement.cpp index 75ae1b37bf1..5608f5cf305 100644 --- a/mozilla/content/html/content/src/nsHTMLTableColElement.cpp +++ b/mozilla/content/html/content/src/nsHTMLTableColElement.cpp @@ -247,17 +247,16 @@ nsHTMLTableColElement::IsAttributeMapped(const nsIAtom* aAttribute) const static const MappedAttributeEntry* const col_map[] = { attributes, + span_attribute, sCommonAttributeMap, }; static const MappedAttributeEntry* const colspan_map[] = { attributes, - span_attribute, sCommonAttributeMap, }; - // we don't match "span" if we're a - // XXXldb Should this be reflected in the mapping function? + // we only match "span" if we're a if (mNodeInfo->Equals(nsHTMLAtoms::col)) return FindAttributeDependence(aAttribute, col_map, NS_ARRAY_LENGTH(col_map));