33994 - In the last text field when a search is preformed the result is a bunch of garbled characters in the main window

Status: CLOSED DUPLICATE of bug 22980

(SeaMonkey :: Sidebar, defect, P2)

Description

[Rob Spain]

From Bugzilla Helper:
User-Agent: Mozilla/4.72 (Macintosh; U; PPC)
BuildID:    2000033010 



Reproducible: Always
Steps to Reproduce:
1.type something in the last text field
2. click botton directly under text field
3. notice a bunch of garbled characters in the main window

Comment 1

[Linda Baliman]

Reassigned to Kat Momoi, who is primary Rakuten contact.

Comment 2

[Linda Baliman]

*** Bug 34929 has been marked as a duplicate of this bug. ***

Comment 3

[Katsuhiko Momoi]

The last text input field is supposed be for e-mail
address only so that you can be on their mailing list.
If you enter anything other than that, you will get taken to
a page which says "Please enter a correct email-address".

There seems to be a bug here in that even when Auto-Detection
is on, it does not detect the encoding. This error page
is in EUC-JP but is not marked so.
I'll keep track of this bug in the CC line, but we need to assign
the QA contact to blee while I'm away from MtnView.
We need to do 2 things:

1. Ask Rakuten to put in a met-tag on this error page. 
   That will fix this problem.
2. We also need to find out why auto-detection does not work when
   the page is loaded from the sidebar. This is probably an
   i18n bug. Possibly a duplicate of an existing bug.
   
   If so, let's keep this bug open for #1, which can be closed
   when Rakuten changes their page.

Sending it to bobj.

Comment 4

[bobj]

Last night's tip build does strange stuff in the sidebar.
But I went back and tried this with the Beta1 build, 2000032306, and it
WORKSFORME.  The first time I set autodetect, nothing changed, but when I
clicked on the button in the sidebar again, it loaded fine.

Comment 5

[bobj]

Nevermind.
If I don't have autodetect set before clicking the button, it gives me a
different page (the error page mentioned earlier).  If I do have it set,
it gives me a confirmation page.  So, autodetect is failing on the error page.

Comment 6

[bobj]

If I have EUC-JP selected and autodetect is on, then the error page is
displayed correctly.  So is this an ambiguous page and then the autodetector
falls through for the default?

Comment 7

[Frank Tang]

Sorry, this bug do not include enough information for me to debug. What is the 
URL ? What is "JA sidebar tab Rakuten [ichiba]"? Is this a sidebar that we ship 
with Japanese localized build ? If so, can someone tell me how can I add that 
into my English build ? Also, what is "the last text field"? Is it the last text 
field inside the "Rakuten tab" ? IS that a Internet Search ? or something else ?
If it is a Internet search, can someone attached the Internet search src file ? 

Comment 8

[bobj]

You can add this in any build by hitting the customize link and adding "Rakuten"
which is listed under "International" 

ftang> Also, what is "the last text field"? Is it the last text 
ftang> field inside the "Rakuten tab" ?

I assumed so. It fit the description.  I tried this on the Beta1 build because
last Thu night build had the double-sidebar bug.

Comment 9

[Rob Spain]

even with the proper charactor encoding the error is still there at least on Mac.

Comment 10

[Katsuhiko Momoi]

The problem still occurs with 4/21/2000 Win32 build.

Comment 11

[Frank Tang]

two problems
1. the return page do not have meta charset so it won't display correctly. 
However, if you do label it , then it will crash because of the problem in the 
parser that vidure use a interger for the parser key but we use that key as 
nsIDocument
2. the auto detection code does not work. But that is a seperate issue. (see bug 
22980)
Mark this as dup of 22980

*** This bug has been marked as a duplicate of 22980 ***

Comment 12

[Linda Baliman]

Takashi Yoshida, rakuten.co.jp, added to cc-lits

Comment 13

[Katsuhiko Momoi]

This problem has been resolved with a fix checked in connection Bug 22980,
which dealt with Auto-detection failure. If Auto-detection is turned on, the
page is displayed corectly. If not, then it will work only if the fallback encoding
is EUC-JP. This is the extent to whih the client side can go for this problem.

I notified the Rakuten webmaster requesting them to insert a meta charset tag
on this page. That is the server-side problem.

Marking it verified as a duplicate.

Comment 14

[Rob Spain]

works great marking as closed