Skip to content

Add bottom padding to prevent floating help button from obscuring content#609

Open
jon-bell wants to merge 1 commit intostagingfrom
claude/fix-help-button-overlap-THOPk
Open

Add bottom padding to prevent floating help button from obscuring content#609
jon-bell wants to merge 1 commit intostagingfrom
claude/fix-help-button-overlap-THOPk

Conversation

@jon-bell
Copy link
Contributor

@jon-bell jon-bell commented Feb 14, 2026

The fixed-position "Get Help" button (bottom-right corner) could overlap
and hide content in discussion posts, rubric sidebar, and other pages.
Added pb="80px" to the course layout content wrapper, discussion scroll
container, and rubric sidebar scroll container so users can always scroll
past the floating widget.

https://claude.ai/code/session_012tQEji4uZCSLG57K5Q9yT9

Summary by CodeRabbit

  • Style
    • Enhanced bottom spacing consistency across course layouts, discussion pages, and assignment submission views for improved visual hierarchy and content separation.

…tent

The fixed-position "Get Help" button (bottom-right corner) could overlap
and hide content in discussion posts, rubric sidebar, and other pages.
Added pb="80px" to the course layout content wrapper, discussion scroll
container, and rubric sidebar scroll container so users can always scroll
past the floating widget.

https://claude.ai/code/session_012tQEji4uZCSLG57K5Q9yT9
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 14, 2026

Walkthrough

Three layout files receive consistent bottom padding adjustments (80px), replacing or supplementing existing vertical padding configurations across course submission, discussion, and main layout components.

Changes

Cohort / File(s) Summary
Layout spacing adjustments
app/course/[course_id]/assignments/[assignment_id]/submissions/[submissions_id]/layout.tsx, app/course/[course_id]/discussion/layout.tsx, app/course/[course_id]/layout.tsx
Added or modified bottom padding to 80px across multiple layout files. Submissions layout now has pb="80px". Discussion layout changed from vertical padding shorthand to explicit top and bottom padding (pt and pb="80px"). Main course layout added pb="80px" to the children wrapper.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

Eighty pixels down the line,
Spacing flows so smooth and fine,
Three layouts breathe with breathing room,
No more cramped within the gloom! 🎨

🚥 Pre-merge checks | ✅ 3 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding bottom padding to prevent the floating help button from obscuring content, which aligns with all three file modifications.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into staging

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude/fix-help-button-overlap-THOPk

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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@app/course/`[course_id]/layout.tsx:
- Around line 62-64: The parent course layout's outer Box (rendering children)
redundantly applies pb="80px" while inner scrollable components (e.g., the
discussion layout's inner Box with flex="1" and RubricView) already provide
bottom padding for FloatingHelpRequestWidget; remove the parent's pb="80px" from
the Box around {children} (or replace it with a CSS variable for
bottom-safe-area and apply that variable only in scrollable components) so
padding is only applied by the scroll containers (update the Box instance that
currently has pt="0" ml="0" mr="0" pb="80px" and ensure
FloatingHelpRequestWidget still has room when present).

Comment on lines +62 to 64
<Box pt="0" ml="0" mr="0" pb="80px">
{children}
</Box>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

find app/course -name "layout.tsx" -o -name "layout.ts" | head -20

Repository: pawtograder/platform

Length of output: 1150


🏁 Script executed:

rg -n "100dvh|100vh" --type=tsx --type=ts app/course/

Repository: pawtograder/platform

Length of output: 91


🏁 Script executed:

find app/course -path "*discussion*" -name "*.tsx" | head -10

Repository: pawtograder/platform

Length of output: 639


🏁 Script executed:

find app/course -path "*submissions*" -name "*.tsx" | head -10

Repository: pawtograder/platform

Length of output: 965


🏁 Script executed:

cat -n app/course/[course_id]/discussion/layout.tsx

Repository: pawtograder/platform

Length of output: 4324


🏁 Script executed:

cat -n app/course/[course_id]/assignments/[assignment_id]/submissions/layout.tsx

Repository: pawtograder/platform

Length of output: 2464


🏁 Script executed:

cat -n app/course/[course_id]/layout.tsx | head -70

Repository: pawtograder/platform

Length of output: 3096


🏁 Script executed:

rg -n "RubricView" app/course/ -A 5 -B 2

Repository: pawtograder/platform

Length of output: 2022


🏁 Script executed:

cat -n app/course/[course_id]/assignments/[assignment_id]/submissions/[submissions_id]/layout.tsx | sed -n '1281,1350p'

Repository: pawtograder/platform

Length of output: 3350


🏁 Script executed:

rg -n "return" app/course/[course_id]/assignments/[assignment_id]/submissions/[submissions_id]/layout.tsx | grep -A 20 "1281:"

Repository: pawtograder/platform

Length of output: 46


Consider removing redundant bottom padding or consolidating padding approach.

The discussion layout uses a flex-based structure where the outer Box (height="100dvh") acts as a viewport-bound container and the inner Box (flex="1") handles scrolling with its own pb="80px". The parent course layout also applies pb="80px", creating redundancy.

Since the discussion layout's scrollable container already manages its own bottom padding for the FloatingHelpRequestWidget, the parent's pb="80px" may be unnecessary and could cause unexpected spacing on pages that don't scroll internally (like non-thread discussion views).

RubricView has a similar pattern: height="100vh" with pb="80px" for internal scrolling, which is appropriately self-contained.

Consider:

  1. Removing pb from the parent layout, or
  2. Using a CSS variable to conditionally apply padding only where needed, rather than on the universal wrapper.
🤖 Prompt for AI Agents
In `@app/course/`[course_id]/layout.tsx around lines 62 - 64, The parent course
layout's outer Box (rendering children) redundantly applies pb="80px" while
inner scrollable components (e.g., the discussion layout's inner Box with
flex="1" and RubricView) already provide bottom padding for
FloatingHelpRequestWidget; remove the parent's pb="80px" from the Box around
{children} (or replace it with a CSS variable for bottom-safe-area and apply
that variable only in scrollable components) so padding is only applied by the
scroll containers (update the Box instance that currently has pt="0" ml="0"
mr="0" pb="80px" and ensure FloatingHelpRequestWidget still has room when
present).

@argos-ci
Copy link

argos-ci bot commented Feb 14, 2026

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ⚠️ Changes detected (Review) 67 changed, 2 removed, 8 failures Feb 14, 2026, 3:54 AM

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.

2 participants