htmlb Browser Support

[Former Member]

Has anyone tested the different htmlb tags on browsers not officially supported by SAP/BSPs? We need to support more browsers than SAP and have done some preliminary testing of some simple components (textView, inputField, and button) on Netscape (even on a Mac) and Mozilla to see if we can use these components on the different browsers. If anyone else has done similar type testing, it would be nice to compare notes/share the results. We would like to end up with a spreadsheet listing the htmlb components and which browsers seem to handle them successfully.

Note that even to test on unsupported browsers, we had to define our own zzcontent to keep the SAP-standard content from erroring out due to browser-type.

[Former Member]

Hello Connie,

I tried my BSP's at an Apple iMac with MacOSX 10.2.8. I only got errors with the htmlb Tags at Safari Browser and IE for Mac (I used inputfields, buttons, DDLB).

Here my Posting for that, mayby there are helpful answers for you:

Best regards,

Timo

[Former Member]

Here is what we did to be able to test htmlb tags on different browsers:

1. Create a class that has CL_HTMLB_CONTENT as a superclass

2. Redefine the method IF_BSP_ELEMENT~RUNTIME_IS_VALID in our new class (zclb_htmlb_content) and comment out the

statements that do the browser check; for example:

• m_validator->browser_check( request = request ie = 501 nn = 620

• msg = 'Dieser Browser wird nicht unterstützt.'(004) ).

3. Create a BSP Extension in SE80 called z_ext_test with folder zzcontent that refers to the

zcl_htmlb_content class as its element handler class

4. Include the following reference in your View:

<%@extension name="z_ext_test" prefix="zhtmlb" %>

5. Use the new zzcontent instead of content in the view where we are going to put htmlb tags to try.

Put this at the top:

<zhtmlb:zzcontent>

This at the bottom

</zhtmlb:zzcontent>

Hope this helps,

Connie

[maximilian_schaufler]

Yeah, perfectly clear so far.

But you didn't mention any specific user agent, that you are using for your tests.

Debugging further into the HTMLB classes starting from point of browser check I found this code in

METHOD IF_HTMLB_ELEMENT_DELEGATED~DO_AT_BEGINNING

CASE user_agent_type.
	WHEN ihttp_user_agent_ie.
	  IF user_agent_version < 600. device = 'ie5'.
	  ELSE.                        device = 'ie6'.
	  ENDIF.
	WHEN ihttp_user_agent_nn.
	  IF user_agent_version < 700. device = `nn6`.
	  ELSE.                        device = `nn7`.
	  ENDIF.
	WHEN OTHERS.                   device = `ie5`.
ENDCASE.

I think this part is very important for your tests, as there might be different results using different values for "device" here. Some javascript files are of course user agent dependent, and therefore not made for other browsers - so results may differ.

Maybe you can use this as an extension to your test environment, to not only disable the browser check but also allow for a "free choice of user agent" - otherwise you will always have the "ie5" style and javascript files for other browser.

Regards,

Max

[Former Member]

Hi Max,

I'm testing my BSPs on Mozilla and I noticed that by default, the IE5 files (eg: sapUrMapi_ie5.js) are being used which obviously causes problems for Mozilla since it is based on NN.

As you mentioned above, I specified the device as 'NN6' for 'Others'. However, the default IE5 files are still being used.

As I debugged I noticed that the browser id is "NN6" and so is the device, but finally when the BSP is displayed, sapUrMapi_ie5.js is used.

Any help regarding this would be greatly appreciated.

Regards,

Rohini.

[former_member181879]

Rohini,

Either one of two cases: (1) the browser is sending out an identification string that makes us recognize it as IE5 and not a Mozilla, or (2) there might still be a bug.

Please send us an OSS message to quickly look into this. If you should feel like debugging, the interesting code will be in CL_HTMLB_HEADINCLUDE (local implementation section). Hmmm.... as I look at that code, I see...hmmmm... will try to complete a note for you in the next day or two.

bye, brian

[former_member181879]

Rohini,

The experts here in the team has shown me that I forgot to look also other parts of the code, and that everything works fine. However, we did have the problem you describe long time. We just can not remember where/when. Can you please send us an OSS message to look into your system and decide again what we fixed. Also check your SP against the version from where we actually started to support Mozilla.

Thanks,

brian

[maximilian_schaufler]

Hi Connie,

I haven't done any specific tests, but I tried to display my BSP application on Mozilla as well (I'm using the User Agent Switcher to "fake" IE).

Used htmlb elements that seem to work allright:

DateNavigator, Buttons, Trays, Dropdowns

(although there is the known issue of Mozilla not interpreting the cursor:pointer e.g. on the datenavigator)

The Tree element is not working, subelements in the tree don't open up.

Now I don't know what results you would get if you would use another "supported browser's javascript", as I just displayed the IE6-results in Mozilla.

What supported browser type are you using when accessing your applications in not-supported browser?

Maybe there are some major differences in compatibility if you compare IE6-output with NN7-output, especially when using Mozilla?

That would really be interesting to learn.

Also, if you could share some code so that others could configure a small testing environment (based on zzcontent you mentioned) quickly that would be helpful. I once debugged into the code where browser type was checked, but if you already have some working example that would be nice to have.

Best regards,

Max

[former_member202342]

Hi Connie,

You may have already seen it, but there is a complete guide focusing on htmlb provided here on SDN. In this guide, each visible control (such as button, textView, etc.) has three subsections, "Usage and Types," "More Info," and "Control API." The "More Info" section for each visible control lists known browser compatibility issues. Unfortunately, since you stated in your post that you need to support more browsers than SAP and we [SAP] probably only tested against those browsers that we planned to support, this may be of no use to you. A link to the guide is listed below.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/sap htmlb guidelines

Best Regards,

Mike

[Former Member]

Hi Connie,

I have tested some components with FireFox and could not find any problem yet. But of course this was no extensive test.

Kind regards

Francisco