obsproject / obsproject/obs-studio
Window capture shifts the source outside of it's bounding box when "unmaximizing" browsers only. Fresh install. Easily replicated.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
30.2.3
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/78VkGhxrtaLj9SBF
OBS Studio Crash Log URL
No response
Expected Behavior
On a Window Capture, unmaximizing a browser should not shift the contents outside of it's own bounding box.
Current Behavior
On a Window Capture, unmaximizing a browser causes the source's contents to be shifted down within it's own bounding box by 21px as noted by both the empty space between the top of the bounding box and top of the browser as well as the content that's cut off at the bottom.
Steps to Reproduce
- Fresh install.
- No changes to any settings whatsoever.
- Start w/ a browser (tested on both Firefox and Chrome) maximized.
- Add window capture for that browser.
- "Restore down" the browser (make the window not maximized).
Anything else we should know?
Workaround Fixes:
• Hiding and showing the source (or any other edit to the source).
• Restarting OBS.
• Changing scenes but NOT in Studio Mode.
Observations:
• This happens every time you maximize and then unmaximize the window.
• The size of the source seems to update correctly (I can test a specific window size w/ window management software), it's "internal" contents are just shifted outside of the bounding box.
• This happens with or without "Client Area" being checked.
• It only seems to do it with browsers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with Firefox or Chrome on Windows 10 using the listed maximize and restore-down steps, then inspect the attached OBS Studio log. Done means the window-capture contents remain aligned with their bounding box after restoring the browser, without needing to hide the source or restart OBS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100