[Bug] PR comments are not resized

[AndriySvyryd]

Steps to Reproduce

1. Go to chore(main): release 0.0.12 #63

Expected Behavior

The comment column to use all available space

Actual Behavior

The comment column is as wide as it was without this extension

Screenshots

Environment

• Browser: Edge Version 149.0.4022.62 (64-bit)
• Extension Version: 0.0.11
• OS: Windows 11
• GitHub Page: pull requests

Enabled Features

• Wide Layout
• Table Expand
• Image Lightbox
• GIF Picker
• Sidebar Toggle

Console Errors

None

[lamngockhuong]

Thanks for the detailed report, @AndriySvyryd! 🙏

I tried to reproduce this on the current GitHub PR Conversation layout with v0.0.11 and the comment column expands to full width in every case I tested:

• Logged out & logged in
• Viewport widths 1365px, 1920px, and 2167px (matching your screenshot)

In the current layout, the comment column is wrapped in GitHub's prc-PageLayout-Content region, and the extension's existing .container-xl { max-width: none } rule already lets it fill the widened container (GitHub also relaxes its own max-width: 1012px cap to 100%).

My guess is your screenshot was taken on a different PR Conversation layout variant that GitHub was rolling out (these are A/B'd per account/browser, and you're on Edge). That variant may keep a hard max-width on the comment column that our selectors don't reach.

Could you help confirm a couple of things on the latest version?

1. Is this still happening for you right now on chore(main): release 0.0.12 #63 ?
2. If yes, open DevTools → Elements, select one comment (.TimelineItem), and walk up its ancestors to find the element that still has a max-width set. A screenshot of that DOM chain (or the offending element's class) would let me target the exact fix.

If it's no longer reproducing, it was likely resolved by a GitHub layout change and we can close this out. Thanks again!

[AndriySvyryd]

My guess is your screenshot was taken on a different PR Conversation layout variant that GitHub was rolling out (these are A/B'd per account/browser, and you're on Edge). That variant may keep a hard max-width on the comment column that our selectors don't reach.

I also see the same behavior in Chrome, must be dependent on my account.

This is the offending class: .Conversations-module__content__IAZbQ

[lamngockhuong]

Thanks @AndriySvyryd, that Conversations-module__content__<hash> class was the missing piece. GitHub is rolling out a new PR Conversation layout that caps the comment column with that CSS-module class, and our existing selectors didn't reach it.

I've opened a fix in #76 that targets the stable class prefix (the hash suffix changes per deploy, so we can't match it literally).

Since I can't reproduce this layout variant on my account, I'd appreciate a quick test before merging. A Chrome/Edge build with the fix is attached below.

How to load it (unsigned, so Developer Mode only):

1. Download and unzip github-flex-pr76-chrome.zip.
2. If you have GitHub Flex from the store installed, disable it first so two copies don't run at once.
3. Open chrome://extensions (or edge://extensions) and enable Developer mode (top-right toggle).
4. Click Load unpacked and select the unzipped folder (the one containing manifest.json).
5. Hard-reload chore(main): release 0.0.12 #63 and check the comment column.

If the comment column now fills the width, let me know and I'll merge + ship a release. If it still caps, a fresh screenshot of the Conversations-module__content... element's computed max-width would help me dig further. Thanks!