273708 - Index entries fail when offline

Status: RESOLVED INVALID

(Core Graveyard :: History: Global, defect)

Description

[Rod Whiteley]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Some index entries fail intermittently when Firefox is offline.

Reproducible: Always
Steps to Reproduce:
1. Disconnect fromn the Internet 
2. Start Firefox
3. Open the Help
4. Go to the index
5. Expand A and click on Accessibility

Actual Results:  
Help displays the correct chapter (Mozilla Firefox Options), but goes to the
bottom of the chapter.

Expected Results:  
Help should display the Accessibility section.

Online, the index works OK.

Even offline, some index entries always seem to work.  Others, like
Accessibility, sometimes work and sometimes fail.  Accessibility always fails if
it is the first entry I click after opening Help.

Comment 1

[Nickolay_Ponomarev]

WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0

may be a win98-only problem

Comment 2

[Rod Whiteley]

I tried it on Linux, and I see the same problem.

Comment 3

[Jeff Walden (gone starting June 8)]

I can't reproduce this either.  Are you still seeing this using the latest trunk
builds?

Comment 4

[Rod Whiteley]

(In reply to comment #3)
It still happens today using Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.7)
Gecko/20050414 Firefox/1.0.3.

I should have included a step 2b: Clear the cache.  (I forgot that my cache is
turned off.)  Help's images seem to be online.  An index entry initially goes to
the correct heading.  Then it tries to connect to load the images for the page,
if they are not cached.  After it fails to connect, it displays a different
place in the page.

Comment 5

[Mike Connor [:mconnor]]

there's a bug with named anchors and slow images, which isn't specific to Help
(the GNOME HIG 2.0 has a lot of the same issues for me).

Most likely a dupe, or at the least in the wrong component.

Comment 6

[Jeff Walden [:Waldo]]

Moving to a more likely component to get this off radar...

It might also be worth checking if fastback (bug 274784) fixed this, although
it's not clear yet whether fastback will work well enough to be enabled for
Firefox 1.1 or the xulrunner preview.

Comment 7

[Wayne Mery (:wsmwk)]

this form of offline help is no longer available