Closed
Bug 1138642
Opened 10 years ago
Closed 9 years ago
Tab sharing may need a de-bouncing mechanism
Categories
(Hello (Loop) :: Client, defect, P5)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: standard8, Unassigned)
References
Details
(Whiteboard: [screensharing])
Currently tab sharing files all window ids straight to the sdk. With the latest version of the sdk, we should check to see if we need a de-bouncing mechanism or not and implement it if required.
I'm not sure if we will need it - as I suspect replaceTrack very quickly replaces what it had with the new window, but we should still check this.
|
Reporter | |
Updated•10 years ago
|
Rank: 8
|
||
Updated•10 years ago
|
Flags: firefox-backlog+
|
|
||
Comment 1•10 years ago
|
||
improvement - haven't seen issues - will move up much higher if see reported. currently tab sharing seems fast enough on developer machines :)
Rank: 8 → 50
Priority: P1 → P5
Whiteboard: [screensharing]
|
|
Reporter | |
Comment 3•9 years ago
|
||
(In reply to Ian Bicking (:ianb) from comment #2)
> Mark: is this still valid?
I'm slightly cautious that we might be getting some issues when switching tabs, but I'm not quite sure (I wonder if changing too quickly can affect the sdk). There's other UI changes being discussed (like not switching straight away) that might help this as well.
Lets mark this as wfm for now, and if we see issues in the wild, then we can address them.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(standard8)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•