Portal rendering errors using IE10

Question

Hi,
We've recently patched all of our SAP systems (portal and backend) and checked we're at the requisite level for IE10 support in the PAM.
We're currently in the process of testing all of our applications for IE10 compliance and have identified two issues which someone may have experienced or can advise upon:
Issue 1) SAP Transaction iView (ITS) raising following error in popup dialog box 'The application was stopped due to a critical rendering error.  The IE compatibility view is not supported (Note 1586993).'
This iView connects from our portal (EP 7.0 EHP2 SP14) to a backend SAP ERP (ECC) system patched to NW EHP3 (SP09).
Note 1586993 is not particularly helpful as it simply states 'The administrator must assure, that IE frame content is compatible and correctly configured'.
Additional research identified note 1970427 which I have applied to the backend system - subsequently I added application parameter 'sap-ie=EmulateIE8' to the iView (both within the iView config and at runtime) but this made no difference to the behaviour.
I checked the user's framework page and the 'Browser Document Mode' iView is linked in and has it's property set to 'IE=EmulateIE7'.  I tried moving this iView further up the order sequence (i.e. putting it first) as well as changing it's setting to 'IE=EmulateIE8' but once again this had no effect on the behaviour.
I notice when logging into the portal, at first the F12 console shows Browser Mode = 'IE10', Document Mode = 'IE5 quirks' but when the problematic iView renders, the Document Mode changes to 'Quirks' which I'm assuming is why the error occurs.
I'm not sure what I can do to make the iView render in 'IE5 quirks' mode?
This iView is called dynamically at runtime with some URL parameters that are passed to the backend transaction so I cannot follow the advice in note 1590563.
Issue 2) BSP iView for 'CRM Web Interaction Centre' - all F4 dialog popups are displaying empty with no content, e.g. Inbox search help for classification field
This iView connects from our portal (EP 7.0 EHP2 SP14) to a backend SAP CRM system patched to NW EHP2 (SP04).
I tried setting my user parameter CRM_THTMLB_IE_COMP to 'IE8' but this had no effect.
Note, if I set the IE10 property 'Display intranet sites in Compatibility View' both issues above are resolved.  We're trying to avoid this as we've had this setting in place for a number of years and it affects the correct operation of non-SAP applications.  Given there are numerous ways of making SAP operate by emulating older compatible IE versions, I expected we could work around needing to do this but it may be a last resort.
Please offer any advice you can as it will be much appreciated.
Thanks,
Alan

Answer 1

Hi Lawrence,
We have a mixture of custom and SAP standard portal applications developed over the past 10 years.
UI technologies include: Java Server Pages, Web Dynpro Java, ITS, BSP, Web Dynpro ABAP and BEx.
Quite honestly, the portal hasn't proved to be the best SAP product in our experience, and we've tried hard to keep it patched up-to-date. OK, it offers integration and navigation but that capability is offered by the Fiori Launchpad, albeit presenting new challenges and possibly some limitations on the integration of existing applications.
We could have opted to integrate the Fiori Launchpad with the portal but decided it was cleaner to perform a standalone installation on our newly built NetWeaver Gateway server.
We're starting our Fiori journey by implementing selected SAP delivered apps for the first pilot projects then plan to replace or migrate existing portal applications.
We'll replace any custom Java apps with UI5 apps built in-house as we need to rationalise UI technologies and this one is a prime candidate given the lack of in-house skills and SAP direction. 
Our expenses application is currently an SAP ITS transaction iView in the portal but will be replaced with the My Travel and Expenses Fiori app this year.
CRM Transaction Launch isn't used often so we may kill it off.
BSP's are solely in the CRM area and I read they're not supported yet in the launchpad - hopefully they will be in a future version (?).
We have quite a few Web Dynpro ABAP applications so these will take some time to rewrite if required (assuming we cannot port them).
BEx may be replaced with Business Objects or taken out of the portal in favour of the Excel version we also run (portal offers little value for massive reports so users download to Excel in any case).
My understanding is that the Fiori Launchpad does support integration of legacy SAP technologies so we'll need to gauge if and when we each a tipping point where any remaining portal applications can either be integrated with the launchpad or replaced with alternative new applications. Obviously all of the above will take time.
We're working on developing a custom Fiori/UI5 theme and have hit a few snags. We've just patched to SP09 on our development Gateway system but the UI Theme Designer is still a bit flaky (we run the tool there but could also do this on our portal). My colleague is now trying the cloud version to see if that proves a more viable route. In either case we'll be seeking SAP assistance as we really want our UI5 apps to adopt recently developed corporate branding rules. Our portal currently uses a copy of Gold Reflection with simply the SAP logo replaced for our company's logo.
If you have any further queries just let me know, or similarly advice/experience on the above.
Hope this helps.
Alan