Last Comment Bug 153600 - ProcessScriptElement should use successvalue as indicator
: ProcessScriptElement should use successvalue as indicator
: regression, testcase
Product: Core
Classification: Components
Component: DOM: Core & HTML (show other bugs)
: Trunk
: All All
: -- normal (vote)
: Future
Assigned To: Jonas Sicking (:sicking)
: 154108 154157 154164 154428 (view as bug list)
Depends on: 26790 214081
  Show dependency treegraph
Reported: 2002-06-22 10:52 PDT by larrybird
Modified: 2011-10-10 02:05 PDT (History)
9 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

NSPR nsHttp logs for builds 20020620 and 20020622 (30.22 KB, text/plain)
2002-06-22 19:27 PDT, Andrew Schultz
no flags Details
testcase (123 bytes, text/html)
2002-06-23 18:02 PDT, Andrew Schultz
no flags Details
patch to fix (1.32 KB, patch)
2002-06-25 16:56 PDT, Jonas Sicking (:sicking)
bzbarsky: review+
jst: superreview+
Details | Diff | Review

Description larrybird 2002-06-22 10:52:17 PDT
This page loads immediately in IE, but hangs indefinitely in mozilla.  I'm 
not adept at HTML so I have no idea why.
Comment 1 Markus Långström 2002-06-22 11:45:40 PDT
WFM, 2002061712 Win 98.
Reporter, please always specify which Build ID you're using when filing a bug.
Comment 2 Matthias Versen [:Matti] 2002-06-22 12:02:13 PDT
wfm with win2k build 20020621..
Comment 3 R.K.Aa. 2002-06-22 14:42:25 PDT
spins forever on a current CVS, linux - nothing loads.
Tried all possible combos of proxies and pipeline settings - no go.
Comment 4 Andrew Schultz 2002-06-22 18:56:39 PDT
confirmed with linux build 2002062204.  works fine with build 2002062021.

marking NEW
==> Http
Comment 5 Andrew Schultz 2002-06-22 19:27:03 PDT
Created attachment 88826 [details]
NSPR nsHttp logs for builds 20020620 and 20020622

produced with diff --side-by-side (trivial differences manually ignored)
Comment 6 Jeremy M. Dolan 2002-06-22 19:36:00 PDT
Finishes displaying in 2002062004 linux, but status bar still says "Transfering
data from ...". I get that on quite a few sites... especially.
Comment 7 Andrew Schultz 2002-06-22 19:44:13 PDT
Jeremy: regression occurred after your build...

marking NEW for real.
sniffit showed the document fully transferred and view->source displayed it just
fine...  ???
Comment 8 Andrew Schultz 2002-06-23 05:53:32 PDT
this seems to be working with build 20020622 now.  A new http log shows only
minor differences with build 20020620.

if someone can't just look at the logs I attached and know what's going on, this
is worksforme.
Comment 9 Cees T. 2002-06-23 08:11:07 PDT
Still occurs with trunk 2002062304 on Windows ME.
View Source does show the code..
Comment 10 Andrew Schultz 2002-06-23 18:02:23 PDT
Created attachment 88891 [details]

this has nothing to do with networking...
Comment 11 Andrew Schultz 2002-06-23 18:05:21 PDT
regression from bug 26790
Comment 12 Henrik Gemal 2002-06-24 02:52:20 PDT
this is a blocker, since people are unable to load pages with mozilla...

it seems like:
<script language="javascript" type="text/javascript">printHeader();</script>
will also prevent a page from loading.

at least that's what I'm seeing on:
which refuses to render...
Comment 13 Jeremy M. Dolan 2002-06-24 11:38:39 PDT
I've had issues loading BBC News lately too. In their source:

<script src="/nol/shared/js/nol.js" language="JavaScript"></script>
<SCRIPT LANGUAGE="JavaScript" src="/javascript/avmega.js"></SCRIPT>

But there were occasionally problems even before this more consistent one.
There's another bug I filed before on it only being loadable once per browser run.
Comment 14 Boris Zbarsky [:bz] 2002-06-25 04:04:06 PDT
*** Bug 154108 has been marked as a duplicate of this bug. ***
Comment 15 Jonas Sicking (:sicking) 2002-06-25 14:32:05 PDT
got a patch to fix this, will attach asap
Comment 16 Jonas Sicking (:sicking) 2002-06-25 16:56:09 PDT
Created attachment 89164 [details] [diff] [review]
patch to fix

this fixes the problem but it's not as beautiful as it should be. What we might
end up doing is call ScriptAvailable/ScriptEvaluated more then once if you
first insert an empty <script> and then set the src-attribute or give it

This can never happen during parsing since we always add all
attributes/children to a <script> before adding it to the document tree.
However it can happen during DOM manipulation. We'll still never evaluate a
script more then once though.
Comment 17 Jonas Sicking (:sicking) 2002-06-25 16:57:08 PDT
bz, got time to review this?
Comment 18 Boris Zbarsky [:bz] 2002-06-25 18:04:51 PDT
*** Bug 154157 has been marked as a duplicate of this bug. ***
Comment 19 Boris Zbarsky [:bz] 2002-06-25 20:28:13 PDT
Comment on attachment 89164 [details] [diff] [review]
patch to fix

r=bzbarsky, but it'd be nice to make the return value from
ProcessScriptElement() be a success value that says "script evaluated" or a
success value that says "nothing to evaluate".

Then we could just check that return value and set mIsEvaluated accordingly....
Comment 20 Johnny Stenback (:jst, 2002-06-26 00:17:20 PDT
Comment on attachment 89164 [details] [diff] [review]
patch to fix

sr=jst, lets get this in and leave the bug open if we want to tweak things more
Comment 21 John Unruh 2002-06-26 08:49:12 PDT
*** Bug 154164 has been marked as a duplicate of this bug. ***
Comment 22 Bernard Alleysson 2002-06-26 16:46:59 PDT
*** Bug 154428 has been marked as a duplicate of this bug. ***
Comment 23 Jonas Sicking (:sicking) 2002-06-26 17:12:43 PDT
Comment on attachment 89164 [details] [diff] [review]
patch to fix

this one has landed so all problems should be fixed. However i'm keeping this
bug open to fix the suggestion from Boris
Comment 24 Christopher Aillon (sabbatical, not receiving bugmail) 2002-06-26 17:14:02 PDT
Jonas, I'd suggest filing that as a separate bug.
Comment 25 Jonas Sicking (:sicking) 2002-10-01 14:53:38 PDT
changing this bug to reflect the remaining work needed
Comment 26 larrybird 2003-06-25 05:16:06 PDT

I'm the original submitter. I'm not certain, but I think you believe this bug
is resolved, but its not as you can see at:,1589,12+410+415+9,00.html

which still displays incorrectly.  
Comment 27 Andrew Schultz 2003-06-25 05:56:36 PDT
this bug (originally) concerned Mozilla hanging when trying to load a page with
a particular <sciprt> syntax.  A display problem (which I do see) on a different
page is a different bug.
Comment 28 :Ms2ger 2011-10-09 08:46:51 PDT
Jonas, are you still planning to do anything in this bug?
Comment 29 Jonas Sicking (:sicking) 2011-10-10 02:05:40 PDT
No, it appears that we've cleaned things up enough that there's nothing left here to do.

Note You need to log in before you can comment on or make changes to this bug.