Skip to content

fix: restore authz bg styles but keep content cap to header xl - #235

Merged
dcoa merged 7 commits into
openedx:masterfrom
eduNEXT:dcoa/fix-authz-styles
Sep 24, 2026
Merged

dcoa merged 7 commits into
openedx:masterfrom
eduNEXT:dcoa/fix-authz-styles

Conversation

@dcoa

@dcoa dcoa commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Summary

01fdfb5 wrapped the app body in Container size="xl" fluid px-0 so it would line up with the site header. That capped the whole body at the header's max width, which also clipped the authz module's colour bands: bg-light-100 behind the title and bg-light-200 behind the content stopped bleeding to the viewport edges, leaving the page background showing down both sides above 1464px.

home wizard
image image

This restores the full-bleed bands while keeping the alignment, and consolidates the page chrome that had drifted apart across the module's four pages.

home wizard
image image

Also fixed

  • Permissions table could not be scrolled sideways. A 432px table sat in a 279px card with no scroll container in the ancestor chain; the card now scrolls horizontally.
  • Wizard step 2 overflowed. The search field and Org filter were locked to a single line; the row now wraps and the hardcoded 300px width is gone.
  • Dead context prop removed from AuthZLayout: all three call sites passed { id: '', title: '', org: '' } for use in the StudioHeader, but that was not removed after the migration to frontend-base.
  • pageSubtitle is now optional. Only audit-user uses it; the others passed "" purely to satisfy the type.

@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Sep 22, 2026
@openedx-webhooks

openedx-webhooks commented Sep 22, 2026

Copy link
Copy Markdown

Thanks for the pull request, @dcoa!

This repository is currently maintained by @openedx/committers-frontend.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@codecov

codecov Bot commented Sep 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.53%. Comparing base (01fdfb5) to head (4d04747).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #235   +/-   ##
=======================================
  Coverage   98.53%   98.53%           
=======================================
  Files          73       73           
  Lines        1297     1299    +2     
  Branches      394      396    +2     
=======================================
+ Hits         1278     1280    +2     
  Misses         19       19           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dcoa
dcoa force-pushed the dcoa/fix-authz-styles branch from 72d4376 to d99430c Compare September 22, 2026 11:55
@dcoa
dcoa marked this pull request as ready for review September 22, 2026 12:10
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Ready for Review in Contributions Sep 22, 2026

@arbrandes arbrandes left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approved, but with a few suggestions. Address them at your convenience.

<Card>
// The matrix is wider than a narrow viewport once it has a few role columns, so the
// card scrolls rather than letting the table overflow with no way to reach it.
<Card className="overflow-auto">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

overflow-auto makes the Card the scroll container for the sticky-top headers below, so they no longer pin to the viewport at any width. Scope the scroll to small breakpoints with a media query, or drop sticky-top.

Comment on lines +84 to +91
<div className="col col-md-7">
<p className="text-primary font-weight-bold h4">{intl.formatMessage(messages['authz.tabs.permissionsRoles.courses.alert.title'])}</p>
<span>
<span className="font-weight-bold">{intl.formatMessage(messages['authz.tabs.permissionsRoles.courses.alert.note'])}</span>
{intl.formatMessage(messages['authz.tabs.permissionsRoles.courses.alert.description'])}
</span>
</div>
<div className="col col-5">
<div className="col col-md-5 mt-3 mt-md-0">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

.col is flex: 1 0 0, so these still sit 50/50 below md (and flex-wrap is already the .row default). col-12 col-md-7 / col-12 col-md-5 will stack them.

return (
<Container className="p-5">
<>
<Container className="pb-5">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

With the outer Container gone, this one is centred with Paragon's breakpoint max-widths, so the toggle drifts up to ~100px right of the table at tablet widths. A plain <div className="pb-5"> fixes it.

{typeof pageSubtitle === 'string'
? <> { pageSubtitle !== '' && <hr className="mx-lg-3" /> }<h3 className="mb-0 py-2 font-weight-light text-gray-700">{pageSubtitle}</h3></>
: <>{ pageSubtitle !== '' && <hr className="mx-lg-3" /> } <div className="mb-0">{pageSubtitle}</div></>}
? <> { pageSubtitle !== '' && <hr className="authz-action-divider mx-lg-3" /> }<h3 className="mb-0 py-2 font-weight-light text-gray-700">{pageSubtitle}</h3></>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: with no subtitle this still renders an empty <h3> (axe empty-heading). Consider rendering nothing when pageSubtitle is falsy.

Comment thread src/style.scss Outdated
// element stays full width, so a background it carries still bleeds to the edges. Must
// span the viewport: `100%` resolves against its own containing block, so nested in a
// constrained box the overhang silently goes to zero. Pair with `py-*`, not `p-*`, and
// not on a Paragon `Container` -- its gutter ties on specificity and wins on order.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: frontend-base wraps Paragon in @layer paragon and app CSS in a higher layer, so .page-band would beat the Container gutter regardless of order. The py-* advice holds only because .p-* is !important.

@dcoa

dcoa commented Sep 23, 2026

Copy link
Copy Markdown
Contributor Author

thanks @arbrandes i addressed your feedback.

If there is not additional comment I will merge this tomorrow.

@dcoa
dcoa merged commit 8242c1c into openedx:master Sep 24, 2026
6 checks passed
@openedx-semantic-release-bot

Copy link
Copy Markdown
Collaborator

🎉 This PR is included in version 1.0.0-alpha.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U released on @latest

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants