Closed
Bug 56225
Opened 25 years ago
Closed 22 years ago
[H4BTN]<hr> in <button> looks bad, causes button to grow on hover/click
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: jruderman, Assigned: rods)
References
Details
Attachments
(1 file)
|
488 bytes,
text/html
|
Details |
Hover or click any of the buttons in the testcase that contain <hr>. The
button will grow vertically, pushing down any text below the <hr>. An
exception is the button just containing the <hr>, which ends up looking like it
contains three <hr>s but stops growing at that point.
Also note that the <hr>s inside buttons look bad in general. HTML 4 allows
pretty much anything in buttons besides other forms elements, and IE displays
them nicely.
|
Reporter | |
Comment 1•25 years ago
|
||
|
Assignee | |
Comment 2•25 years ago
|
||
wow, that is bad, don't do that :)
I'll have to take a look. futuring for now.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
|
|
Assignee | |
Updated•24 years ago
|
Summary: <hr> in <button> looks bad, causes button to grow on hover/click → [H4BTN]<hr> in <button> looks bad, causes button to grow on hover/click
|
||
Comment 6•24 years ago
|
||
Note:
When the document has a invalid doctype
(<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 //EN">) [validator on w3c.org
sais.. that's not a good doctype :)]
, the buttons _won't_ grow or shrink!
See:
http://www.8ung.at/efu/butest.html
And:
http://www.8ung.at/efu/butestx.html
for more details..
butest.html is a document with the 'invalid' doctype -> works fine
butestx.html is a document with a VALID doctype -> doesn't work fine
... a html page without a doctype also won't work...
|
|
Assignee | |
Updated•23 years ago
|
Priority: P3 → --
|
||
Comment 7•22 years ago
|
||
Testcase seems to be fine in W2K 2003011508. No growing buttons (I did see this
ages ago). FIXED?
|
||
Comment 8•22 years ago
|
||
Works for me on build 2003-01-09-08-trunk
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•