Closed Bug 98687 Opened 23 years ago Closed 22 years ago

storagereview.com - page won't load if not following link

Categories

(Core :: Networking: HTTP, defect, P3)

x86
All
defect

Tracking

()

VERIFIED WORKSFORME
mozilla1.0

People

(Reporter: lorenzo, Assigned: harishd)

References

()

Details

(Keywords: testcase)

Attachments

(4 files)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801
BuildID:    2001080104 (Mozilla 0.9.3 Linux)

Mozilla will only load HTML pages from www.storagereview.com if following links
from the site itself. If you try to load pages by typing the URL in the URL bar
or by clicking on "Open Link in New Window", the pages will not load..

Reproducible: Always
Steps to Reproduce:
1.Open the example URL in a new window
2.Wait forever. :-)
3.

Actual Results:  The page never loads. The throbber keeps going and the status
line says "Document: done"

Expected Results:  Mozilla should be able to load the page in a new window.

The problem does not appear if JavaScript is disabled or if the SCRIPT tag that
loads load_css.js is removed.
confirming with win2k build 20010907..
Status: UNCONFIRMED → NEW
Ever confirmed: true
Can not confirm in win me 2001090703.

Page loads correctly.
Still seeing this in 2001091303 under WinME.
right click page source comes up before page does, which takes forever and is
not loading. 2001092908 w2k. clicking on link from front page header will load
the page. even though they are exactly the same.
appears to be an iframes type of site.. see attachment.
this problem also occurs while trying to load the body part of frames under both
right-click options: open frame in new window and show only this frame.

the previous doesn't always happen its random.. maybe something of a random side
effect here of bad code when mozilla fails to continue loading page after it
connects. hmm.
ahh, found it.. right-clicking those two items the page loads from the
discussion page.  But it doesn't finish loading from the main page from within
the same frame.
I see the difference, CSS is hard-coded into the page that works, not an
external file like the first page.
page that works has the following dir, and hard-coded css:

<script language="JavaScript1.2" type="text/javascript"
src="style/load_defaults.js"></script>

pages that do not work:

<script LANGUAGE="JavaScript1.2" TYPE="text/javascript"
SRC="/styles/load_css.js"></SCRIPT>

notice the differences.
emailed webmaster at site.
From a quick look it seems like the HTML parser doesn't properly continue
parsing once the external css file is loaded, we do tell the parser to continue,
but something goes wrong.
Assignee: jst → harishd
Component: DOM Level 0 → Parser
QA Contact: desale → moied
interestingly I don't get an OnStopRequest. However, I do get a Terminate()!

CNavDTD::DidBuildModel(CNavDTD * const 0x02dd2b40, unsigned int 2152596471, int
1, nsIParser * 0x02d99880, nsIContentSink * 0x02dc3430) line 572
nsParser::DidBuildModel(unsigned int 2152596471) line 1385 + 55 bytes
nsParser::Terminate() line 1470
nsHTMLDocument::StopDocumentLoad(nsHTMLDocument * const 0x02d8a1b0) line 877
DocumentViewerImpl::Stop(DocumentViewerImpl * const 0x02d91f30) line 1349
nsDocShell::Stop(nsDocShell * const 0x00b53d40, unsigned int 2) line 2301
LocationImpl::SetHrefWithBase(const nsAString & {...}, nsIURI * 0x02dbb750, int
0) line 566
LocationImpl::SetHrefWithContext(JSContext * 0x00b9cb40, const nsAString &
{...}, int 0) line 501 + 25 bytes
LocationImpl::SetHref(LocationImpl * const 0x02ddaf50, const nsAString & {...})
line 470 + 18 bytes
nsWindowSH::SetProperty(nsWindowSH * const 0x0276ecf0, nsIXPConnectWrappedNative
* 0x02771460, JSContext * 0x00b9cb40, JSObject * 0x01650128, long 23395740, long
* 0x0012f600, int * 0x0012e8b8) line 2482 + 27 bytes
XPC_WN_Helper_SetProperty(JSContext * 0x00b9cb40, JSObject * 0x01650128, long
23395740, long * 0x0012f600) line 792 + 47 bytes
js_SetProperty(JSContext * 0x00b9cb40, JSObject * 0x01650128, long 41305840,
long * 0x0012f600) line 2689 + 207 bytes
js_Interpret(JSContext * 0x00b9cb40, long * 0x0012f820) line 2634 + 1939 bytes
js_Execute(JSContext * 0x00b9cb40, JSObject * 0x01650128, JSScript * 0x0282b9c0,
JSStackFrame * 0x00000000, unsigned int 0, long * 0x0012f820) line 1012 + 13 bytes
JS_EvaluateUCScriptForPrincipals(JSContext * 0x00b9cb40, JSObject * 0x01650128,
JSPrincipals * 0x02dc2e00, const unsigned short * 0x016e37a8, unsigned int 937,
const char * 0x02828fc0, unsigned int 1, long * 0x0012f820) line 3356 + 25 bytes
nsJSContext::EvaluateString(nsJSContext * const 0x00b9da80, const nsAString &
{...}, void * 0x01650128, nsIPrincipal * 0x02dc2dfc, const char * 0x02828fc0,
unsigned int 1, const char * 0x0099368c, nsAString & {...}, int * 0x0012f88c)
line 674 + 85 bytes
nsScriptLoader::EvaluateScript(nsScriptLoadRequest * 0x02d82190, const
nsAFlatString & {...}) line 576
nsScriptLoader::ProcessRequest(nsScriptLoadRequest * 0x02d82190) line 483 + 22 bytes
nsScriptLoader::OnStreamComplete(nsScriptLoader * const 0x02dc49f4,
nsIStreamLoader * 0x02db9f60, nsISupports * 0x02d82190, unsigned int 0, unsigned
int 4294967295, const char * 0x0282ef3a) line 771
nsStreamLoader::OnStopRequest(nsStreamLoader * const 0x02db9f64, nsIRequest *
0x02df8b50, nsISupports * 0x00000000, unsigned int 0) line 137
nsHttpChannel::OnStopRequest(nsHttpChannel * const 0x02df8b54, nsIRequest *
0x02803994, nsISupports * 0x00000000, unsigned int 0) line 2386
nsOnStopRequestEvent::HandleEvent() line 213
nsARequestObserverEvent::HandlePLEvent(PLEvent * 0x0282f4b4) line 116
PL_HandleEvent(PLEvent * 0x0282f4b4) line 590 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x00ba7aa0) line 520 + 9 bytes
_md_EventReceiverProc(HWND__ * 0x002c0630, unsigned int 49495, unsigned int 0,
long 12221088) line 1071 + 9 bytes
USER32! 77e13eb0()
USER32! 77e1401a()


I doubt this a parser problem. 
Attached file Testcase
Keywords: testcase
Priority: -- → P3
Target Milestone: --- → mozilla0.9.8
Giving bug to netlib folks for scrutiny.
Component: Parser → Networking: HTTP
--> netlib
Assignee: harishd → darin
QA Contact: moied → tever
harishd: you don't see the OnStopRequest, because this JS script is being loaded
using a nsStreamLoader object.  all you get therefore is a OnStreamComplete
notification, which corresponds to an OnStopRequest.

-> back to harish :-)
Assignee: darin → harishd
Out of time. Mass move to 0.9.9
Target Milestone: mozilla0.9.8 → mozilla0.9.9
jst: This is probably a bug in the script loader. After the script is evaluated
the parser should get a ContinueParsing call. But since the script is loading a
new location it tries to stop the old document and hence terminates the parser
without resuming it.  
Keywords: nsbeta1
Target Milestone: mozilla0.9.9 → mozilla1.0
nsbeta1- per ADT triage.
Keywords: nsbeta1+nsbeta1-
This looks like it's fixed. WFM with 2002050506 (branch) WinME. The testcase
works fine too.

Can someone confirm so we can resolve this as fixed or worksforme?
Worksforme too.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
verified - wfm too - 06/18/02 builds
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: