Closed Bug 20388 Opened 25 years ago Closed 25 years ago

w3 reloads forever

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

VERIFIED INVALID

People

(Reporter: mikepinkerton, Assigned: vidur)

References

()

Details

(Whiteboard: [PDT-])

Go to our internal w3 page....watch it never stop reloading.
Severity: normal → critical
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Summary: w3 reloads forever → [dogfood] w3 reloads forever
adding [dogfood] to the summary, this is a pretty darn important page for internal netscape. happens on windows as well with debug build from 12/9/99
Whiteboard: [PDT-]
W3 user layers, so it's not dogfood.
Reassigning all of leger's unscreened Browser-General bugs to nobody@mozilla.org for pre-screening and triage.
For everybody outside Netscape, could you guys please be a bit more specific? Is http://w3 a mirror of http://www.w3.org? Probably not, as the w3c wouldn't use layers, but is this site somewhere accessible through the internet so I can make a testcase or something?
Component: Browser-General → Networking
QA Contact: nobody → tever
Assignee: nobody → gagan
Changing to Networking component, and reassigning and updating QA Contact.
Target Milestone: M14
Whiteboard: [PDT-]
No. They're talking about our internal Netscape site which provides employees with company/HR etc data. This was still happening with Jan 05 builds. I am removing PDT-, for consideration for PDT+ if it is not fixed with today's build. tever, let us know please.
FYI: I saw a similar problem in the past on an earlier version of http://w3/ with an earlier version of Nav4.0x or 4.x (not sure which). The problem then was that I was running Nav 4.0x with the cache turned off, and somehow the page's code was causing Nav4 to load and reload and reload the page forever. Not sure if that was related to w3's use of the LAYER tag at that time. This problem may or may not be related.
Whiteboard: [PDT-]
Putting on PDT- radar.
Keywords: beta1
this has nothing to do with networking. the script on that page requests (and repeats) for a document. as per rickg there are no layers tag for dogfood...
Assignee: gagan → leger
but it would be good to have a way for the browser to recognize that it is doing this and either stop it, or pop up a dialog asking if they want to stop it with a link to some doc explaining the problem. Otherwise, whenever anyone runs into this they're not going to understand what the problem is, and they will assume it's a problem with the browser, not the web page. At the very least we should put a warning somewhere stating that this page is using non-standard HTML (LAYERS tag) to give people a little clue.
the looping behavior is pretty confusing. is there anyway to get rid of that for beta1? who should own this bug? removing pdt- for dogfood
Assignee: leger → rickg
Whiteboard: [PDT-]
Layers. PDT-
Whiteboard: [PDT-]
Putting dogfood in the keyword field.
Keywords: dogfood
Moving out.
Target Milestone: M14 → M15
Summary: [dogfood] w3 reloads forever → w3 reloads forever
Ok -- so the new issue isn't layers, it's that the page loads, and reloads forever. It would be really nice to find a way to disable this. I'm out of the office for a few days, so I'll ask vidur to take a look. If it's not fixed when I get back, I'll take another look. V?
Assignee: rickg → vidur
Note that IE does the same. The problem is the malformed <META HTTP-EQUIV="Refresh"...> in the <NOLAYERS> section of the document. The CONTENT attribute should have a delay in milliseconds (which it does) as well as a "URL=" before the URL to refresh to (which it doesn't). The reloading is a result of the malformed CONTENT string (we use the page's URL as the base for the reload, and resolve a relative URL of "" off that because of the malformed string). The owners of page should really fix this. I'm checking to see what Navigator does for malformed CONTENT attributes. If it does the same, I'm inclined to mark this INVALID or WONTFIX.
Nav 4.x does the same. Marking this INVALID. Again, someone should tell the owners of the page to fix their content.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
verifying invalid
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.