Closed
Bug 3658
(frame-longdesc)
Opened 26 years ago
Closed 2 years ago
UAAG: frame/iframe longdesc attribute not used [frame]
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: glynn, Unassigned)
References
()
Details
(Keywords: access, html4, testcase, Whiteboard: [HTML4-16.2.2][HTML4-16.5])
Attachments
(3 files)
March 11 Seamonkey builds, Mac 8.5/G3, Linux 5.2, optimized, viewer
March 10 win98 optimized, viewer
1. Launch Seamonkey and load test case page:
slip/projects/marvin/html/frameset_longdesc.html
2. These frames include longdesc attributes; it is unclear even per HTML 4.0
spec what the user should see when this attribute is used.
• What should the user experience here when the longdesc attribute is used?
Need clarification on this from engineering to determine A) if this is indeed a
functional failure B) to refine test case.
Beth -- HOW we handle attributes is not a parser problem. It's core layout.
Passing these on to Kipp.
I filed these all in one lump..hence why all were marked parser..will mark layout
for this variety in future.
Updated•26 years ago
|
Assignee: karnaze → pollmann
Comment 4•26 years ago
|
||
Eric is working on frameset related DOM changes which will include longdesc, so
I'm reassigning this to him to make sure that getting and setting this attribute
works.
However, what the viewport display does with this is not clear to me and maybe
Troy has some insight, since it is related to what the viewport will need to do
with the title attribute.
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 5•26 years ago
|
||
This is treated as the longdesc attribute on an img tag, which is to say it
isn't yet.
The attribute is stored in the content model correctly (as can be seen by
dumping the content model. However, when the DOM methods are used to access it,
an empty string is returned.
After the document is loaded, the longdesc attribute can be set and retrieved
through the DOM, but has no effect on either the content model or the display of
the document.
(This behaviour was observed at http://blueviper/frames/test.html)
Updated•26 years ago
|
Target Milestone: M6
Comment 6•25 years ago
|
||
Redistributing to M8...
Comment 7•25 years ago
|
||
Didn't make M8
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → REMIND
Summary: frame/iframe longdesc attribute implementation unclear → frame/iframe longdesc attribute not used
Comment 8•25 years ago
|
||
This doesn't seem like a dogfood, beta, or final ship requirement to me, but
more like an accessability enhancement. We are already storing the attribute in
the content model, I think that should be enough for a while.
Perhaps we should leave this up to the creator of an enhanced browser that
embeds gecko to get then use the longdesc file as needed. Closing the bug open
as remind.
If anyone things this should be addressed now or before ship, please reopen and
suggest how we should handle the longdesc attribute.
Comment 9•24 years ago
|
||
Reopening and moving to Future...
Severity: major → normal
Status: RESOLVED → REOPENED
OS: Windows 98 → All
Resolution: REMIND → ---
Target Milestone: M11 → Future
Updated•24 years ago
|
Keywords: mozilla1.1
Comment 11•23 years ago
|
||
Bulk reassigning form bugs to Alex
Assignee: pollmann → alexsavulov
Status: REOPENED → NEW
Updated•23 years ago
|
Summary: frame/iframe longdesc attribute not used → frame/iframe longdesc attribute not used [frame]
Comment 12•23 years ago
|
||
The longdesc attribute is now supported with a img element. That procedure
should similarly work with iframe/frame elements. Right clicking on a iframe or
frame should display a popup menu that includes a View Frame info item.
Selecting this menu item should open a dialog that includes the specified
longdesc uri.
Comment 13•23 years ago
|
||
Comment 14•23 years ago
|
||
removing myself from the cc list
Updated•23 years ago
|
Whiteboard: [HTML4-16.2.2][HTML4-16.5]
Comment 17•22 years ago
|
||
Comment 18•22 years ago
|
||
Comment 19•22 years ago
|
||
Comment 20•20 years ago
|
||
Reporter, please try a newer build. This bug is getting quite old and will be
marked invalid if some action does not occur shortly.
-R
Updated•20 years ago
|
Alias: frame-longdesc
Comment 21•19 years ago
|
||
*** Bug 321623 has been marked as a duplicate of this bug. ***
Updated•19 years ago
|
Summary: frame/iframe longdesc attribute not used [frame] → UAAG: frame/iframe longdesc attribute not used [frame]
Comment 22•17 years ago
|
||
The previous URL
http://slip/projects/marvin/html/frameset_longdesc.html
is now "Not Found 404"
Replacing with
http://www.w3.org/WAI/UA/TS/html401/cp0203/0203-FRAME-LONGDESC-TEST.html
Updated•15 years ago
|
QA Contact: amar → layout.html-frames
Shouldn't this be WONTFIX now that HTML5 obsoletes longdesc?
Comment 24•14 years ago
|
||
Since this is a 4 digit bug, I don't know that it matters whether HTML5 obsoletes longdesc here. But, note that for iframe HTML5 also obsoletes: frameborder, marginheight, marginwidth, and scrolling. I think if we don't have, or remove processing for those, then we should close this bug.
Comment 25•14 years ago
|
||
That's not quite right; it still requires that they be implemented by browsers (with the exception of "scrolling", no idea what that needs to do).
Comment 26•11 years ago
|
||
Removing QAwanted from this bug since it didn't come with any specific request and it was added 11 years ago. Please re-add if you need anything specific from QA.
Keywords: qawanted
Updated•6 years ago
|
Product: Core → Core Graveyard
Assignee | ||
Updated•6 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
Comment 27•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: db48x → nobody
Updated•2 years ago
|
Severity: normal → S3
Comment 28•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 10 votes.
:emilio, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(emilio)
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago → 2 years ago
Flags: needinfo?(emilio)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•