Question
Marsh
US
Last activity: 26 Aug 2020 8:17 EDT
Pega 7 User portal launches in Quirks Document mode
Hi,
We upgraded from 6.2 sp2 to 7.1.7. Our Pega 7 user portal always takes Quirks Document mode by default. We use IE 9. Can you please tell us if this is being forced somewhere?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Yes Apoorva. If you are moving to Pega 7 and using the new technology that comes with it, you will need to be in standards mode and enable the HTML5 doc type.
When you come over from previous releases you may find some functionality does not work when running in standards mode. This is almost always because some of the features you brought over were originally designed with Quirks mode in mind and this will conflict with the HTML5 doc type. Often there are auto-generated, HTML5 compliant replacements for said features and you can upgrade them.
The first place I would explore is the HTML5 readiness wizard. Consider it analogous to a Pega guardrail report, scoped specifically to get you standardized for HTML5.
Use this in conjunction with resources like this: https://pdn.pega.com/user-interface/upgrading-your-application-to-html5-document-type-standards-mode
Yes Apoorva. If you are moving to Pega 7 and using the new technology that comes with it, you will need to be in standards mode and enable the HTML5 doc type.
When you come over from previous releases you may find some functionality does not work when running in standards mode. This is almost always because some of the features you brought over were originally designed with Quirks mode in mind and this will conflict with the HTML5 doc type. Often there are auto-generated, HTML5 compliant replacements for said features and you can upgrade them.
The first place I would explore is the HTML5 readiness wizard. Consider it analogous to a Pega guardrail report, scoped specifically to get you standardized for HTML5.
Use this in conjunction with resources like this: https://pdn.pega.com/user-interface/upgrading-your-application-to-html5-document-type-standards-mode
Then during your upgrade effort if you have any specific issues or functionalities you are having difficulties with, I would recommend you be as specific and detailed as possible when opening an support request or engaging the support community depending on your needs and the context of the issue.
Please let me know if this answers your question.
On your application rule, turn on the HTML5 doc type. If you migrated from PRPC, then this existing application rule will not have this checked.
New applications will have this on by default.
Marsh
US
Thank you, Rett. I thought Pega 7 as such needs IE 9 standards mode even if I don't opt to check the Include HTML5 doc type.
The issue we are having is that some of the core functionalities do not work if we turn on the HTML5 doc type. Having said that, NestedTabbedNavigation works only with HTML5 turned on.
Accepted Solution
Yes Apoorva. If you are moving to Pega 7 and using the new technology that comes with it, you will need to be in standards mode and enable the HTML5 doc type.
When you come over from previous releases you may find some functionality does not work when running in standards mode. This is almost always because some of the features you brought over were originally designed with Quirks mode in mind and this will conflict with the HTML5 doc type. Often there are auto-generated, HTML5 compliant replacements for said features and you can upgrade them.
The first place I would explore is the HTML5 readiness wizard. Consider it analogous to a Pega guardrail report, scoped specifically to get you standardized for HTML5.
Use this in conjunction with resources like this: https://pdn.pega.com/user-interface/upgrading-your-application-to-html5-document-type-standards-mode
Yes Apoorva. If you are moving to Pega 7 and using the new technology that comes with it, you will need to be in standards mode and enable the HTML5 doc type.
When you come over from previous releases you may find some functionality does not work when running in standards mode. This is almost always because some of the features you brought over were originally designed with Quirks mode in mind and this will conflict with the HTML5 doc type. Often there are auto-generated, HTML5 compliant replacements for said features and you can upgrade them.
The first place I would explore is the HTML5 readiness wizard. Consider it analogous to a Pega guardrail report, scoped specifically to get you standardized for HTML5.
Use this in conjunction with resources like this: https://pdn.pega.com/user-interface/upgrading-your-application-to-html5-document-type-standards-mode
Then during your upgrade effort if you have any specific issues or functionalities you are having difficulties with, I would recommend you be as specific and detailed as possible when opening an support request or engaging the support community depending on your needs and the context of the issue.
Please let me know if this answers your question.