Closed
Bug 120955
Opened 24 years ago
Closed 24 years ago
Internet speed test fails to show results
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 118404
People
(Reporter: tajkkj, Assigned: tetsuroy)
References
()
Details
(Keywords: intl)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4)
Gecko/20011128 Netscape6/6.2.1
BuildID: 2002011503
The MSN internet speed test is supposed to time the download of some files and
display your current connection speed. This works OK on Netscape 6.2 and until
recently worked with Mozilla. Now, you get a page which tells you this may take
some time, but once this page displays there is no data transferred, and the
display never changes.
Reproducible: Always
Steps to Reproduce:
1. Load the referrenced URL.
2. Enter your area code.
3. Select your connection type
4. Click "Test It"
Actual Results: Speed results never displayed
Expected Results: Speed results should be displayed
Comment 1•24 years ago
|
||
wfm with win2k build 20020119..
(I used area code "112" and it seems to be valid)
![]() |
||
Comment 2•24 years ago
|
||
worksforme, linux build 2002-01-18-08
Comment 3•24 years ago
|
||
Doesn't work for me on 2002011604 Win98SE.
However, based on previous comments, it looks like this got fixed a couple of
days after my version.
Comment 4•24 years ago
|
||
wfm 2002011803.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 5•24 years ago
|
||
I just tried this with build 2002011908 and it's still not working. I've tried
my area code (520) and the 112 tried by Matthias with no success. Probably
unrelated, but when I first tried it with 2002011908, the "Test It" button
didn't appear either. It only appeared after I tried this with Netscape 6.2.
Reporter | ||
Comment 6•24 years ago
|
||
I just tried this again with the 2002012503 build. Now the "Test It" button
appears, but I still don't get the results rendered after the test is complete.
This is on WinXP home edition. I'm entering 520 as the area code and checking
the DLS/Cable radio button, although it doesn't seem to matter what area code or
connection type I choose.
Comment 7•24 years ago
|
||
Reporter:
This is still worksforme with an 3h old CVS build on win2k.
Can you first try a new profile ?
Run "Mozilla -profilemanager" and cerate a additional test profile.
BTW: Have you installed Mozilla in an empty directory (not over an older build) ?
If you see the same problem with the new profile:
Can you generate a Http log ?
set NSPR_LOG_MODULES=nsHttp:5
set NSPR_LOG_FILE=c:\http.log
and start mozilla, go to that page and select ISDN and aArea code 520.
Attach this http log to this bug... (via "create new attachment")
Reporter | ||
Comment 8•24 years ago
|
||
Well, I found the problem with my profile. I started with a clean one which
didn't have this problem, then replaced it piece by piece with mine until I got
the failure. I then narrowed it down to this line:
user_pref("intl.charset.default", "");
I have no idea where it came from, but when this line is present the problem
exists. Take it out, and the problem goes away.
Comment 9•24 years ago
|
||
Reporter: Do you use an migrated NS4.7x profile ?
Reporter | ||
Comment 10•24 years ago
|
||
Yes, that's where the present Mozilla profile came from, but I could not find
the above line in that profile.
Comment 11•24 years ago
|
||
reopening
Status: RESOLVED → UNCONFIRMED
Component: Browser-General → Internationalization
Resolution: WORKSFORME → ---
Comment 12•24 years ago
|
||
and -> Internationalization
the line : user_pref("intl.charset.default", ""); should not cause this problems !
Assignee: asa → yokoyama
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: doronr → ruixu
![]() |
||
Comment 13•24 years ago
|
||
Duplicate of "External JS files not loading; fixed by making new Profile" (same
exact problems).
*** This bug has been marked as a duplicate of 118404 ***
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•