Closed
Bug 310126
Opened 20 years ago
Closed 20 years ago
alt text doesn't work for "java disabled" state
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 114641
People
(Reporter: ddyer, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728
the alt text prescribed by the referenced official mozilla
testing procedure doesn't work.
Reproducible: Always
Comment 1•20 years ago
|
||
I see only the beginning of the alt text with Seamonkey 1.1a rv: 1.9a1 build
2005092606 and in Firefox 1.4 rv: 1.8b5 build 20050926 under XP Pro SP2 here.
The problem is that the attribute value is not coded correctly, therfore the
testcase is not accurate. This is the code at line 150 (notice the inner double
quotes inside the alt attribute value):
<applet codebase="." code="JitterText.class" width=400 height=80
alt="[The "Jitter Text" Java Applet!]"><param name=BGCOLOR value="000000"><param
name=TEXTCOLOR value="FF0000"><param name=TEXT value="JitterText!">
when it should be
<applet codebase="." code="JitterText.class" width=400 height=80
alt="[The 'Jitter Text' Java Applet!]"><param name=BGCOLOR value="000000"><param
name=TEXTCOLOR value="FF0000"><param name=TEXT value="JitterText!">
The W3C HTML validator also spots the problem.
I can correct the page test.
Comment 2•20 years ago
|
||
I have corrected the webpage code and have removed markup validation errors from it.
In Firefox 1.4 rv: 1.8b5 build 20050926, I now see the alt attribute value. I do
not see the
"The JitterText applet is a spinoff from Sun's ... resumes the animation."
text which the page claims I should be seeing.
In Seamonkey 1.1a rv: 1.9a1 build 2005092606, I do not see the alt attribute
value. So, at least, this part is clearly a bug.
http://www.w3.org/TR/html4/struct/objects.html#adef-alt
What is remaining to do is to verify if there is a duplicate for this.
Comment 3•20 years ago
|
||
Attachment 90614 [details] from bug 114641 pinpoints exactly what this bug is about. So,
resolving as DUPLICATE of bug 114641
*** This bug has been marked as a duplicate of 114641 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
with the current firefox release (1.07), and the corrected test page,
it still doesn't work for me. Also doesn't work in mozilla 1.7.11
that is, the "applet below" box is empty, and the box below that,
showing what you should see, is not duplicated.
BTW, nemesis Internet Explorer doesn't display the "alt" tag
but does, correctly, display the html embedded in the applet
body.
Comment 5•20 years ago
|
||
> with the current firefox release (1.07), and the corrected test page,
> it still doesn't work for me. Also doesn't work in mozilla 1.7.11
Dave,
all of these problems and issues (Firefox 1.0.x branch, Mozilla 1.7 branch, alt
text, embedded content) are being dealt with, discussed, are already being
addressed in bug 114641 since Dec. 2001. Just read yourself the comments made
over there. This bug 310126 is definitely a duplicate of bug 114641.
Alt attribute value is currently rendered in Firefox 1.4, will be rendered in
Firefox 1.5 (rv:1.8) and there are chances it will be rendered in Seamonkey
based on rv:1.9 final.
The issue of whether or not embedded content should be rendered too along+with
the alt attribute value has been formally addressed over there too and in
comments #25, #27 and #28 of bug 71473.
Converting <applet> to <object> is one simple and good thing web authors (you?)
can do:
http://ww2.cs.fsu.edu/~steele/XHTML/appletObject.html
<applet> has been formally deprecated in HTML 4.01 in favor of <object>, some 7
years ago. Another thing you can do now is to vote for bug 114641... unless you
can bring up a patch yourself for bug 114641.
Your concern is not being ignored: it has been dealt with in bug 114641 in the
last 3 years and it still is been dealt with as far as I can say.
Thank you for your understanding,
Gérard
You need to log in
before you can comment on or make changes to this bug.
Description
•