Hi,
Currently we are using HTMLB tags and the Design2003 for developing BSP applications.
However, most of the users use Imacs with Mozilla or Safari. The BSPs give a short dump since these browsers are not supported.
Hence, I modified the IF_BSP_ELEMENT~RUNTIME_IS_VALID method in the CL_HTMLB_CONTENT class so that the browser check is not carried out:
CASE design.
WHEN CO_DESIGN_CLASSIC.
m_validator->browser_check( request = request ie = 501 nn = 620
msg = 'Dieser Browser wird nicht unterstützt.'(004) ).
WHEN CO_DESIGN_2002.
m_validator->browser_check( request = request ie = 550 nn = 620
msg = 'Dieser Browser wird nicht unterstützt.'(004) ).
WHEN CO_DESIGN_2003.
*{ DELETE R3DK902446 1
m_validator->browser_check( request = request ie = 550 nn = 700 moz = 9999
msg = 'Dieser Browser wird nicht unterstützt.'(004) ).
*} DELETE
ENDCASE.
The BSP applications now run fine in both browsers except 1 feature - collapsing trays (which I can avoid using).
My question is, is it preferable to use HTML tags instead so that the BSPs run (without making changes to CL_HTMLB_CONTENT class) or use HTMLB tags (and delete the browser check from the CL_HTMLB_CONTENT class)
Thanks.
Your choice I would say, perferably it's not a change I want to make every SP update.
The User Agent switcher works quite well to avoid the problem as well with Mozilla
I can see Brian wrote as quick as I did 😔 so you got it twice
Rohini,
I always wonder about the stickers that one finds on electronic gear: "warranty void if broken". This probably applies to your code changes as well.
Would recommend as background to see note 598860. In priniciple Safari is handled as IE6 browser (last few SPs), and Mozilla support is scheduled for upcoming SPs (620SP49 and 640SP11).
As to what is preferable, it is your call. Either way the support is for you to handle at the moment. We will not handle any OSS problem tickets on this topic.
brian
Add a comment