Skip to content

fix: Data browser table headers misaligned when scrolling horizontally - #3505

Open
3011felix wants to merge 1 commit into
parse-community:alphafrom
3011felix:fix/header-horizontal-scroll-misalignment
Open

3011felix wants to merge 1 commit into
parse-community:alphafrom
3011felix:fix/header-horizontal-scroll-misalignment

Conversation

@3011felix

@3011felix 3011felix commented Oct 25, 2026 •

Copy link
Copy Markdown

Pull Request

Issue

In the data browser, scrolling a wide class horizontally makes the column headings drift away from their data columns. The header bar stops moving after a certain offset (≈180px in a 2160px-wide table in a 1212px viewport) while the rows keep scrolling, so every heading sits over the wrong column.

Approach

The header bar .bar is position: sticky with both top: 0 and left: 0. top: 0 keeps the header pinned when scrolling vertically, which is intended. left: 0 also makes the bar stick horizontally until it hits the edge of its containing block, so it lags behind the rows.

This removes left: 0. The checkbox, row-number and frozen-column header cells keep their own position: sticky; left: … and still pin correctly.

Measured in Chrome on a real class (left edge of the first data column, header vs row):

scrollLeft before (header / row) after (header / row)
0 330 / 330 330 / 330
300 210 / 30 30 / 30
948 (max) -438 / -618 -618 / -618

Tasks

  • Add tests: not added; the misalignment comes from browser sticky layout, which jsdom does not compute.

Summary by CodeRabbit

  • Style
    • The data browser header bar no longer applies a fixed offset from the left edge. Its sticky positioning and top alignment remain unchanged.

The header bar used position: sticky with left: 0, so it partly stuck
to the left edge while the rows scrolled. Past a certain scroll offset
the headings lagged behind the data columns. Only top: 0 is needed to
keep the header pinned vertically.
@parse-github-assistant

Copy link
Copy Markdown

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

  • Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
  • Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
  • Group code into logical blocks. Add a short comment before each block to explain its purpose.
  • We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
  • Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
  • Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

@coderabbitai

coderabbitai Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8b588a53-a001-4a2c-afeb-6ab432d9f8f6
Commits

Reviewing files that changed from the base of the PR and between 13ecc66 and bf7d344.

Files selected for processing: 1
  • src/components/DataBrowserHeaderBar/DataBrowserHeaderBar.scss
Files with no reviewable changes: 1
  • src/components/DataBrowserHeaderBar/DataBrowserHeaderBar.scss

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

Walkthrough

The .bar style no longer sets left: 0. Its sticky positioning, top: 0, and other styles remain unchanged.

Changes: Header Bar Style

Layer / File(s) Summary
Header bar positioning
src/components/DataBrowserHeaderBar/DataBrowserHeaderBar.scss
The .bar style no longer explicitly anchors the sticky bar to the left edge.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: Minimal · up to bf7d3

The header should track the data columns during horizontal scrolling while remaining pinned vertically. No issue requiring a pre-merge fix is identified.

Pre-merge checks: Passed 7
Check name Status Explanation
Title check Passed The title begins with the required prefix "fix:" and the first letter after the prefix is capitalized ("Data"). It accurately describes the change, which removes left: 0 from the sticky header bar so …
Description check Passed The description follows the repository template. It includes the security and license lines, an Issue section describing the horizontal drift bug, an Approach section explaining the sticky positioning…
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Security Check Passed The pull request changes only one stylesheet declaration: it removes left: 0 from .bar in src/components/DataBrowserHeaderBar/DataBrowserHeaderBar.scss. The remaining rules are layout and presen…
Engage In Review Feedback Passed The current review produced zero actionable findings, and no posted CodeRabbit review threads were returned. Therefore, there was no review feedback requiring engagement, implementation, or discussion…
Full details: Title check

Explanation

The title begins with the required prefix "fix:" and the first letter after the prefix is capitalized ("Data"). It accurately describes the change, which removes left: 0 from the sticky header bar so column headings stay aligned with data columns during horizontal scrolling.

Full details: Description check

Explanation

The description follows the repository template. It includes the security and license lines, an Issue section describing the horizontal drift bug, an Approach section explaining the sticky positioning root cause and the one-line fix with before/after Chrome measurements, and a Tasks section. The tests task is unchecked with a stated reason (jsdom cannot compute browser sticky layout), and the documentation task is not addressed. The Tasks entry is a justified omission rather than a missing section.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

Full details: Security Check

Explanation

The pull request changes only one stylesheet declaration: it removes left: 0 from .bar in src/components/DataBrowserHeaderBar/DataBrowserHeaderBar.scss. The remaining rules are layout and presentation properties. No code, input handling, authentication, authorization, data access, or dependency changes introduce a security vulnerability.

Full details: Engage In Review Feedback

Explanation

The current review produced zero actionable findings, and no posted CodeRabbit review threads were returned. Therefore, there was no review feedback requiring engagement, implementation, or discussion.

Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@3011felix
3011felix marked this pull request as ready for review October 25, 2026 14:36
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.

1 participant