on 12-29-2014 9:27 AM
Hi,
i tried several possibilities to render the Portal login page in standard mode.
By default IE renders in Quirks mode.
I tried the following :
- Adding tags in the login page at the top
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
Result : Line shows up as first entry in the body.
- Setting the tag <!DOCTYPE html> by using SAP note 1697320 (Adding
doctype to the logon application pages)
Result: doctype is set in WebAS Login (e.g. /nwa) , but not in the portal login.
- Adding the header information by using the response object :
<% response.setHeader("x-ua-compatible", "IE=Edge"); %>
Result : Does not show up in HTML
Anyone has another idea ?
Thanks,
Kai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kai Unewisse,
I am also getting this issue please tell me your issue is resolved or not.
Resolved means tell me the steps.
Regards,
Durga Rao.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kai,
If it is portal component,and you have portal request you can try this:
portalRequest.getServletResponse(false).addHeader("X-UA-Compatible", "IE=Edge");
Please note that in NW versions this is not the way to customize your logon page, you can read here:
BTW, IE10 and above render in standard by default.
Regards,
Naama
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Naama,
The sap.com~tc~sec~ume~logon~ui.war file is not an APC, how do you get portalRequest and where are you referring this to be used.. in JSP??
portalRequest.getServletResponse(false).addHeader("X-UA-Compatible", "IE=Edge");
In case you are referring response object in JSP, I've never found that as useful in adding the above as <meta> tag during runtime. Did you ever implemented this and successful? Can you please share me the code snippet or a case study?
Thanks, MS
Hi,
Just got these steps you can perform to apply a workaround that enables rendering of a
<!DOCTYPE html>
for logon screens in Portal and I decided to share it here as it might be helpful until SAP implements that by default:
This should enable a customer to write a markup that will successfully render in different IE versions in "Standards" Mode.
"" ** \\ Before doing it I suggest you to backup the current content so you will be able to rollback the settings in case of any issue you get during this process. // ** ""
1) Create iView: copy Portal Applications -> com.sap.portal.runtime.logon -> certlogon and paste as PCD object "Portal Content".
2) Edit the permissions of the newly created iView add the Group Everyone with both "Admin read" and "End User" checked.
3) Edit the iView using the support "PCD Inspector" tool and add for it a String property with id "com.sap.portal.prt.html5.compliant" and value "true"
4) Apply SAP note "#1713259 - PRT support for HTML5 doctype" Setting the PRT html5.compliant property to "iViewDependent"
5) Follow SAP documentation http://help.sap.com/saphelp_nw73/helpdata/en/1a/3afd4e641b8f42ac07bb77fe30375b/frameset.htm to create your own authscheme.xml file in the custom file replace the entries
"<frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget>" with
"<frontendtarget>pcd:portal_content/certlogon</frontendtarget>"
***If you created the iView under a different ID or location adjust accordingly.
6) Restart the whole cluster for the authscheme.xml configuration to take effect.
Inside the Portal the different logon JSP files are only part of the markup maintained by the Portal Runtime. The logon screen can appear for just one iView inside of a Page of other anonymous iViews.
As such if other iViews do not declare that they are HTML5 compliant the Logon iView will render again in Quirks mode.
Hope this helps,
Edison Büttenbender
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kai,
Please use the <meta> tag as below and please also confirm that you have added this <meta> tab just after <head> tag.
<!doctype html>
<html>
<head>
<meta http-equiv=”X-UA-Compatible” content=”IE=8">
All references to custom CSS and JavaScript files go after this <meta> tag.
Other attributes are:
•“IE=edge”
•“IE=10″
•“IE=EmulateIE10″
•“IE=9″
•“IE=EmulateIE9
•“IE=8″
•“IE=EmulateIE8″
Thanks,
Hamendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kai,
1.) Note 1697320 -- or better: the implementation -- should change. As suggested in and repeated now in my "main thread" about this issue, with response from SAP before, , I would open an OSS message, as the reason to restrict the possibilities of the login page especially for the portal do not hold any longer.
2.) "Adding the header information by using the response object: <% response.setHeader("x-ua-compatible", "IE=Edge"); %> Result : Does not show up in HTML" -- of course not. It should write it into the http header, which anyhow is a valid (even generally the best) way to influence the mode. Anyhow, please check with httpWatch or a similar tool if the header gets really set AND if it is the only x-ua-compatible Header... (and the correct form also would be "X-UA-Compatible", but I'm not sure if IE cares; anyhow, httpWatch always signals the name as lower case even if it is a mixed upper/lower case, don't let you irritate by that).
Best regards
Detlev
PS: Not about the logon page, but the mixture of portal and non-portal stuff within the portal and the different IEs, there's a good overview:
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.