Closed Bug 10522 Opened 21 years ago Closed 21 years ago

no "back" functionality with XML pages

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: chris, Assigned: nisheeth_mozilla)

References

()

Details

Following a link from an HTML page to an XML page, the XML was displayed OK but the back button then stopped working. FDor an example, go to www.w3.org/TR/SVG, go to a chapter with examples (there are lots) and follow the link from an example to its xml source.

These xml files have no stylesheets; I don't know if that makes a difference or not. I was using M8 under NT4/sp3
Assignee: shuang → hyatt
hyatt, can you have this bug or should I give to someone else?
Assignee: hyatt → nisheeth
Giving to Nisheeth.
Status: NEW → ASSIGNED
I went to http://www.w3.org/TR/SVG/struct.html and clicked on the first example.
I then clicked the back button and I went back fine.

I am using today's NT debug build.  Chris, which build are you using?  Thanks.
I was using the M8 build ID 1999071417 under Windows NT 4.0 (x86) SP3
This might be a networking problem or cacheing problem rather than UI. I tried
it again and it did, after 15 seconds, go back. But when I went forwards again,
it just sat there for ever.

Netscape Navigator 4.6 on the same machine over the same dialup connection (ISDN
modem) retrieved the struct.html page in about 2 seconds wheras Mozilla M8 seems
to take a lot longer (variable though, sometimes its fast). Does Mozilla fetcha
new copy from the network when you use the back button, or does it (surely) use
a cached copy?
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Yes, the cache is not kicking in when it should.  Once Necko lands, we are going
to try to enable the cache before M9 is released.  That work should, hopefully,
fix the cache-related bugs that you are seeing.

I'm marking this bug worksforme because today's builds are going back/forward
reasonably fast.
Status: RESOLVED → VERIFIED
I'll verify this as WFM but the reporter should keep an eye out for a behavioral

change whenever the new cache lands.
Moving all UE/UI bugs to new component: User Interface: Design Feedback
UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.