Closed
Bug 45929
Opened 25 years ago
Closed 19 years ago
outupt warning if unicode converter hit conversion error.
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: teruko, Assigned: smontagu)
References
()
Details
(Keywords: intl)
Attachments
(2 files)
This page is the home page of Japanese Horoscope in Japanese sidebar.
This page is not loaded correctly.
Steps of reproduce
1. go to above URL
Title is displayed in the page. Title should not be displayed in the page.
Also, nothing else is displayed.
I looked at the source. This page is used CSS and Javascript.
Tested 2000-07-19-10 Win32 and Linux build.
Comment 1•25 years ago
|
||
Reassign to rogerl@netscape.com, not sure if this is a problem of Javascript
Engine. The anmation by JS is not showing at all.
Assignee: nhotta → rogerl
Comment 2•25 years ago
|
||
Adding Rosilene Martins, who is the program manager for this tab.
Teruko, what are the steps to reproduce? I cannot seem to find a link from this
tab to the URL?
| Reporter | ||
Comment 4•24 years ago
|
||
Changed QA contact to andreasb@netscape.com.
QA Contact: teruko → andreasb
Comment 5•24 years ago
|
||
Comment 6•24 years ago
|
||
Sorry about the delay; I lost track of this one!!! My apologies !!!
This is definitely not JavaScript Engine. The reduced testcase I made
above has no JavaScript in it. It loads fine in NN4.7 and IE4.7.
It does not load in Mozilla. Using Mozilla binary 20010303xx on WinNT).
The problem lies in these two lines:
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=x-euc-jp">
<title>マリイプリマヴェラの今日の星占い</title>
If you have only one or the other of these, Mozilla loads the page fine.
That is: if you have that <META> tag but not the <title>, it loads fine.
If you have that <title> tag but not the <META>, it loads fine.
But if you have both; Mozilla won't load the page (but NN4.7 and IE4.7 will).
That is what is stopping the given URL from rendering correctly.
If you save the HTML for the site locally, add a <BASE> tag, and
delete the <META> tag, Mozilla displays the page correctly.
I will attach such a file below to prove this -
Comment 7•24 years ago
|
||
Comment 8•24 years ago
|
||
We can see from the second attachment above that removing the <META> tag
makes the whole site work perfectly in Mozilla. This is the problem
with both the site and the reduced testcase.
Reassigning to Internationalization for their expertise on charsets,
although perhaps it is Parser or DOM...
Again, my apologies for my delay on analyzing this!
Assignee: pschwartau → nhotta
Comment 9•24 years ago
|
||
I looked at the title string, it is not EUC-JP as indicated in the META tag, the
string is actully Shift_JIS. So the page is incorrect.
Reassign to ftang, do we still want to show the body after encoutering invalid
strings?
Assignee: nhotta → ftang
Comment 10•24 years ago
|
||
I think they fix the page. Mark this bug as Workforme
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 11•24 years ago
|
||
But what about nhotta's question at 2001-03-12 16:12 above:
> do we still want to show the body after encoutering invalid strings?
(For example, in the reduced testcase at 2001-03-10 19:47)
Comment 12•24 years ago
|
||
Changing QA contact to jonrubin@netscape.com. Jon, can you verify this bug? You
might want to open a new bug for nhotta's question at 2001-03-12 16:12 above.
QA Contact: andreasb → jonrubin
Comment 13•24 years ago
|
||
Reopening this bug. The original horoscope page has been fixed, but the behavior in Mozilla is still such that the body will not load if there are
invalid strings. If we do not load the page, we should indicate that an error is the reason for the page not loading. At that point, the user could
be given the choice to load the page anyway, i.e. "This page contains an error, load anyway?"
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 14•24 years ago
|
||
Because this may happen in many situations (e.g. multiple windows, page loaded
in mail view), I don't think alerting is not a good UE.
Other browsers behavior:
4.x - it does not abort the conversion, invalid characters are displayed as garbage.
IE 5.0 - shows nothing (same as 6.0).
Comment 15•24 years ago
|
||
In the status bar, instead of saying "Document: Done", perhaps we could load the
page (or not load the page) with the following status: "Document: Error on
page".
Comment 16•24 years ago
|
||
Change the summary from "This page is not loaded correctly", to "outupt warning
if unicode converter hit conversion error."
Mark this as Future.
Status: REOPENED → ASSIGNED
Summary: This page is not loaded correctly → outupt warning if unicode converter hit conversion error.
Target Milestone: --- → Future
Comment 17•24 years ago
|
||
mass change, switching qa contact from jonrubin to ruixu.
Keywords: intl
QA Contact: jonrubin → ruixu
Comment 18•20 years ago
|
||
-> to default owner (rather than ftang's WONTFIX)
Assignee: ftang → smontagu
Status: ASSIGNED → NEW
QA Contact: ruixu → amyy
Target Milestone: Future → ---
| Assignee | ||
Comment 19•19 years ago
|
||
Reduced HTML testcase now works.
Status: NEW → RESOLVED
Closed: 24 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•