Navigation problem

[Former Member]

We have XMII 12.051 lastest build , JAVA SP 16 on the AS.

We have some menus on the left pane of XMII, when we use IE 6.0 works fine, we can access the childs of the menus, but in Firefox 3.0.4 we cannot expand the menu to access the childs.

Our Java VM in the server and on the workstations is 1.4.2_16

Please advise.

Thank you.

[jcgood25 · Accepted solution]

Sounds like it may be a browser sniffing issue for version settings.

In the appropriate them file (DynamicHomePage.xsl) adjust line #26 (or thereabouts)

from

<xsl:param name="BrowserType">Unknown</xsl:param>

to

<xsl:param name="BrowserType">Microsoft</xsl:param>

This will ensure that the html building exercise done by the DynamicHomePageLibrary uses all of the full features.

Regards,

Jeremy

[Former Member · Accepted solution]

Jeremy :

First of all , thank you for your help.

I have found only 1 DynamicHomePage.xsl file in directory

D:\usr\sap\XMD\JC00\j2ee\cluster\server0\apps\sap.com\xapps_xmiiear\servlet_jsp\XMII\root\Themes

I have changed it, and no luck, do I need to restart the server for it to change?

Another thing in the error console from firefox I get several warnings:

Warning: Error in parsing value for property 'cursor'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/logon/css/main2ns.css

Line: 103

Warning: Expected ':' but found 'COLOR'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/logon/css/main2ns.css

Line: 317

Warning: Error in parsing value for property 'border-left'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/logon/css/main2ns.css

Line: 326

Warning: Error in parsing value for property 'border-bottom'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/logon/css/main2ns.css

Line: 339

Warning: Error in parsing value for property 'border-top'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/logon/css/main2ns.css

Line: 341

Warning: Unknown property 'VALIGN'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/XMII/Themes/src/HomePage.css

Line: 29

Warning: Error in parsing value for property 'border-style'. Declaration dropped.

Source File: http://arbassrv11.sa.esab.org:50000/XMII/Illuminator?service=Personalization&sniffer=Netscape,5,630,...,

Line: 0

Warning: Selector expected. Ruleset ignored due to bad selector.

Source File: http://arbassrv11.sa.esab.org:50000/XMII/Stylesheets/XMII_UI.css

Line: 1

Thanks.

[jcgood25 · Accepted solution]

After logging into the Personalization home page do a view...source in your browser and tell me what you see in the DEBUG INFO html comment section at the top (make sure not to view source in the iframe).

[Former Member · Accepted solution]

This is the source view of the page http://host:port/XMII once i am logged in.

thanks.

< <!--

DEBUG INFO

IllumLoginName: fcorrea

BrowserType: Netscape

BrowserVersion: 5

isIE4Up: false

isNetscape6Up: true

isCompliant: true

PageWidth: 1280

Navigation Width: 12%

TabsPerRow: 10

TabsNeeded: 9

TabWidth: 10

HeaderMaxHeight: NaN

HeaderTableHeight: 50

FooterMaxHeight: 24

FooterTableHeight: 24

DisplayAreaHomePage: /XMII/Menu.jsp

-->

[jcgood25 · Accepted solution]

I tried with Firefox 2.0.0.18 on versions 11.5, 12.0, and 12.1 with similar results as you are experiencing, and it looks like a problem in the home page building process when it sniffs out Netscape from the Firefox session.

Short term solution - use IE

[Former Member · Accepted solution]

Hmmm , problem is users have Linux, cant use IE.

Well guess I will have to report it.

[Former Member · Accepted solution]

Hi Daniel,

I got the same problem. Child menus didn't open, when I use the Netscape based Browsers (i.e. also Firefox 1, 2 and 3), with IE no problems, menus are working as expected.

Since I was rather annoyed about this problem and I don't like IE really, I started searching the reason for the problem last weekend. And I found the reason. Upon opening the portal MII builds the HTML page dependent on the type of browser you are working with (IE or Netscape). Therefore the JavaScript Menu Handler distinguishes between these browsers, whenever you click on any menu item. The routine, that handles clicks for Netscape based browsers, has a bug.

The JavaScript Menu Handler is located in the file: <XMII_Home>/Themes/src/ExpandingOutline.js. The (blank) line 7 of the function getElement is the problem:

        function getElement(tagType,tagValue,index) {
                // init the return element
                var element = void(0);
                // is the type an id
                if (tagType.toLowerCase()=="id") {
                        // does the value return an object

                // is the type a name
                } else if (tagType.toLowerCase()=="name") {
                        element = getNamedDocElement(tagValue, index);
                // is the type a tagname
                } else if (tagType.toLowerCase()=="tagname") {
                        element = getNamedDocElement(tagValue, index);
                }
                // return the element
                return(element);
        }

Insert into line 7 the following JavaScript code:

          element = getNamedDocElement(tagValue, index);

and save the file.That's all.

BTW, I cannot understand, why this problem hat not yet been fixed by SAP. I assume, that the origin of the separation of browser handling results from old versions of IE and Netscape. But actually (since IE 5 and higher), all Browsers understand the JavaScript getElementById, so one could realize only one menu handler for all types of browsers.

Bodo.