Closed
Bug 62280
Opened 25 years ago
Closed 25 years ago
Cells with a class= tag containing only don't show background.
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
CLOSED
WORKSFORME
People
(Reporter: jason, Assigned: shanjian)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i586; en-US; m18) Gecko/20001206
BuildID: 2000120608
I have table cells that are defined as such:
<td wdith="100" class="colorclass"> </td>
Colorclass sets the background color to various colors. It works correctly when
I enter text or a graphic as the contents of the column. However if the only
contents of the column is an the background becomes the same as the
page's and not the colors that were assigned by the style sheet. I spoke with
some people on #mozillazine and a person with 2000-12-06-08 could see the same
problem but a user with 2000-12-05-08 saw the page correctly. I tried with M18
and got the same problem. I would suggest this is some regression problem.
Netscape 6 seems to show it correctly.
Reproducible: Always
Steps to Reproduce:
1.View http://ussdenmark.tranzor.net. At the top, there should be a horizontal
red bar the entire way acrosss.
2.What I see can be found at http://mail.packetwarriors.net:3000/moz-shot1.png.
3.Also, http://bfsearch.tranzor.net has the same CSS with red backgrounds and
the left side of the red border is not there for me.
Actual Results: As described aboved.
I don't know what else you would wnat. You can e-mail me at
jason@packetwarriors.net if I haven't been clear.
Comment 1•25 years ago
|
||
Adding regression keyword. OS -> All since it apparently occurs on NT too.
Keywords: regression
OS: Linux → All
Comment 2•25 years ago
|
||
I am seeing this too:
Platform: PC
OS: Windows 98
Mozilla Build: 2000120604 M18 Trunk Build
Marking as NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•25 years ago
|
||
Note that the testcases from bug 41959 are shown correctly in 2000-12-07-08. so
this is not just a recurrence of that bug.... Over to HTML tables and
reassigning to owner of bug 41959.
Assignee: asa → shanjian
Component: Browser-General → HTMLTables
| Assignee | ||
Comment 5•25 years ago
|
||
Could not reproduce the problem, it works fine on my NT. (I just
update my source tree today.) If you still see the problem, reopen
the bug and I will take a look. Please attach the testcase and marked
screen snap, in case we might have different interpretation of the
right behavior. (I also tried it on IE, but could not see any difference.)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Comment 6•25 years ago
|
||
Comment 7•25 years ago
|
||
The attached file shows a definite problem for me with Linux. Attaching
screenshots of Netscape and Mozilla renderings.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 8•25 years ago
|
||
| Assignee | ||
Comment 9•25 years ago
|
||
It works fine on both my NT and Linux. Both source tree are updated today.
Please try the latest build.
Status: REOPENED → ASSIGNED
Comment 10•25 years ago
|
||
I am seeing this problem in a debug linux build from source pulled at "Tue Feb
6 19:09:42 EST 2001"
| Assignee | ||
Comment 12•25 years ago
|
||
I tried on several machines, but could not reproduce the problem. I just
did it one more time on my winnt, I download build 2001022209, and everything
works fine.
If you still experience the problem, could you look a little further and
probably try someone else's env.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Comment 13•25 years ago
|
||
Both the testcase and the original page now work for me too, with build
2001-02-22-13 on Linux.
Jason, could you please test it too and verify if it works for you?
Severity: normal → blocker
Comment 14•25 years ago
|
||
no idea how severity got reset.... but setting it back.
Severity: blocker → normal
| Reporter | ||
Comment 15•25 years ago
|
||
It looks good to me too. Thanks guys for the fix.
Status: RESOLVED → CLOSED
You need to log in
before you can comment on or make changes to this bug.
Description
•