FOUR-19561: In a screen with more than one page, when I zoom more than 150% I return to the first page

[fagubla]

Issue & Reproduction Steps

1. Create a process: Start Event - Task - End Event.
2. In the Task, create a screen with 2 pages. Page 1 has a Page Navigation button to take the user to the second page.
3. Save the screen and publish the process.
4. Start a case.
5. Click on the Navigation Button.
6. On the second page, zoom to 150%.

Current Behavior:
The screen returns to the first page.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-19561

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:deploy

[cypress]

screen-builder    Run #1773

Run Properties:   Passed #1773  •  b3816b145c: FOUR-19561: In a screen with more than one page, when I zoom more than 150% I re...

Project	screen-builder
Branch Review	bugfix/FOUR-19561
Run status	Passed #1773
Run duration	09m 02s
Commit	b3816b145c: FOUR-19561: In a screen with more than one page, when I zoom more than 150% I re...
Committer	Fabio Rodolfo Guachalla Blanco
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	19
Skipped	0
Passing	366
View all changes introduced in this branch ↗︎

[fagubla]

@caleeli all tests are green

[caleeli]

approved

[pmPaulis]

@boliviacoca @ryancooley
The Storybook is showing this issue:

Package libasound2 is a virtual package provided by:
  liboss4-salsa-asound2 4.2-build2020-1ubuntu3
  libasound2t64 1.2.11-1build2 (= 1.2.11-1build2)

E: Package 'libasound2' has no installation candidate
Failed to install browsers
Error: Installation process exited with code: 100

This is fixed in the PR:
#1785

Regards,

[pmPaulis]

@ryancooley @boliviacoca
In this PR is failing the CICD deploy-EKS, I created the following ticket
https://processmaker.atlassian.net/browse/SCO-27217
Regards,

[tokensPM]

QA server K8S was successfully deployed https://ci-52f60887da.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-52f60887da.engk8s.processmaker.net

[pmPaulis]

Update with release-2025-spring and marked Spring Review

[pmPaulis]

the unit test issue is not related with the changes

Filter (Tests\Filter)
 ✘ Compare data integer
   │
   │ Failed asserting that actual size 2 matches expected size 1.
   │
   │ /opt/processmaker/tests/unit/ProcessMaker/FilterTest.php:88
   │ /opt/processmaker/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:176
   │

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[pmPaulis]