Skip to content

FOUR-32573: Fix inbox list scrolling - #8986

Open
eiresendez wants to merge 1 commit into
developfrom
task/FOUR-32573
Open

FOUR-32573: Fix inbox list scrolling#8986
eiresendez wants to merge 1 commit into
developfrom
task/FOUR-32573

Conversation

@eiresendez

Copy link
Copy Markdown
Contributor

Issue & Reproduction Steps

On /inbox, a task list containing enough items to exceed the available viewport height is clipped at 100% browser zoom. Users cannot reach the end of the list or its pagination controls without reducing the browser zoom.

To reproduce:

  1. Open /inbox with more than 15 available tasks.
  2. Keep the browser zoom at 100%.
  3. Use a 1280×720 viewport or another viewport where the task list exceeds the available height.
  4. Attempt to scroll to the pagination controls.

Solution

  • Allow the Inbox content container to scroll when its content exceeds the available viewport height.
  • Preserve the existing scrolling behavior for Process and Dashboard views.
  • Keep the change scoped to ParticipantHomeScreen.vue.

How to Test

  1. Open /inbox with more than 15 tasks at 100% browser zoom.
  2. Confirm the complete task list and pagination controls are accessible through vertical scrolling.
  3. Repeat the verification on the Inbox, Priority, and Drafts tabs.
  4. Confirm Process and Dashboard views retain their existing scrolling behavior.

Validation performed:

  • git diff --check passed.
  • A targeted ESLint comparison against develop confirmed that the change introduces no new findings.
  • Local browser validation was blocked by an unrelated Laravel bootstrap error: Target class [view] does not exist.

Related Tickets & Packages

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

@processmaker-sonarqube

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

@nolanpro

Copy link
Copy Markdown
Contributor

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

@eiresendez
eiresendez requested a review from mcraeteisha August 12, 2026 12:03
@eiresendez eiresendez self-assigned this Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants