You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integration managers currently use the "Scalar Messaging API", a rather old and not particularly well-documented API which enables the integration manager iframe to communicate with the client via postmessage to request specific actions like inviting a user or setting a widget.
In many ways, integration managers are very much like widgets -- external pages in an iframe which communicate with the client via postmessage API. It follows then, that it would be a benefit in terms of flexibility and ease of client implementation for integration managers to use the Widget API instead.
Indeed there is already significant overlap in functionality of the two APIs. To the extent that, as far as I can tell the Widget API is already a superset:
This has been cut down to Scalar API actions which to my knowledge are actually in use. There are a number of other actions which refer to unspecced or unsupported functionality.
What would you like to do?
Enable integration managers to use the Widget API across all clients.
Why would you like to do it?
Improve flexibility and ease of implementation for both clients and integration managers.
How would you like to achieve it?
Listen for Widget API requests from the integration manager iframe.
There may be other considerations for how the user grants permissions to the integration manager, and how to approach deprecation of the Scalar API.
Have you considered any alternatives?
Another option could be for the integration managers to become a full embedded Matrix client rather than having to communicate with the parent client, but this seems much more complex.
Additional context
No response
Are you willing to provide a PR?
No
The text was updated successfully, but these errors were encountered:
Your use case
Integration managers currently use the "Scalar Messaging API", a rather old and not particularly well-documented API which enables the integration manager
iframe
to communicate with the client via postmessage to request specific actions like inviting a user or setting a widget.In many ways, integration managers are very much like widgets -- external pages in an
iframe
which communicate with the client via postmessage API. It follows then, that it would be a benefit in terms of flexibility and ease of client implementation for integration managers to use the Widget API instead.Indeed there is already significant overlap in functionality of the two APIs. To the extent that, as far as I can tell the Widget API is already a superset:
close_scalar
close_modal
get_widgets
read_events
set_widget
send_event
join_rules_state
m.room.join_rules
for the roomread_events
get_room_enc_state
m.room.encryption
for the roomread_events
membership_state
m.room.member
for a user in the roomread_events
set_bot_power
m.room.power_levels
for a user in the roomsend_event
invite
send_event
kick
send_event
get_open_id_token
get_openid
What would you like to do?
Enable integration managers to use the Widget API across all clients.
Why would you like to do it?
Improve flexibility and ease of implementation for both clients and integration managers.
How would you like to achieve it?
Listen for Widget API requests from the integration manager
iframe
.There may be other considerations for how the user grants permissions to the integration manager, and how to approach deprecation of the Scalar API.
Have you considered any alternatives?
Another option could be for the integration managers to become a full embedded Matrix client rather than having to communicate with the parent client, but this seems much more complex.
Additional context
No response
Are you willing to provide a PR?
No
The text was updated successfully, but these errors were encountered: