issues Search Results · language:Dune language:JavaScript language:JavaScript language:Java language:JavaScript language:C#
Filter by
39.5M results
Summary
Sessions are ephemeral with no replay capability. A recording feature produces a replayable artifact for async review,
onboarding, or documentation.
Problem Statement
Team members across time ...
needs-template
Summary
Closing the browser tab without clicking Leave does not properly terminate the WebSocket connection. The departed
participant remains visible in the session for 30+ seconds.
Current Behavior ...
needs-template
Summary
Participants have no in-session communication channel and must switch to external messaging apps, breaking focus and
context.
Problem Statement
During a collaborative review, participants need ...
needs-template
Summary
All participants currently have equal ability to annotate and move cursors. Presenters and code reviewers need a way to
invite observers who can watch but not interact.
Problem Statement
During ...
needs-template
Summary
TabTwin relays cursor positions, annotations, and tab content through a signaling server in plaintext. Without
end-to-end encryption, the server operator or any network intermediary can read shared ...
needs-template
So, on line 50, the class should be infoHeading for it to work the way you want.
Like this:
div class= infoHeading span id= highlighted_airline n/a /span /div
infoData : NO! infoHeading : OK!
Summary
Currently every review scans all files in the repository. For large codebases, this is slow and buries new findings
among re-listed old ones. A diff mode restricts analysis to files changed in ...
Summary
When a contributor pushes new commits to an open PR (triggering a synchronize webhook), the reviewer posts a full new
comment thread instead of updating the previous one. PRs with multiple pushes ...
Summary
Review results exist only in the browser or terminal. PDF and Markdown export let teams attach reports to PRs, Jira
tickets, or documentation wikis.
Problem Statement
After a review, engineers ...
Summary
All review rules are hardcoded. A config file at the repo root would let teams disable noisy checks, adjust severities,
and ignore generated file paths.
Problem Statement
A project that intentionally ...

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.