element-hq / element-hq/element-web

Verification only half-completes - left waiting for confirmation

Open
#13,303 1 comment 1 reaction 0 assignees View on GitHub
T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

Between the linux Desktop client and chromium Web client, the non-legacy verification does not complete for the Desktop client. After the emoji verification, we are left with a spinning dialogue:

![image](https://user-images.githubusercontent.com/64051199/79815847-be80f980-834f-11ea-8054-0e114b9befe9.png)

The desktop client is also left waiting for confirmation.
![image](https://user-images.githubusercontent.com/64051199/79815889-da849b00-834f-11ea-9437-4de9a3135f76.png)

After clicking back into the compose message window, the dialogue disappears and apparently cancels the remaining verification, leaving the Web client to see the Desktop client as verified (green shield), but the Desktop client does NOT see the Web client as verified (red shield).

The only way around this was to use the Legacy method to verify the Web client session.

Versions
riot-web version: 1.5.15
olm version: 3.1.3

Contributor guide

Open the contributing guide

Research direction

Reproduce non-legacy emoji verification between the Linux Desktop client and Chromium Web client using the reported versions, then trace the verification flow from the spinning dialogue and confirmation state. Done means both clients complete verification and show each other as verified without cancelling when returning to the compose window.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.