Closed
Bug 299723
Opened 20 years ago
Closed 19 years ago
[FIXr]Table attribute RULES doesn't seem to recognize "none" and other values work strangely
Categories
(Core :: Layout: Tables, defect, P1)
Core
Layout: Tables
Tracking
()
VERIFIED
FIXED
mozilla1.8beta3
People
(Reporter: surrano, Assigned: bzbarsky)
References
()
Details
(Keywords: regression, testcase)
Attachments
(2 files)
330 bytes,
text/html
|
Details | |
2.35 KB,
patch
|
dbaron
:
review+
dbaron
:
superreview+
asa
:
approval1.8b3+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+ The simple example url works as expected in IE or Firefox 1.0, but produces an unfortunate thin grid in Deer Park Alpha 1. I wonder if it's not a bug but a stricter interpretation of the HTML standard in 1.8, and if so, what is the correct solution? 1. If I use BORDER(>0), FRAME(above) and RULES(none), the frame "above" is correct, but a thin grid around each cell is drawn (that violates RULES=none) 2. If I change RULES to groups or rows, the thin lines disappear, but the frame seems to be overdrawn by two half-thick lines. 3. If I omit BORDER (RULES back to none), there's a thin frame "above" and no other grid lines, but then I can't influence the line width. Reproducible: Always Steps to Reproduce: Create a TABLE with BORDER="10px" RULES="none" FRAME="above" CELLSPACING="0" The latter two are not mandatory, just allows you to see more. Actual Results: got a table with thin grids, contradictory with RULES=none. Expected Results: draw a table without any lines except the thick line above the table.
Updated•20 years ago
|
Component: General → Layout: Tables
Keywords: testcase
Product: Firefox → Core
QA Contact: general → layout.tables
Version: unspecified → Trunk
Comment 1•20 years ago
|
||
This regressed between 2005-04-28 and 2005-04-29: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-04-28+05%3A00%3A00&maxdate=2005-04-29+10%3A00%3A00&cvsroot=%2Fcvsroot Probably a regression from fixing bug 290377.
Blocks: 290377
Comment 2•20 years ago
|
||
Updated•20 years ago
|
Keywords: regression
Assignee | ||
Comment 3•20 years ago
|
||
Actually, this is a regression from bug 155507. The problem is that the table attribute-mapping code is pretty silly; it maps in a computed style for cells based on the table's border no matter what. It used to be that the cell borders got nixed later as part of collapsed border processing here, but that's not happening for rules="none" anymore...
Assignee | ||
Updated•20 years ago
|
Assignee: nobody → bzbarsky
OS: Windows 2000 → All
Priority: -- → P1
Hardware: PC → All
Summary: Table attribute RULES doesn't seem to recognize "none" and other values work strangely → [FIX]Table attribute RULES doesn't seem to recognize "none" and other values work strangely
Target Milestone: --- → mozilla1.8beta3
Assignee | ||
Comment 4•20 years ago
|
||
Attachment #188342 -
Flags: superreview?(dbaron)
Attachment #188342 -
Flags: review?(dbaron)
Attachment #188342 -
Flags: superreview?(dbaron)
Attachment #188342 -
Flags: superreview+
Attachment #188342 -
Flags: review?(dbaron)
Attachment #188342 -
Flags: review+
Assignee | ||
Comment 5•19 years ago
|
||
Comment on attachment 188342 [details] [diff] [review] Fix requesting 1.8b3 approval. This is a quite safe fix for a regression in rendering of tables with rules="none".
Attachment #188342 -
Flags: approval1.8b3?
Assignee | ||
Updated•19 years ago
|
Summary: [FIX]Table attribute RULES doesn't seem to recognize "none" and other values work strangely → [FIXr]Table attribute RULES doesn't seem to recognize "none" and other values work strangely
Updated•19 years ago
|
Attachment #188342 -
Flags: approval1.8b3? → approval1.8b3+
Assignee | ||
Comment 6•19 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•19 years ago
|
||
Gérard, I was just fixing a regression, but did this patch actually fix all the issues in bug 172213?
Blocks: 172213
Comment 9•19 years ago
|
||
Boris, the way I see this: this bug was a duplicate of bug 172213. Either way, as long as the problem is fixed, I don't really care :) I'm using Firefox Deer Park alpha 1 build 20050707 under XP Pro SP2 and do not see the fix when I try attachment 188325 [details] or attachment 101453 [details] or attachment 112626 [details]. I'll definately try with tomorrow's build.
Assignee | ||
Comment 10•19 years ago
|
||
It wasn't quite a duplicate, since bug 172213 is present in Firefox 1.0, and this bug as filed was not. But yes, if you could test with tomorrow's builds, that would be great!
Comment 11•19 years ago
|
||
Excellent work, Boris. attachment 188325 [details], attachment 101453 [details] and attachment 112626 [details] all render expected results with Deer Park alpha 2 rv: 1.8b3 build 20050708 under XP Pro SP2. Thank you :) Marking as VERIFIED
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•