matrix-widget-api
matrix-widget-api copied to clipboard
JavaScript/TypeScript API for widgets & web clients to communicate
https://matrix.to/#/!rDkLtgRQarvieuFHBA:t2l.io/$M5vvMdiNrsNxh4eB8_S8Z-S17TrUns3KE-qXX71dYBk?via=matrix.org&via=element.io&via=envs.net > Yes you are right. You could try to pass either the client origin (i.e. the Element URL) of "*" to the [WidgetApi constructor](https://github.com/matrix-org/matrix-widget-api/blob/5d6a4e8caf6d989d2564c2cf964b3783399b10fd/examples/widget/index.html#L65). > > The problem was...
See https://github.com/matrix-org/matrix-spec-proposals/pull/3817 for more details.
**Is your feature request related to a problem? Please describe.** The name 'matrix-widget-api' causes the package to frequently get confused with the The Widget API when talking to people about...
https://github.com/matrix-org/matrix-spec-proposals/pull/3819
On each side of the widget transport, there are `handleMessage` functions such as: ```js private handleMessage(ev: CustomEvent) { const actionEv = new CustomEvent(`action:${ev.detail.action}`, { detail: ev.detail, cancelable: true, }); this.emit(`action:${ev.detail.action}`,...
The API surface we expose doesn't support iterative changes to capabilities very nicely, so we should change that.
Let's say my friend hosts a hypothetical video game that allows users to join without registration, and a URL like `https://coolgame.com/?guestname=` allows the browser to suggest a pre-filled username (similar...
Need to `yarn build` the project, copy the `dist/api.js` to next to the `index.html`, and serve the widget off a web server of some sort.
The given example given in https://github.com/matrix-org/matrix-widget-api/tree/master/examples/widget, gives 404 for `api.js`. By replacing https://github.com/matrix-org/matrix-widget-api/blob/master/examples/widget/index.html#L50 with ``, I get the following errors when opening the `Custom Widget`: ``` Action:notify_capabilities failed with message:...
This is meant to be an independent thing from the Element stack, but we should use familiar changelog tooling.