Closed Bug 270979 Opened 20 years ago Closed 19 years ago

inconsistent handling of text-decoration with input type=button and img alt text

Categories

(Firefox :: General, defect)

x86
Windows 98
defect
Not set
trivial

Tracking

()

RESOLVED INVALID

People

(Reporter: charonme, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

standards mode. text-decoration:underline applied to input type=button and img
elements

the button text is not underlined but the alt text of an image is underlined.
according to the discussion on bug #219516 they have to be handled the same way,
ie. both not underlined or both underlined.

Reproducible: Always
Steps to Reproduce:
0. read the discussion on bug 219516
1. go to http://www.charon.sk/button_underline_test.htm
2. check whether the button text and the img alt text is underlined


Actual Results:  
button text is not underlined, img alt text is underlined

Expected Results:  
they either have to be both underlined or both not underlined
So how is this bug different from the one you already filed (Bug 270379) and was
duped to bug 219516?
sorry about confusion.
I was told the behavior of the input button is expected, ie not a bug. but if
this is true, then the behavior of the alt text of an image is an bug, because
the text (which is not a text) has to be rendered the same way as the button
text, but it isnt.

however, if the button text should be underlined and if it is a bug indeed, than
the underline applied to the img alt text is NOT a bug and this report (270979)
is obsolete.
This problem also exists with <button> tag!
The button tag contains text (as a child).

Image alt text is just text and should be treated as such.  In particular, an image replaced by alt text is NOT a replaced element anymore.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.