INC-140482 · Issue 594166
Handling added for last focused element in custom modal
Resolved in Pega Version 8.3.5
Using Shift-Tab can take the focus out of the modal window when using a custom modal template without the "X" icon in the header. The issue did not happen when using "tab" key press to traverse the modal. This was a missed use case for the last focused element being div and tabindex as 0 combined with using a custom template which doesn't have close button. This has been resolved.
INC-138803 · Issue 591926
Mouse event Cross-site scripting updates
Resolved in Pega Version 8.3.5
Cross-site scripting protections have been added to mouse event attributes.
INC-138701 · Issue 596612
Multi Select populates values for Page group
Resolved in Pega Version 8.3.5
The Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source.
INC-139156 · Issue 592150
Pasting image lands in correct location
Resolved in Pega Version 8.3.5
When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich text editor, and has been resolved.
INC-132771 · Issue 584963
Refresh section of MultiSelect properly handles refresh section
Resolved in Pega Version 8.3.5
On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.
INC-137785 · Issue 589064
Removed unneeded scroll bars on optimized table
Resolved in Pega Version 8.3.5
Horizontal and Vertical scroll bars were seen when using an optimized table in the Case Manager portal even when they were not needed. This was traced to the table having "overflow: auto" set, and has been resolved.
INC-132569 · Issue 595177
Resolved case detail overwrite
Resolved in Pega Version 8.3.5
In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.
INC-144600 · Issue 599916
Skip links enabled for all users by default
Resolved in Pega Version 8.3.5
In order to improve the UI experience, the isAccessible check for skiplinks has been removed. This allows users to navigate the content of the page using skip links without having to have their access group be set to accessible mode.
INC-142034 · Issue 596085
Tab moves to next field after autocomplete
Resolved in Pega Version 8.3.5
After entering the value on an autocomplete field, it took two presses of the Tab key to move to the next field. Investigation showed that on autocomplete keydown of the tab key, there was an event preventing the expected default behavior. This has been resolved.
INC-135523 · Issue 590437
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.3.5
When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.