d->m: Consider using tables for inline embed fields #28

New Issue

Open

opened 2024-01-13 10:24:14 +00:00 by cadence · 1 comment

cadence commented

2024-01-13 10:24:14 +00:00

Owner

Tables aren't supported on Element Android, but a workaround is to use the elements td p /p td td p /p td. Android will render the P elements and not the table structure, and Element Web will render the table structure and not the P. This looks good on nheko too.

Inline fields would look weird if they were the only ones in the table and had a border, but apparently colspan is supported, so the whole embed can be in a table! Nice!

Tables aren't supported on Element Android, but a workaround is to use the elements `td p /p td td p /p td`. Android will render the P elements and not the table structure, and Element Web will render the table structure and not the P. This looks good on nheko too. Inline fields would look weird if they were the only ones in the table and had a border, but apparently colspan is supported, so the whole embed can be in a table! Nice!

cadence commented

2024-01-13 10:30:13 +00:00

Author

Owner

colspan isn't supported in Element, here's the MSC: https://github.com/matrix-org/matrix-spec-proposals/pull/4003

Implementing these tables in OOYE and Schildi should hopefully be enough for them to update the sanitiser in Element.

Nheko already supports colspan, yay!

`colspan` isn't supported in Element, here's the MSC: https://github.com/matrix-org/matrix-spec-proposals/pull/4003 Implementing these tables in OOYE and Schildi should hopefully be enough for them to update the sanitiser in Element. Nheko already supports `colspan`, yay!

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cadence/out-of-your-element#28

No description provided.