Closed Bug 37608 Opened 25 years ago Closed 25 years ago

hr tag

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: rw263, Assigned: asa)

Details

the hr tag puts a line over images and text. Pages with <hr> or <hr noshade> both work incorrectly. Seems to be the case since the early milestones and still occurs.
rw263@NYU.EDU, please refer to the Bug Writing Guidelines at http://www.mozilla.org/quality/bug-writing-guidelines.html to see the kinds of information that we need in a bug report and consider using the Bugzilla Helper to report future bugs. THe helper can be found at http://www.mozilla.org/quality/help/bug-form.html What build did you test this on. Can you attach a simple testcase or point to a URL that exhibits this problem.
It occurs in all milestones that I've tried (atleast the last 6). I didn't include a test page, because it occured on every page on the net I tested it on. It's quite a common mistake.
rw263@NYU.EDU, Can you post a URL or screenshot or something that demonstrates this problem. What build specifically can you demonstrate this on now. I cannot reproduce this with 4/28 builds under windows or linux. I'm marking this worksforme. If you can provide some demonstration of this problem then please reopen the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Reporter is correct about there being problems with <hr> tags at times, there are multiple issues, and this sounds like a duplicate of several of them. I think you will find your problems described in the following: bug 18754 - "[FLOAT] problems with HRs around floats" bug 34892 - "adding <hr> to left of right-justified image overwrites image" bug 20582 - "[BLOCK] <HR>rules are not obeying the CSS padding of the <BODY>" bug 2590 - "<HR> and <BR> are unstylable!!!" (the latter concerning also the "noshade" option) Since it seems this bug is a "multi-bug" bug, but the problem as such is known, i suggest setting it to "invalid" in stead of WFM.
dark, thanks for the digging on this bug. You're right, invalid is probably correct but I'm going with inertia on this one to avoid a couple of steps and some spam. Verifying.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.