Closed Bug 44114 Opened 24 years ago Closed 24 years ago

Unable to Reload after linking to anchor in different document

Categories

(Core :: DOM: Navigation, defect, P3)

Product:
Core
Component:
DOM: Navigation
Platform:
x86
Windows 98
Type:
defect

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: val, Assigned: alecf)

References

Details

(Keywords: testcase, Whiteboard: [nsbeta3-])

Attachments

(1 file)

anchor/reload testcase
602 bytes, text/html
Details 
From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en-gb]C-CCK-MCD NetscapeOnline.co.uk  (Win98; I)
BuildID:    2000061311

Linking to an anchor in a different document:
#anchor-name added to URL in address bar OK, and 'Back' button becomes available 
OK.
However, current page will not reload (though reload button is available).

Linking to an anchor in the same document:
In addition, the name of current page is blank in 'Go' menu. 
(And if one goes 'Back', it's also blank in drop-down list for 'Forward' 
button.)



Reproducible: Always
Steps to Reproduce:
Create a simple HTML file to test linking to anchor in same document:

<head>
<title>Test</title>
</head>
<body>
<a name="fred" href="#fred">text</a>
</body>


Actual Results:  Clicking link produces the effects described above.

Expected Results:  After clicking on link to anchor:
Page should be reloadable (from anchor position onwards?).
Title should appear in 'Go' menu, and 'Forward' and/or 'Back' button drop-down 
lists where appropriate.
I sort of see this in 2000062708, when you click the #link in the same page it
shows fine in the back and go, but the #link one shows wrong in foward and go.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Target Milestone: --- → M22
Possibly dupe of one of my nsbeta3+ bugs
Keywords: nsbeta3
Target Milestone: M22 → M18
nav triage team:
This is actually 2 bugs:
1) page title does not appear in go menu
2) can't reload in this scenario.

Part 1 about the page title is just like a bug that Bill Law has, bug 22174.

Changing the summary of this but to talk *only* about the reload problem.  We
could live with this remaining problem (unhappily), so marking nsbeta3-
Summary: Unable to Reload after linking to anchor in different document, and also absent Page Title after linking to anchor in same document. → Unable to Reload after linking to anchor in different document
Whiteboard: [nsbeta3-]
marking dependency on 22174 (which deals with the page title in the go menu piece)
Depends on: 22174
I notice that most of the bug in its original form (reported in M16) seems to 
have vanished - i.e. in M17, a single link to anchor (in same or different 
document) with reload now seems to work.

But there's still a problem with anchors and Reload:

The attachment is simply a series of links to anchors (tho' Anchor 3 doesn't 
actually exist).
When first loaded the page title is in the Go menu.

Click link to Anchor 1.
Notice blank entry added to Go menu.

Click link to Anchor 2.
Notice still only the one blank entry in Go menu, which seems to belong to 
Anchor 1, because...
Click Reload, and now we're back to Anchor 1.
(Notice that Reload has now substituted page title for blank entry.)

Click link to Anchor 2 again.
Now new blank entry is added to Go menu, and Reload now works for this anchor.

Go 'Back', to Anchor 1.
Reload now will wrongly reload Anchor 2.
But some indicators seem to say we're still at Anchor 1 - ie 'Back' takes us to 
Top of page (where a Reload loads Anchor 2), whereas 'Forward' leaves us at 
Anchor 2 (where a Reload now reloads Anchor 1) ... 

Hope this is of some use.
Attached file anchor/reload testcase — 

    
  
Keywords: testcase

    
    

    
  
nav triage team: looked at this bug, it is not a beta stopper. bulk update of 
several such bugs. 
Keywords: nsbeta1-

    
    

    
  
Mass moving all Navigator bugs to the Nav team. 
Assignee: radha → vishy
Status: ASSIGNED → NEW

    
    

    
  
over to alecf

Assignee: vishy → alecf

    
    

    
  
this is a session history bug if it even still exists. I can't figure out what
this bug actually is at this point, so I'm suggesting we just mark it WORKSFORME
and open a new bug for the problem described at the end.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME

    
    

    
  
mass-verifying WorksForMe bugs which haven't changed since 2001.12.31.

set your search string in mail to "EmperorLondoMollari" to filter out these
messages.
Status: RESOLVED → VERIFIED

    
  
Component: History: Session → Document Navigation
QA Contact: claudius → docshell

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: