Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Popup msg window not shown per skin styles



The "Work object is already open" message popup is not shown fully per the skin styles.
It does get some of the styles. This means that on our high contrast skin, the popup dialogue message is not getting the black background for the page that the skin specifies. It is however getting the cyan and yellow text which makes the text almost invisible on the dialogue message.
Users who require a high contrast screen will not be able to read the text.

We could reproduce this problem using any OOTB skin (which changes background colour) and check this behaviour.
We have noticed this issue only the "Work object is already open" message popup mentioned in the SR.
CompositePortalConflict is the HTML rule associated with the popup and it is a final rule.

Steps to Reproduce

Change the skin on a portal.
Open a workobject.
Try to reopen the same workObject.
A pop up appears informing the user that WO is already open and would he like to open it again. This popup does not pickup the style from skin.


This issue is resolved through the following local change:

It seems that since there isn’t any reference in CompositePortalConflict that is non-final, a hotfix cannot be provided to resolve this issue.
We advised that this issue is of minimal impact to accessibility. The problem being that the popup doesn’t match your skin on high contrast; which has a black background. Visually there is some inconsistency with it being white. But at the same time it is a type of ‘alert’ message so a different colour for the popup window is justifiable and even beneficial in terms of raising user awareness.
The primary reasons users have high contrast is susceptibility to brightness (white background). For such a small visual area as the warning message this really should not be a problem. Users will not see it often enough, for long enough and it’s not a large area of the screen. The text is black on a white background so has good default contrast. The text is also not too small (i.e. acceptable by WCAG standards).

Additionally, there was a problem with yellow colour on white brackground used for the pop-up header which isn't acceptable and not readable. This is because of other changes made for accessibility.
To overcome this, we suggested to change foreground using Branding wizard for Traditional Portal -> Navigation (left).
The traditional portals aren’t used anywhere so that style won't affect anywhere else on user normal screens so it's considered safe to apply these changes using branding wizard.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us