Closed Bug 1210843 Opened 10 years ago Closed 10 years ago

Inert messaging area in release browser when messaging during FxA contact call

Categories

(Hello (Loop) :: Client, defect)

defect
Not set
normal

Tracking

(firefox41 wontfix, firefox42 unaffected, firefox43 unaffected, firefox44 unaffected)

RESOLVED WONTFIX
Tracking Status
firefox41 --- wontfix
firefox42 --- unaffected
firefox43 --- unaffected
firefox44 --- unaffected

People

(Reporter: rpapa, Unassigned)

Details

STR - SCENARIO #1 [1]. Open 2 browsers with clean profiles (1 Nightly, 1 General Release) [2]. Login both browsers to separate firefox accounts [3]. Add the Firefox account contact of one of the users to the other browser [4]. Initiate a call to the other firefox account contact [5]. Send a message from Nightly to General Release [6]. Observe that message area posts correctly on Nightly, but message area on General Release browser is inert (unable to post messages) and obscured by black background (though it does resize with new messages) https://www.dropbox.com/s/oavjv3taali9v7t/Screenshot%202015-10-02%2008.40.07.png?dl=0 STR - SCENARIO #2 [1]. Open 2 browsers with clean profiles (Both General Release) [2]. Login both browsers to firefox accounts [3]. Add the Firefox account contact of one of the users to the other browser [4]. Initiate a call to the other firefox account contact [5]. Observe that message area on both browsers is inert (unable to post messages) and obscured by black background https://www.dropbox.com/s/shk45nf013egbom/obscured.png?dl=0
I managed to figure this out: - Firefox 41 supports text chat for rooms (aka conversations). It doesn't support text chat for direct calls. - 42 and later added support for text chat. - We detect text chat based on if we're able to set up data channels. - Due to the support 41 has for rooms, the code that's shared between rooms & direct calls automatically sets up the data channels. - Hence, 42 detects this and enables text chat - 41 doesn't know about text chat in direct calls, and so doesn't provide a text box. Hence the broke state. Given 41 is in release and would be where the fix is needed, this is unfortunately a wontfix for 41 (and not chemspill worthy). In 42 it'll resolve itself. Note this only affects users using 42 or later to talk to 41 via direct calls.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.