Closed
Bug 197623
Opened 22 years ago
Closed 22 years ago
prefetch links should not be shown in Site Navigation Bar
Categories
(SeaMonkey :: UI Design, defect)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: brant, Assigned: bugzilla)
Details
(Keywords: testcase)
Attachments
(3 files)
|
413 bytes,
text/html
|
Details | |
|
497 bytes,
text/html
|
Details | |
|
951 bytes,
patch
|
jst
:
review+
deanis74
:
superreview+
asa
:
approval1.4+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030307
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030307
If a Webmaster believes certain links will be followed in a Web page, he or she
may add link elements with prefetch relations. This, a decidedly internal
mechanism from the consensus of bug 193563, should not appear in the Site
Navigation Bar.
For details of the previous discussion of prefetch links in the toolbar, see bug
193563.
For details on prefetching itself, see
<http://www.mozilla.org/projects/netlib/Link_Prefetching_FAQ.html>.
Reproducible: Always
Steps to Reproduce:
1. Create a page with the following code in either HTML or XML syntax:
<link rel="prefetch" href="page2.html" title="Prefetched Content">
2. Open the page in Mozilla Navigator.
3. Make sure the Site Navigation Bar is visible by clicking Show/Hide > Site
Navigation Bar > Show Always in the View menu.
4. If the toolbar is not visisble, expand any unexpanded grippies until you find it.
5. Click the More button in the Site Navigation Bar.
Actual Results:
In the menu expanded by the More button, there is a prefetch folder listing
"Prefetch Content."
Expected Results:
There should not be a prefetch folder.
| Reporter | ||
Comment 1•22 years ago
|
||
I am adding active CCs from other bug.
OS: Windows XP → All
Hardware: PC → All
| Reporter | ||
Comment 2•22 years ago
|
||
I haven't been able to modify my patch from the original bug so that <link
rel="prefetch next"> appears as Next, but not as prefetch. Does anybody have
any ideas on how this could be done.
| Reporter | ||
Comment 3•22 years ago
|
||
cc'ing some others from bug 173674 to see if they can help on this one
Comment 4•22 years ago
|
||
Comment 5•22 years ago
|
||
This is the problematic case with the original patch -- if rel="next prefetch"
is specified, the Next button should be enabled but there should not be a More
> prefetch menu.
Comment 6•22 years ago
|
||
Updated•22 years ago
|
Attachment #119815 -
Flags: review?(choess)
Updated•22 years ago
|
Attachment #119815 -
Flags: review?(choess) → review?(jst)
Comment 7•22 years ago
|
||
Comment on attachment 119815 [details] [diff] [review]
fix
r/sr=jst
Attachment #119815 -
Flags: review?(jst) → review+
Updated•22 years ago
|
Attachment #119815 -
Flags: approval1.4?
Comment 8•22 years ago
|
||
Comment on attachment 119815 [details] [diff] [review]
fix
a=asa (on behalf of drivers) for checkin to 1.4
Attachment #119815 -
Flags: approval1.4? → approval1.4+
Comment on attachment 119815 [details] [diff] [review]
fix
r=me; jst's r= now becomes sr=.
Attachment #119815 -
Flags: superreview+
Updated•22 years ago
|
Attachment #119815 -
Flags: superreview?(dean_tessman)
Attachment #119815 -
Flags: superreview?(dean_tessman)
Comment 10•22 years ago
|
||
timeless just checked this in
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•