Closed Bug 299190 Opened 20 years ago Closed 18 years ago

Updated index page loads blank; status bar reads done

Categories

(Firefox :: General, defect)

x86
Windows NT
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mambolian, Unassigned)

References

()

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; (R1 1.5); .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 This new index page is very simple and WC3 compliant. No scripts, frames or layers. Have received complaints it is loading blank and status bar reads "done". I cannot duplicate, shows up fine in my earlier version of Firefox as well as IE. Hosting service also could not duplicate. Have asked complainers to clear cache and reload but this did not work. Reproducible: Couldn't Reproduce Steps to Reproduce: 1.Complainers report simply opening this web page. 2. 3. Actual Results: They only see a blank page with status bar reading done. Expected Results: Full page should display. Is it a cache conflict with Windows NT, or something related to Bookmarking? Is it related to networking restrictions?
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050628 Firefox/1.0+ ID:2005062811
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050629 Firefox/1.0+ ID:2005062910 WFM The Gif(s) display fine. You need to provide more information about the clients that are having a problem showing the page. FF version/OS etc... Are you reporting a bug in firefox or asking for help making your site work, as bugzilla is for reporting firefox bugs not web development assistance.
WFM - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050629 Firefox/1.0+
Closing as WORKSFORME per comments 1 through 3. Becky, if you can still reproduce this using Firefox 2.0.0.3 with a clean profile, please file a new bug with details.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.