Pinning a webcam tile as moderator is applied globally which is unexpected
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the webcam tile menu and the handlers for “Pin” and “Focus”; the issue does not name specific files or tests. Check how the pin action is shared with meeting participants and how the menu communicates its scope. Done when moderators can tell that pinning affects everyone and the pinned tile is visually distinct from a locally focused tile.
Written by the indexing model from the issue text.
Description
When a moderator selects "Pin" on a webcam tile, the pin is propagated to all viewers in the meeting. However, nothing in the UI indicates that this action affects everyone: the pin toggle looks like a purely local view option (similar to "Focus"), and there is no confirmation dialog, tooltip, or visual marker communicating that the pin is global.
As a result, moderators unknowingly change the video layout for all participants, while believing they are only adjusting their own view.
Steps to reproduce:
- Join a meeting with at least two participants as moderator.
- Click on the name of another participant in the webcam tile view
- Select "Pin".
Expected behavior:
- The UI clearly indicates that pinning is a global action affecting all viewers (e.g., tooltip, confirmation prompt, or an explicit label such as "Pin for everyone").
- The pinned tile is visually distinguishable from locally focused tiles.
Actual behavior:
- Pinning is applied to all participants without any indication. The moderator cannot tell whether the action was local or global.
Suggested fix:
- Add a hint next to the "Pin" action, e.g. "Pin (visible to everyone)".
- Optionally show a brief confirmation for moderators: "Pin this video for all participants?" with the option to pin locally (focus) instead.
- Other options within the tile menu, e. g. "Focus" should be handled similarly if they affect the view of all users
- Dominant language
- Ruby
- Stars
- 850
- Forks
- 3.6k
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 9
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 bigbluebutton/greenlight
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bigbluebutton/greenlight#6266 ·
Maintainers usually reply within 6 days
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
bigbluebutton/greenlight#6340 ·
Maintainers usually reply within 6 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
bigbluebutton/greenlight#6338 ·
Maintainers usually reply within 6 days
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
bigbluebutton/greenlight#6326 · 1 reaction ·
Maintainers usually reply within 6 days
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
bigbluebutton/greenlight#6325 ·
Maintainers usually reply within 6 days
All issues in bigbluebutton/greenlight
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Parallels/vagrant-parallels#530 ·
-
Good first issue: add rails-hotwire stack budget preset (Ruby on Rails 8 + Hotwire + PostgreSQL)Openenhancement good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
simp/pupmod-simp-tftpboot#152 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fluent/fluent-plugin-kafka#612 ·
Maintainers usually reply within 2 days