Closed
Bug 102906
Opened 23 years ago
Closed 14 years ago
Link toolbar doesn't support <meta> links
Categories
(SeaMonkey :: UI Design, enhancement)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ian, Unassigned)
References
()
Details
(Keywords: testcase, Whiteboard: [Hixie-P4])
STEPS TO REPRODUCE Go to a web page with links in <meta> tags, e.g.: http://www.bath.ac.uk/~py8ieh/internet/eviltests/link4.html ACTUAL RESULTS The link toolbar has no links. EXPECTED RESULTS Identical to http://www.bath.ac.uk/~py8ieh/internet/eviltests/link2.html cc'ing usual suspects as per bug 102832.
Reporter | ||
Updated•23 years ago
|
Reporter | ||
Updated•23 years ago
|
Whiteboard: [Hixie-P4]
Comment 1•23 years ago
|
||
This is definitely an RFE, together with supporting Link: headers that the webserver sends. We took it out of the initial implementation because it wasn't working. Also, I seem to remember noticing last night that HTTP 1.1 deprecates Link: headers. See the end of section 19.6.3 of RFC 2616. Do we really need to support them at all? Gerv
Comment 2•23 years ago
|
||
cool new feature! ->claudius, since he tests toolbars.
QA Contact: sairuh → claudius
Reporter | ||
Comment 3•23 years ago
|
||
Gerv: Yes, we do. It was only taken out of the spec because there were no implementations. If implementations spring up, it will be added back in. HTTP Link headers are an amazingly powerful feature. We support them for stylesheets, making it possible to style an entire website without touching a single file outside the server configuration. Similarly, supporting Link for the link toolbar would give the same power for linking. If we support real headers (bug 102907) then we should definitely support <meta> headers, since they should always be treated identically. (In fact, we should not have to do any extra work to do this -- if one works, the other should automatically work if we have a well designed architecture. Please bare this in mind when fixing this bug.)
Comment 4•23 years ago
|
||
Supporting <media> would be no more difficult than supporting the HTTP Link:, as the parsing code would be identical. The only difference would be the few extra lines to grab all the <media> elements from the document to pull out the Link: headers.
Reporter | ||
Comment 5•23 years ago
|
||
s/<media>/<meta>/
Reporter | ||
Updated•23 years ago
|
Severity: normal → enhancement
Comment 6•22 years ago
|
||
Is this related: http://www.richinstyle.com/test/attachment/http.php?
Updated•21 years ago
|
Assignee: drbrain-bugzilla → guifeatures
OS: Windows 2000 → All
Hardware: PC → All
Updated•20 years ago
|
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
Comment 7•16 years ago
|
||
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: claudius → guifeatures
Comment 8•14 years ago
|
||
Shouldn't this be WONTFIXed now that HTML5 obsoletes http-equiv="Link"?
Comment 9•14 years ago
|
||
WONTFIX based on Comment 8
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•