element-hq / element-hq/element-web

Replying with a location message does not send as reply

Open
#33,323 0 comments 0 reactions 0 assignees View on GitHub
A-Composer A-Location-Sharing A-Replies O-Uncommon S-Minor T-Defect Z-ProductPolish
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Open a room
2. Hover over a message and click the "Reply" button
3. Observe that the composer now has "Replying" and a quote of the message being replied-to above it
4. Click the "More options" menu (three dots) to the right of the composer
5. Click "Location" and select "Drop a pin"
6. Drop a pin somewhere
7. Click "Share location"

### Outcome

#### What did you expect?

The location message should be sent as a reply, with a `m.in_reply_to` referencing the message being replied-to. The "Replying" state should be cleared from the composer.

#### What happened instead?

The location message is sent not as a reply (without a `m.in_reply_to`). The composer stays in the "Replying" state.

### Operating system

_No response_

### Browser information

_No response_

### URL for webapp

staging.element.io

### Application version

Element version: 1.12.16

### Homeserver

_No response_

### Will you send logs?

No

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.