Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error sending event to widget: Unknown or unsupported action: send_event #20815

Closed
jaller94 opened this issue Jan 31, 2022 · 3 comments
Closed

Comments

@jaller94
Copy link
Contributor

Steps to reproduce

  1. We use a spanner 🔧 widget to avoid working on the same system at once.
  2. It sets a state event and posts a message every time someone takes or drops a spanner.

Outcome

What did you expect?

No error

What happened instead?

A console error whenever I take or drop the spanner.

Screenshot_2022-01-31_13-50-57

Operating system

Manjaro Linux

Browser information

Firefox Developer 97

URL for webapp

staging.element.io

Application version

Element version: 1.9.10-rc.2, Olm version: 3.2.8

Homeserver

vector.modular.im

Will you send logs?

No

@jryans
Copy link
Collaborator

jryans commented Jan 31, 2022

@jaller94 Can you share the source of the widget?

@jaller94
Copy link
Contributor Author

jaller94 commented Jan 31, 2022

@jryans
Copy link
Collaborator

jryans commented Jan 31, 2022

@jaller94 This appears to be an artefact of the current matrix-widget-api contract as hinted in the docs: it currently expects you to call ev.preventDefault() and send a reply for any event you process.

Personally, I find this to be a somewhat surprising API expectation, as it leads to extra error messages like this, even though the widget has actually processed the data anyway. I filed matrix-org/matrix-widget-api#53 to discuss possibly changing that contract for the general case.

To resolve this for the spanner widget, either you can wait to see the outcome of that general API contract change, or the spanner widget could be altered to follow the current contract.

Either way, the changes wouldn't happen in Element Web directly, so I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants