fix: Pagination footer bar hides rows in data browser

[mtrezza]

Summary

• ensure cells are scrolled into view before hitting BrowserFooter

Testing

• npm test (fails: jest not found)
• npm run lint (fails: cannot find module 'eslint/config')

---

https://chatgpt.com/codex/tasks/task_e_686e76052c40832db1eaa717673e5a14

Summary by CodeRabbit

• Bug Fixes
  • Improved scrolling behavior to ensure that cells are not hidden behind the footer when brought into view.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[parse-github-assistant]

The label codex cannot be used here.

[parseplatformorg]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[coderabbitai]

📝 Walkthrough

Walkthrough

The change updates the scroll-into-view logic in the BrowserCell component by introducing a bottomBoundary constant, which accounts for the height of the BrowserFooter. This ensures that when a cell is scrolled into view, it is not hidden behind the footer.

Changes

File	Change Summary
src/components/BrowserCell/BrowserCell.react.js	Adjusted scroll-into-view logic to use a new bottomBoundary constant that considers footer height.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BrowserCell
    participant Window

    User->>BrowserCell: Triggers cell scroll into view
    BrowserCell->>Window: Get window.innerHeight
    BrowserCell->>BrowserCell: Calculate bottomBoundary (window.innerHeight - 36)
    BrowserCell->>BrowserCell: Check if cell's bottom > bottomBoundary
    alt Cell is out of view
        BrowserCell->>Window: Scroll cell into view (above footer)
    end

Loading

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error code ERR_SSL_WRONG_VERSION_NUMBER
npm error errno ERR_SSL_WRONG_VERSION_NUMBER
npm error request to https://10.0.0.28:4873/npm/-/npm-10.9.2.tgz failed, reason: C0CCF6A5347F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
npm error
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-09T14_10_12_306Z-debug-0.log

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/components/BrowserCell/BrowserCell.react.js (1)

238-239: Good implementation with a minor suggestion for maintainability.

The introduction of bottomBoundary constant properly accounts for the BrowserFooter height, which should fix the visibility issue. The descriptive comment clearly explains the purpose.

However, consider making the footer height configurable or importing it from a constants file to avoid the magic number 36.

Consider extracting the footer height to a constant:

+const BROWSER_FOOTER_HEIGHT = 36;
+
 // BrowserToolbar + DataBrowserHeader height
 const topBoundary = 126;
 // Account for BrowserFooter height when checking the bottom boundary
-const bottomBoundary = window.innerHeight - 36;
+const bottomBoundary = window.innerHeight - BROWSER_FOOTER_HEIGHT;

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 92ce7a5 and 1b453fe.

📒 Files selected for processing (1)

• src/components/BrowserCell/BrowserCell.react.js (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Docker linux/amd64

🔇 Additional comments (1)

src/components/BrowserCell/BrowserCell.react.js (1)

243-243: Correct implementation of the bottom boundary check.

The updated condition properly uses the bottomBoundary constant instead of the raw window.innerHeight, which ensures cells are scrolled into view before being obscured by the footer.

[uffizzi-cloud]

Uffizzi Ephemeral Environment deployment-64561

⌚ Updated Jul 09, 2025, 14:12 UTC

☁️ https://app.uffizzi.com/github.com/parse-community/parse-dashboard/pull/2879

📄 View Application Logs etc.

What is Uffizzi? Learn more

[parseplatformorg]

🎉 This change has been released in version 7.3.0-alpha.7