** Observed with 3/16/2000 Win32 build ** This is really an exasperating set of problems. Our JPN Sidebar partner, Arukikata, very recently seems to have changed their main page design and this is causing 3 problems of display. It is particularly distressing because we are supposed to be show-casing this site for the Beta Sidebar program, yet the left half of the page is garbled and not shown as Japanese any more. I have done some investigation but not in-depth enough to pinpoint all the causes. Some I know to be a potential problem once a prevaling bug is removed. 1. The left side of the page does not show as Japanese at all. This area is constructed out of a table and <font class...> definition which I believe is read from an external .css file. I changed the font prefs for Mozilla to use the user's fonts only but this does not correct the problem. You can use erik's great view utility to see what is defined in the external .css file. http://webtools.mozilla.org/web-sniffer/ Just click on the link on this line: link href="/js_script/arukikata.css" rel="styleSheet" type="text/css"> in the page the view utility returns. ** If you save this page as a local file, the left side displays OK as Japanese. Since I don't have the .css file locally,that seems to resolve the problem. Thus it points to the .css deifnition as a possible cause. BTW, 4.72 does not have any problem with this even honoring the page's font definitions. 2. The next problem is that of JavaScript. Clicking on some of the links at the left side is supposed to bring up a list of countries in pop-up window. This does not work at all. I'll attach an image taken by 4.72 so that you can see that 4.72 can do this. These JS calls fail in Mozilla but work in 4.72. e.g. <A href="javascript:changeUrl(0);void(0)" onclick="changeLayer(0,event)"><B>EUROPE</B></A> The word EUROPE is in Japanese but is shown here in English. As you can see from an 4.72 image below, this brings up a list of European countries to choose from in a pop-up under 4.72. 3. #2 brings up yet another problem. These pop-up countries names are read in from an external JS file. This means that if the countries names can be read in this way after #2 is fixed, they will show as garbage due to a known Bug 28474, which should have been fixed for Beta1 because the fix is already known. You can see the source of the .js file which sends the country names by using erik's View Utility above. The .js file for country data is: <SCRIPT SRC="/js_script/data.js"> Just click on this link in the page erik's View Source utility returns. So we have a big problem here for Beta 1. Arukikata has a contract with us and we are obligated to have Sidebar feature work for them. But this Browser display problem makes it difficult for us to honor it properly. So, 1. We need to find workarounds for #1 and #2 or fix them outirght. 2. We also need to fix #3 in Beta 1 for a fix for #2 to be effective. 3. There needs to be some coordination with our partner to also see if they can fix some things on their web site to resolve these problems. 4. To accomplish 1-3. we need to find the exact causes of these problems. I'm sorry that I had to put in 3 problems in 1 bug but I hope you undestand why given the context of these problems. We need solutions of one kind or another for Beta 1.

Is #2 above possibly a layer problem?

1. The web site feed different html to 4.7 , mozilla and telnet. Try to load them in 4.7 and seamonky and do a view-source. The content are different. 2. The problem of display is NOT related to css, but external JavaScript- That is a dup of 28474. I believe both problem #1 and #3 can be fixed by 28474. 3. I talk to harishd about the 2nd problem, we look at it and it seems they are using layer to do the popup. According to harishd, we won't support layer in mozilla. Add Eric Krock to to cc list. Reassign this to jbetak because he also wrok on 28474

Here are the URLs you need to resolve all LAYER problems and educate customers. All--please bookmark each of these URLs. 1) statement on Nav4 Layer DOM and MSIE DOM non-support and list of equivalent W3C standard features: http://sites.netscape.net/ekrock/standards.html 2) template for creating and sending an email to notify site owners that their site contains Nav4 Layer DOM code and must be updated to support standards: http://sites.netscape.net/ekrock/fixit/layer.html 3) My personal FAQ for general Gecko and standards info: http://sites.netscape.net/ekrock/answers.html Normally, I would email the customer myself directly and close out the bug as INVALID. However, in this case, it sounds like you have a relationship established with the customer already, so I will let one of you who knows the customer generate and send the email instead so you can make it less generic and more customer-specific if you wish. Thanks!

OK. I've been dealing with this partner. I can take it from here on the layer issue. Can we get Bug 28474 fixed for Beta 1?

I sent email to see if Arukikata will change its content to not use layers. I included links to ekrock's documents. momoi will follow-up with Arukikata on Monday JST.

This bug has 2 issues: (1) external non-ASCII JS files and (2) page with layers fails. I'll move (2) to a new bug (which will probably get a WONTFIX) and keep this bug for (1).

Since this bug is reduced to the external non-ASCII JS file bug, I have dup'd it to bug 28474. *** This bug has been marked as a duplicate of 28474 ***

I moved the layers dependency issue to bug 32288.

I just verified in Bug 28474 that #1 of the 3 problems does not occur any more. There is still issue #3, which should be the same thing but it would be best to wait until Arukikata fixes the layer porblem in #2. They will do so by the end of the month. Please wait to check the workaround for the layer problem and then verify #3. Or if you prefer, you can assign the verification to me since I have to check this status for the JPN sidebar project anyway. Thanks.

Changed QA contact to momoi@netscape.com

Arukikata re-designed the page so that problem #2 does not occur any more. The remaining problem was taken care of in Bug 28474. verifying this bug as a duplicate of that but.

Hiroshi Doi, arukikata.do.jp, added to cc-list Marked Not "Netscape Confidential"