[FR]: Associate native PiP with its source window on Wayland
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- desktop
Research direction
Start by reviewing the linked local implementation and the browser's native PiP window creation and Wayland integration points. Check how the originating browser window is associated with PiP, then verify that the compositor places PiP on the same workspace when browser windows share a process. Done means the association works without taking ownership of the source window; no test or source file is named in the issue.
Written by the indexing model from the issue text.
Description
Description
Associate native PiP with the browser window that opened it so Wayland compositors can place it correctly.
Who's implementing?
- I'm willing to implement this feature myself
The problem
PiP can open on a different workspace from the window that opened it when browser windows share a process.
Possible solutions
I've implemented and tested a change locally that gives the compositor a non-owning association with the originating browser window. Would you accept a Linux PR for this?
Additional context
Resubmitted through the feature request form as requested in #453. Aspect-ratio resizing is tracked separately in #452.
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#452 · 1 comment ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 80/100